Virtual Box Guest lock up after forced Windows 10 update

[Michael37]

Team

Sorry if this may have been broached before. I attempted to read forum post prior to posting this question.
Host machine: Win10 Ver 1703 build 15063.483
Virtual Box 5.2.9

After Microsoft forced the update and rebooted my machine, my existing VM are unstable. Some I can get to boot but eventually will fail. I do not believe it to be guest specific but with VB Manager. If I attempt to start ANY existing guest and immediately try to access the options in the device menu, the guest becomes not responsive and will eventually give the error message below.

I rolled back as many of the updates as I could. There are two that will not. KB4049011 & KB 4025342. Performed Full system boot scan on host. Booting guests in safe mode experience same result. Any guidance will be greatly appreciated.

VirtualBox: VirtualBox.exe - Application Error

The instruction at 0x0000000067258A90 referenced memory at 0x0000000000000008. The memory could not be read.

Click on OK to terminate the program

[mpack]

VirtualBox 5.2.9 is a test build, why are you using that?

OTOH Win10 1703 build 15063.483 is even older than the "slowest of slow lanes" update channel we use at work. So presumably the update that killed you wasn't a feature update, it was just maintenance.

Do all the affected VMs use 3D acceleration? Are they the same OS or a variety?

Pick one VM and provide both a hardening log and VM log for it: With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" and "VBoxHardening.log" (no other files) to a zip, and attach the zip here.

[ohaya@yahoo.com]

I just moved some guests over to my VBox (latest 5.2.8 r121009) and all of them crashed shortly I started them. Is this a 5.2.8 r121009 version problem?

Jim

EDIT: My Windows is: Windows 10 Pro, Version: 1709, Build: 16299.309
EDIT 2: I have a mix of Window 2012 R2 and CENTOS 6.9 guests - all crashed

[ohaya@yahoo.com]

Hi,

FYi, I uninstalled the exensions and the VBox 5.2.8 and re-installed VBox 5.2.6-120293 and the extensions and the guests are so far not blowing up.

[Michael37]

VirtualBox 5.2.9 is a test build, why are you using that?

OTOH Win10 1703 build 15063.483 is even older than the "slowest of slow lanes" update channel we use at work. So presumably the update that killed you wasn't a feature update, it was just maintenance.

Do all the affected VMs use 3D acceleration? Are they the same OS or a variety?

Pick one VM and provide both a hardening log and VM log for it: With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" and "VBoxHardening.log" (no other files) to a zip, and attach the zip here.

I reapplied the patches and it updated the Host Win Version to Win 10 1703 15063.966.

I am running 5.2.9 thinking it might have had a fix.

All the guest OS's are Windows based an none have 3D acceleration enabled.

I have attached both the hardening and vbox

[BillG]

I have attached both the hardening and vbox

Really? Where ?

[Michael37]

Files attached.

[Michael37]

Hi.. Just checking to see if anything might have been found in attached log files?

[mpack]

There's lots of stuff in the logs, which were truncated (i.e. open files grabbed while the VM was still running) so not as useful as one could wish. I see Avast, and some kind of runtime security, and maybe encryption too?

[Michael37]

@mpack

Anything that could point to why the VM will not function correctly?

I am suspecting it was some KB update. I rolled back all that I could and still no luck

[mpack]

Have you read the hardening faq? Everything we know about how to troubleshoot the issue is given in that.