Page 18 of 33

Re: Discussion of Problems due to Hardened Security

Posted: 26. Jan 2016, 00:58
by garbage_collected
I'm unable to get 3D acceleration fully working due to an issue loading the AMD display drivers.

In VBox.log:

Code: Select all

00:00:01.335082 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x7 fAccess=0x2 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys: 
00:00:01.335336 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: cached rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x2 fAccess=0x7 cHits=1 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys
In VBoxHardening.log:

Code: Select all

12f4.510: supHardenedWinVerifyImageByHandle: -> -608 (\Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys)
12f4.510: Error (rc=0):
12f4.510: supR3HardenedScreenImage/NtCreateSection: rc=Unknown Status -608 (0xfffffda0) fImage=1 fProtect=0x7 fAccess=0x2 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys: 
12f4.510: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys
12f4.510: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -608 (0xfffffda0)) on \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys [lacks WinVerifyTrust]
12f4.510: Error (rc=0):
12f4.510: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -608 (0xfffffda0) fImage=1 fProtect=0x2 fAccess=0x7 cHits=1 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys

I've tried so far with the official 5.0.14 release, as well as the 5.0.15r105205 test build (although with the 5.0.14 extension pack). Same results. Both logs attached.

Host system is Windows 7 Pro, x64, SP1.
AMD Radeon Crimson Edition drivers v16.1 (clean install)

Other software:
Avast Internet Security 11.1.2245
Malwarebytes Anit-Malware Home (Free) 2.2.0.1024

Thank you!

Re: Discussion of Problems due to Hardened Security

Posted: 28. Jan 2016, 16:28
by Elliott_P
Hi all,

I just started seeing an error this morning.

Yesterday, I upgraded from v5.0.12 to v5.0.14 in the hopes that it would resolve a hangup I've been seeing every few days. After the upgrade, the VM worked fine for the rest of the day. Overnight, Windows updated itself, and this morning, I'm unable to launch the VM. Details:

Windows host: Windows 10 Pro Insider Preview, build 14251 (this is the update that it did last night; yesterday I was on build 11102).
VirtualBox version 5.0.14
Windows Defender is the only AV software running at the moment

The error I got was:
Failed to open a session for the virtual machine QT Development.

The virtual machine 'QT Development' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in '[path]\VirtualBox VMs\QT Development\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}


VBoxHardening.log is attached. The last few lines:

Code: Select all

1d90.108c: Error (rc=-5644):
1d90.108c: Too many regions for VirtualBox.exe.
1d90.108c: Error (rc=-5644):
1d90.108c: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for VirtualBox.exe.
1d90.108c: Error -5644 in supR3HardNtChildPurify! (enmWhat=5)
1d90.108c: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for VirtualBox.exe.
1d90.108c: supR3HardNtEnableThreadCreation:
Any thoughts? It seems like the last thing that changed before it stopped working was the Windows Insider upgrade, which of course changes a lot of stuff. I posted the same question on the Insider forum.

Thanks!

Re: Discussion of Problems due to Hardened Security

Posted: 28. Jan 2016, 17:50
by massi
VBoxHardening.log is attached. The last few lines:

Code: Select all

1d90.108c: Error (rc=-5644):
1d90.108c: Too many regions for VirtualBox.exe.
1d90.108c: Error (rc=-5644):
1d90.108c: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for VirtualBox.exe.
1d90.108c: Error -5644 in supR3HardNtChildPurify! (enmWhat=5)
1d90.108c: supHardenedWinVerifyProcess failed with Unknown Status -5644 (0xffffe9f4): Too many regions for VirtualBox.exe.
1d90.108c: supR3HardNtEnableThreadCreation:
Any thoughts? It seems like the last thing that changed before it stopped working was the Windows Insider upgrade, which of course changes a lot of stuff. I posted the same question on the Insider forum.
Hi, i'm experiencing exactly the same problem with the same log after update windows 10 to the build 14251.

Re: Discussion of Problems due to Hardened Security

Posted: 28. Jan 2016, 21:10
by Jacob Klein
You guys with the "Too many regions for VirtualBox.exe" problem on Windows 10 Insider Build 14251...
... should be posting in the "VirtualBox on Windows pre-releases" forum, located here:
viewforum.php?f=38

