After virtualbox update, Win10 VM will not boot

Yesterday I updated my 42.2 system using YAST GUI.

One of the updates was to virtualbox 5.1.18-19.5.1

from /var/log/zypp/history:
2017-04-12 20:25:28|install|virtualbox|5.1.18-19.5.1|x86_64|root@PVE-LinuxSRV7|openSUSE-Leap-42.2-Update|adbc2e8f778b9202954ca11a92d1b0288c02723c59170059dfdf8fca8ef9ec2c|

I now find that my Win10VM will not boot.
I get the Win10 login screen, enter my password, then Win seems stuck in startup(the spinning balls).

Any ideas on how to debug?

Hmmm, interesting development.
I tried starting the Win10VM again, as before got the Win login screen, entered password and watched the spinning balls for almost 3 minutes.
I could see some activity flashing on the VMHDD and Network icons, moderate, not heavy.
Then Win10 finally started up.

My VM runs purely on a fast SSD, usually boots almost instantaneously.

Given the early hour (EDT), I am wondering if Win10 was having trouble with password authentication with the MS servers.
Just a wild guess…

But wait, now I see that some update has been pushed to Win10, it is now restarting…

openSUSE Leap 42.2 package checklist:

  • virtualbox and virtualbox-qt: version 5.1.18-19.5.1
  • virtualbox-host-kmp-default: version 5.1.18_k4.4.57_18.3-19.5.1

Oracle VirtualBox checklist (download from <>:

  • Oracle_VM_VirtualBox_Extension_Pack-5.1.18-114002.vbox-extpack
  • VBoxGuestAdditions_5.1.18.iso (only for MS Windows in the VM)

[HR][/HR]After the Leap 42.2 VirtualBox update today, Windows 10 Home (Anniversary Edition) in the VM booted OK – it’s currently downloading the April 11, 2017—KB4015217 (OS Build 14393.1066 and 14393.1083) Windows 10 Version 1607 update – possibly the famous “Creator’s Edition” . . . >:)

Will update this thread later once the VM has rebooted . . .
I do not have any MS authentication servers – it’s a simple stand-alone system running in a VM on this Linux Laptop.

Win10 got a massively large update a month ago, and another larger than usual update this past week.
Depending on your settings, when your system might have downloaded this month’s updates and how often you reboot, you may have experienced a one-off event (at least unrelated to VBox).


By the end of the day I had concluded that events outside my control (Windows update activities) were the culprit.
Same day, I had a similar experience on a totally unrelated Win 7 platform.

Must have been some nasty bugs that needed extermination.

Two days later, I was back to 10 second boot time.

Installed Win7 in a VirtualBox VM recently it took 9 hours to fully update all the while running at a crawl. Wonderful OS Windows… NOT! I actually had to pay money for this treatment:P

My commiserations: I mistakenly purchased a Windows 10 Home small system builder license for a dual-boot Lenovo G505s laptop (AMD) to replace the OEM Lenovo Windows 8.1. Everything installed fine and dandy until the Windows 10 “Anniversary” update installed: . . . crash . . . fallback . . . automatic (Windows 10 Home) update re-install . . . loop until Doomsday . . .

I gave up; installed Leap 42.2 native (without dual-boot); bought a Windows 10 Home “full” licence (box with a usb stick); downloaded the DVD .ISO image from the Redmond folks; installed the Windows 10 in an Oracle VirtualBox . . . >:)

Why two licences?

  • The small system builder license is a “one-shot” licence – installing in a VM on the same hardware doesn’t count . . .

On this machine I decided that I had not enough time troubleshooting and I uninstalled Virtualbox as well as any Windows images completely. Initially I was quite frustrated and went downloading Microsoft Hyper-V Server 2016 which made me even more confused. I ended up reinstalling Virtualbox and loaded an evaluation WinDev1704Eval.ova instance instead. Ain´t pretty, but did not have much choice to begin with.

just a note for those reading - you can download (from MS) and use win 10 without a licence (legally). I have been using for +6 months and the only restriction is gui customisation which you can work around easily.

No matter what version of Windows you install (and format including pre-built like ova) from XP to Windows 10, you’ll need to run Windows Update immediately and go through the hour-plus updating to pick up critical fixes for the Wannacry exploit (fix released Mar 2017) plus misc others (including a critical Dropbox fix in May 2017). Microsoft has released patches which can be installed manually or through Windows Update for every Windows XP through Windows 10.

These are <major> fixes, the March fixes took over an hour to install, the April fixes took nearly as long and the May fix was more normal, taking about 15 minutes to install. I don’t know if you installed all the fixes at once if any time can be saved, and a reboot is required to install each month’s updates.

The Wannacry exploit is supposedly a particularly critical exploit based on code supposedly stolen from the NSA, then when an auction for the code failed was released for free on the Darknet to prove that the batch of stolen exploits were valid. Then someone (as of today speculation is centering on NoKorea) turned the exploit code into the Wannacry Ransomware exploit. The exploit also mutates, to avoid AV detection.

So, this is no ordinary Windows problem. If you don’t patch, then you put yourself at risk at least for having your personal files encrypted.