Discussion of Problems due to Hardened Security

[JPagan]

@JPagan: Cylance protect? Sounds like a good candidate.

Is your company aware that Win10 has fairly decent AV built in? Cylance Protect may not be what causes your problem, but I think it's certainly worth testing what happens if it's disabled.

@mpack - Thanks for the info. Yes, I have Cylance Protect installed by my IT. I will have to look into that.

[ATS2016]

Hello Everyone,

I am running Windows 10 Home Version 1607. And, using VirtualBox 5.1.6. I have tried to start VirtualBox, but continue to get a rc=-5640 error. I am only using Windows Defender, and have searched high and low for a solution. I would greatly appreciate any help that can be provided.

Here is the log.

VBoxHardeningLog.zip

(9.38 KiB) Downloaded 21 times

[mpack]

@ATS2016: are you using some kind kind of accessibility software on your host? The problem seems to be many instances of "OLEACCHOOKS.DLL", which as best I can tell has to do with hooking software calls to add accessibility features. Unfortunately your copy of "OLEACCHOOKS.DLL" is unsigned.

You could also be suffering with malware which is piggybacking on this feature. You should check if your copy of the above DLL (it is in \SYSTEM32) has a timestamp and security stamp consistent with your other system DLLs.

[szgz]

OS: Window 7 profession X64
Virus software: MSE
Firewall: Microsoft windows firewall

1. install VirtualBox 5.0.0 , use ok.
2. Add a SSD hard disk, move boot partition (disk c) to SSD
3. OS and other softwares are ok, but virtualBox isn't ok.
4. Remove VirtualBox
5. reboot OS
6. reinstall VirtualBox 5.0.0, worked ok.
7. reboot OS, virtualbox didn't work, error.
8. reinstall VirtualBox 5.1.6, worked ok.
9. reboot OS, virtualbox didn't work, error.

[sau]

updating to the latest (5.1.6) just fixed it for me despite the changelog not containing anything related to this issue.

[forge33]

The 5.1.6 Update also fixed it for me

[HideData(Ha...)]

Virtual Box Version: 5.1.7.
OS: Win10-x64
IME:Chinese

I get "Error in supr3hardenedwinrespawn" erery time when start vm.
But I can restart Virtual Box and start vm after restarting The Process of IME.
Why????

[TDH Challenger]

Host OS: Windows 7 Ultimate, 64bit
Host AV: Free Avast

What I'm doing:
Install a Windows 2012 R2 server as a requirement due tomorrow. Several times I created a machine set as Windows 64bit (Other), but after clicking start I always get this error:

"Failed to open a session for the virtual machine 4HGrp9PC.

The virtual machine '4HGrp9PC' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\admin\VirtualBox VMs\4HGrp9PC\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}"

What I have tried:
-Uninstall and Resinstall as admin
-Disabling my AV

I will be eternally grateful if someone could at the very least offer me additional solutions so I can resolve this matter, thank you very much

[basty_goofy]

Hello, I seem to have this relatively common problem after the update. No VM can start at all. Not even a headless start. Or perhaps it has nothing to do with the update, but it doesn't matter, because I am at my wit's end.

Failed to open a session for the virtual machine d.

The virtual machine 'd' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

[JWIN]

VirtualBox: 5.1.6 (Previously 5.0)
Host OS: Windows 10 64bit
Windows Firewall

I have always been in Windows 10 using VirtualBox 5.0. I recently encountered an error that will not allow me to start any of my VMs. I upgraded to 5.1.6 and installed the extension pack just in case. I still receive the following error:

The virtual machine 'VM NAME' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\STRS VMs\STRS-DC\Logs\VBoxHardening.log'.

Result Code:
E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

[socratis]

@basty_goofy
Disable the real-time scan of Malware Antivirus (if it has any), disable it, or uninstall it altogether.

I seem to have this relatively common problem after the update.

I think it's not related to the Anniversary Update, but due to the antivirus. That is why I'm "merging" your question and my reply with the Discussion of Problems due to Hardened Security.

[basty_goofy]

I did pretty much everything suggested, including disabling Windows Defender (my only antivirus). Oh well...

[Veritas1980]

I am having the same problems here, but I cannot remove my antivirus, its malware-bytes. I've disabled it so its not running, no windows defender. the log file is too huge it wont let me attach it.

I'm in windows 7 ultimate 64bit, running virtualbox as administrator.

getting the same error with another OS

Failed to open a session for the virtual machine CentOS-6.6-x86_64-minimal.

The virtual machine 'CentOS-6.6-x86_64-minimal' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Owner\VirtualBox VMs\CentOS-6.6-x86_64-minimal\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

uninstalled and installed 5.0.26 instead and loaded a bit image since I didn't want to reboot and enable virtualization in the Bios, got this when trying to start it:

Failed to open a session for the virtual machine CentOS-6.5-i386-minimal.

Implementation of the USB 2.0 controller not found!

Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings.

Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

turned off USB and it started. Is the newest version of VB just broken?

[basty_goofy]

Disabling USB does nothing, sadly.
So far nothing has worked:

1. Re-installing (in different folders)
2. Upgrading
3. Enabling and disabling Hyper-V
4. Disabling Defender
5. Removing Malware-Bytes

[socratis]

Disabling USB does nothing, sadly.

Of course it wouldn't! It would be as much help as if were to eat an apple. Completely unrelated!
Now that you have uninstalled your antivirus, please post a new log. You should do that whenever some major change takes place. But before you do that, open an administrator Command Prompt (right-click, run as administrator) and run "sfc /scannnow". See if it helps. If it doesn't, post the log.