More specifically, we (users having the problem, and devs eventually) are monitoring the issue on this post within that forum:
viewtopic.php?f=38&t=75960

Fyi: I have my PCs set up to dual-boot between "Windows 10 Pro x64 Release" and "Windows 10 Pro x64 Insider", for this exact reason - VirtualBox hardening logic breaks very easily when new Insider builds are released. :)

Kind regards,
Jacob Klein

Re: Discussion of Problems due to Hardened Security

Posted: 28. Jan 2016, 22:21
by Elliott_P
Thanks for the links, Jacob! I missed those while searching. I saw that this thread has been open since 2008 and have been really concerned ...

Re: Discussion of Problems due to Hardened Security

Posted: 28. Jan 2016, 22:36
by Jacob Klein
You're welcome.

Re: Discussion of Problems due to Hardened Security

Posted: 29. Jan 2016, 15:24
by massi
Jacob Klein wrote:You guys with the "Too many regions for VirtualBox.exe" problem on Windows 10 Insider Build 14251...
... should be posting in the "VirtualBox on Windows pre-releases" forum, located here:
Kind regards,
Jacob Klein
Thank you for the info Jacob!

Indeed, instead of the dual boot solution, i became very fond of the "Rollback to previous build" function :D

Re: Discussion of Problems due to Hardened Security

Posted: 30. Jan 2016, 17:42
by greyulv
Host OS Windows 7 Enterprise
HardenSecurity Log file :
VBoxHardening.zip
(24.4 KiB) Downloaded 37 times
No installed Anti-Virus

Re: Discussion of Problems due to Hardened Security

Posted: 30. Jan 2016, 17:52
by mpack
@greyulv: Are you running VirtualBox in some kind of compatibility mode? Don't.

Re: Discussion of Problems due to Hardened Security

Posted: 31. Jan 2016, 02:13
by greyulv
mpack wrote:@greyulv: Are you running VirtualBox in some kind of compatibility mode? Don't.
No, I checked the properties and it is not set to run in compatibility mode.

Have installed the following versions of VBox
5.0.2
5.0.4
5.0.6
5.0.8
5.0.10
5.0.12
5.0.14

Cannot start already existing VMs or even start a freshly created on.

Suggestions on what else to test are welcome.

Re: Discussion of Problems due to Hardened Security

Posted: 11. Feb 2016, 12:06
by lithyum
VirtualBox was working fine while i was using windows 7, after the upgrade to windows 10 it breaks forever -_- i also did a fresh windows 10 installation to see if it fix! I disabled the antivirus/run vb as administrator but still it fails. i need to install vagrant boxes...

HOST OS: Windows 10 Pro
Antivirus: ESET Smart Security 8
Protection Software: Advanced SystemCare 9.1(Free)

Re: Discussion of Problems due to Hardened Security

Posted: 11. Feb 2016, 12:34
by socratis
@lithyum
Uninstall your antivirus completely, don't simply disable it. See if that works...

Re: Discussion of Problems due to Hardened Security

Posted: 11. Feb 2016, 20:53
by stefan.becker
First Update ESET to Version 9. Then uninstall Advanced System Care, you dont need this, ESET is enough for Security. Then check again.

PS: I have 2 Machines with Windows 10 and ESET 9 and VBOX. Its working for me.

Re: Discussion of Problems due to Hardened Security

Posted: 13. Feb 2016, 16:12
by lithyum
stefan.becker wrote:First Update ESET to Version 9. Then uninstall Advanced System Care, you dont need this, ESET is enough for Security. Then check again.

PS: I have 2 Machines with Windows 10 and ESET 9 and VBOX. Its working for me.
Didn't works :/

Re: Discussion of Problems due to Hardened Security

Posted: 15. Feb 2016, 17:50
by stives1974
Running Windows 8.1 host. Was running VB 5.0.14 but have since tried every version back to 4.0, none work any longer. I have completely removed McAfee AV and the agent. I have also removed all Windows Updates installed in the last week.

The virtual machine has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).Result Code: E_FAIL (0x80004005) Component: MachineWrap

Failed to open a session for the virtual machine Fedora.

The virtual machine 'Fedora' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'D:\username\VirtualBox VMs\Fedora\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

VBoxHardening.log attached.