Page 1 of 1

VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 19:53
by gorn1001
Hi i have problem with VB, I cant start any machine, i tried few versions 5.0, 4.3.26, 4.3.28, 4.3.14 and few more, all giving the same error, I am using Win7 x64, with Phenom II X4 processor, SVM mode is Enabled, any ideas?
err.jpg
err.jpg (37.17 KiB) Viewed 1611 times

Re: VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 20:06
by Perryg
Did you read the message and if so do you think we would know more than you if we did not read the file mentioned?

Re: VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 20:14
by gorn1001
here are errors from log file:
f2c.788: Error (rc=0):
f2c.788: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=3 \Device\HarddiskVolume2\Windows\System32\shell32.dll
f2c.788: Fatal error:
f2c.788: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\Windows\system32\SHELL32.dll' / '\??\C:\Windows\system32\SHELL32.dll': 0xc0000190
220.334: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1969 ms, the end);
684.e0c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2586 ms, the end);

Re: VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 20:21
by Perryg
Just for completeness could you post the complete startup.log ( as an attachment )?

Re: VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 20:29
by gorn1001
Cant upload it because file is too big 233kB when limit is 128

Re: VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 20:30
by Perryg
Even compressed?

Re: VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 20:31
by gorn1001
VBoxStartup.rar
(14.07 KiB) Downloaded 10 times

Re: VirtualBox cant start any virtual machine

Posted: 1. Jun 2015, 20:43
by Perryg
It looks like you have a corrupt certificate store, but it could be a bad monthly hotfix that has been happening for the last few months from Microsoft.

You would need to either fix this or you can revert to VirtualBox 4.3.12.