Unable to start VM
Unable to start VM
I am unable to start my Windows Virtual Machine. As usual, everything "seemed" to be good with my last shutdown. I "save machine state" so its easier to bring up. However, today it wouldn't start. I consolidated snapshots, hoping that would help, but it still failed. I have attached todays logs. Thanks!!
- Attachments
-
- VBoxStartup.zip
- Today's startup log (zipped)
- (13.16 KiB) Downloaded 6 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Unable to start VM
Did you do Windows Updates on your host between the last run of your guest and this run?
There are lots of "Lacks WinVerifyTrust" posts in the log pointing to common Windows files. I think this means your PC has one or more Windows Updates that have damaged the authenticity certificate database that the OS keeps. Virtualbox uses these certificates to check if the files are not hacked before VB allows the files to influence VB. Since the Windows Updates have damaged the database, VB can't know if the files are good and so won't run.
These links were posted by Mpack in another thread, for the two known updates that damaged the database. Microsoft apparently has a work-around for one of them:
KB3004394
http://www.infoworld.com/article/285801 ... fende.html
http://www.infoworld.com/article/285911 ... 04394.html
KB3045999
http://www.infoworld.com/article/291459 ... albox.html
There are lots of "Lacks WinVerifyTrust" posts in the log pointing to common Windows files. I think this means your PC has one or more Windows Updates that have damaged the authenticity certificate database that the OS keeps. Virtualbox uses these certificates to check if the files are not hacked before VB allows the files to influence VB. Since the Windows Updates have damaged the database, VB can't know if the files are good and so won't run.
These links were posted by Mpack in another thread, for the two known updates that damaged the database. Microsoft apparently has a work-around for one of them:
KB3004394
http://www.infoworld.com/article/285801 ... fende.html
http://www.infoworld.com/article/285911 ... 04394.html
KB3045999
http://www.infoworld.com/article/291459 ... albox.html
Re: Unable to start VM
Scottgus - "You da man" - Since I didn't feel like playing with uninstalling updates, I reverted my host OS to a snapshot from a few days ago. This would (and did) replace system files, while leaving everything else. After the system recover and reboot, the VM came on as planned.
Thanks again!
Thanks again!
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Unable to start VM
No problem. You can block the updates in question if you figure out which ones did it. I'd first check against the two KB numbers mentioned above to see if either of those updates were installed and block them. Then I'd install the other updates one at a time, reboot, and see if Virtualbox starts.