Virtualbox 6.1 - Windows 10 Pro 1909 Hangs at startup after applying MS KB4524570

[aderlopas]

Hello,

I have a Windows 10 Pro 64-bit guest 1909 running under Virtualbox 6.1 running on Windows 10 Pro 64-bit Host.
Everytime KB4524570 is being installed on the guest windows 10, either by automatic update or by the MSI downloaded, after the first restart it hangs on the Virtualbox screen.
From there I need to force close the machine 3 times for automatic repair to take over, remove the update and start windows normally.

Any ideas on how to solve this? Attaching the virtualbox log.

[scottgus1]

I don't see anything in the log that is egregiously causing a Windows Update to fail in the guest OS.

Typically, if the guest Virtualbox window is open and the guest OS is doing something similar to what that guest OS would do on a physical PC, then Virtualbox is working and you should try to solve this as if the OS is running on a real PC. In other words, Google the issue, don't Virtualbox-forums it.

To clear up any possible conflict with Virtualbox, uninstall the Guest Additions, so the guest OS does not know there's a hypervisor in place. That's all the farther I could suggest about getting this update installed. After that, Google will be your friend.

[scottgus1]

A guest settings suggestion, probably not causing the update issue, but you should know it anyway:

00:00:02.854710   NumCPUs  <integer> = 0x0000000000000004 (4)
00:00:04.124252 CPUM: Physical host cores: 4

Virtualbox does not benefit from hyperthreading, and you have all four physical host cores ready to be used in the guest. If your guest goes full-throttle on all four cores, host performance and stability may suffer. Windows 10 gets by just fine on two cores.

[aderlopas]

Thanks for your reply and suggestions.

I did try to uninstall the guest addons and apply the patch but it again failed to boot.

As for the number of cores, when I set to 1 it goes terribly slow, and since I have 8 available, I just set it to the maximum it allows me without producing a warning, and that is 4.

I don't know whether this is a virtualbox or microsoft windows problem, however I have noticed that it hangs at doing the second hyperV call to address:

GIM: HyperV: Queried extended hypercall capabilities 0x1 at 0x0000000000007000

When the automatic repair takes control I notice that the first HyperV call address changes and is not the same as it used to issue originally:

GIM: HyperV: Queried extended hypercall capabilities 0x1 at 0x00000000007b2000

But it uses another address instead. After that, then the second call to the below address succeeds and Windows load normally and start uninstalling the windows update applied:

GIM: HyperV: Queried extended hypercall capabilities 0x1 at 0x0000000000007000

[fth0]

00:15:03.747263 IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)

This is a known, as yet unsolved problem, see viewtopic.php?f=2&t=95783.

As for the number of cores, [...], and since I have 8 available

No, you have not, see Intel(R) Core(TM) i7-8665U. If you afterwards read the previous comment from scottgus1 again, it maybe makes more sense to you.

[aderlopas]

Hi,
Thanks for your reply. Now I begin to understand why the remaining 4 are in Pink in the options Thanks for explaining!
For the problem I will be waiting for the case resolution then.

[pt58]

There are a couple of threads running about this problem with MS KB4524570 on recent Intel CPUs.

I don't see the problem on my i7-6700k system so I was wondering if it might work to spoof the CPU ID in the problem guest by running the following in a command prompt on the host:

"C:\Program Files\Oracle\VirtualBox\VBoxManage" modifyvm VMname --cpu-profile "Intel Core i7-6700K"

Obviously change the VMname to match the name of the problem Win10 VM.

I have no idea if this will work because I don't have access to a system with a recent Intel CPU.

EDIT:
Unfortunately, I made a typo in the command line above which would result in the following error when trying to run the VM after executing the command:

CPUM internal processing error #1. (VERR_CPUM_IPE_1).

Aplogies if anyone tried this and got the above error.
I have corrected the command above .

Also note that if the Vmname contains any spaces, you will need to enclose the name in quotes, eg. "my vm name"

[mga]

Hello,

You should install VirtualBox 6.0.6 until the bug is solved.