I'm aware this is probably more standard Microsoft incompetence than vmware's fault, but I can't update Windows because it insists that the latest Windows version doesn't support VMWare Workstation Pro, which all of vmware's resources say is false. Even after completely uninstalling VMWare Workstation Pro, I still get this message when trying to update:
I think VMWare may want to raise with Microsoft that they have broken VMWare Workstation Pro for those updating to the latest Windows version
Hi,
What version of VMware Workstation Professional is that?
--
Wil
I got the same problem:
I am using the most recent version workstation Pro 16 on Windows Server, but a virtual machine sends this message - and it is impossible to upgrade the VM to Windows 10 20H2.
Has somebody found a solution so far? Thank you!
Hi Rorrr,
Can you verify that the VM is using the latest virtual hardware version?
--
Wil
Thank you for your answer.
Sorry, maybe this is a silly question: but what do you mean by "virtual hardware version", where can I find the version number? I cannot find a version number under the VM Settings.
This machine runs on VMware Workstation 16 Pro (16.1.0 build-17198959).
Hi,
No worries.. that's not a silly question.
As hardware for a virtual machine is "emulated" it is specific for a VMware Workstation version. Newer versions that expose more functionality get new virtual hardware. In order for VMware Workstation to keep track of what kind of hardware functionality is exposed to the guest, VMware has figured to attach versioning to their hardware functionality. Hope that makes sense.
You can see the hardware version used in the Library overview.
Eg.
In the screenshot above it is version 11.x
You can change the hardware version by right click in the list on the left (not in the screenshot) then choose Manage -> Change Hardware compatibility and follow the steps in the wizard.
Note that the VM has to be shut down, not suspended, in order to be able to change the virtual hardware configuration.
As this is a hardware change and Microsoft Activation logic can trigger on hardware changes it is always recommended to make a backup before changing something like this.
A snapshot would also work.
Hope this helps,
--
Wil
Thank you, wila. Great answer - this did the job.
1. Shut down the machine.
2. Save the virtual machine (only to be on the secure side)
3. "Upgrade this virtual machine" - Wizard
4. Upgraded to virtual machine compatibility 16.x.
5. WIndows 10 20H2 update now started without problems.
Thank you again ![]()
