Windows v1809 broke VirtualBox compatibility

Discussions related to using VirtualBox on Windows hosts.

Windows v1809 broke VirtualBox compatibility

Postby DifferentFun » 7. Dec 2018, 20:12

Hello everybody.
Running a i9 7940X with X299 Ultra motherboard here.
I've been using VirtualBox for a long time, since I updated to the last Windows 1809. Now it is totally unusable.
I've tried to use the last 5.2.23 experimental build too, it changed nothing.
The VM runs, it goes for loading the OS(es), in this case it is Windows 10, then boom, it freezes everything.
I have to open the task manager and kill everything VB related to run it again.
I disabled Hyper V, DeviceGuard and even UAC.
No antivirus installed here, no anti-malware, VT enabled from Bios (which I updated to the last version too with ALL drivers!).

Curious thing: If i set 4 CPUs, the Vbox goes to launch Windows, and it hangs just after the login.
If I raise the CPUs numbers, even to 5, Windows VM won't even boot. Stuck at Windows Logo boot screen.

I've tried even all options in paravirtualization, like disabled, minimal, kvm... nothing changed.

Oh, the guest got assigned 4GB over a total of 40GB RAM (which I tested with memtest, that are fine too) from host machine.

What could it be the problem? VBox not supporting yet Win1809 or what? I'm getting crazy behind this.

Note, before the Win1809 update, it was working like a charm. :(
Posts: 1
Joined: 7. Dec 2018, 20:05

Re: Windows v1809 broke VirtualBox compatibility

Postby socratis » 7. Dec 2018, 22:09

I take it that you re-installed VirtualBox, since you're talking about 5.2.23...

DifferentFun wrote:If i set 4 CPUs ... If I raise the CPUs numbers, even to 5
How about lowering it to 2?

We need to see a complete VBox.log, from a complete VM run:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
Site Moderator
Posts: 23883
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 32 guests