It’s a freshly created win 7 pro 32-bit vm on a VirtualBox. However the windows update only worked before the latest two. It gets “the processor is not supported together with the Windows version that you are currently using” error. The host OS is Ubuntu 18.04, process is i7 7700HQ.
On another host it updated to the latest KB3042058, following a KB4534310, and a KB4536952. On the problematic vm, it gets stuck at KB4536952 with the error.
One of two solutions suggested by a virtualbox forum topic is to change inside a windows system file as discussed on the virtualbox box forum “Concern: Microsoft block win7/8.1 update with new CPU“. The another of the two is to run these two commands:
vboxmanage modifyvm "virtual machine name" --cpuid-portability-level 1
vboxmanage modifyvm "virtual machine name" --cpuidset 80000004 372e3220 7a484730 00000000 00000000
I did run the two commands, the guest win 7 still reports the same system processor “i7 7700HQ” as it used to, and the update still fails the same as before.
Another post on this SE site suggests to use only a valid cpu profile. A list can be found on a virtualbox forum topic “specifying the processor type the vm sees. The two commands are changed to:
vboxmanage modifyvm "virtual machine name" --cpuid-portability-level 1
vboxmanage modifyvm "virtual machine name" --cpu-profile "Intel Core i5-3570"
Again it is not working. I also tried to change "Intel Core i5-3570" to "Intel Core i7-2635QM". In both cases, the guest OS will see the different processor types as set by the command, but the update still fails the same as before.
Any idea how to fix this?
Another data point is that on both the two win 7 vm’s when it is initially created, it fails windows update for a few times. On one of them it updated overnight when left alone. Then I clicked through multiple updates till the latest is done. On the second I just clicked to check for updates it worked for a bunch of successful updates till it fails. Not sure why these two are so different.
Go to Source
Author: minghua
