Windows 11 on Intel Core i7-7820HQ

[kaz219]

It seems upgrading to Windows 11 is slightly more complex than Windows 10 and I'm stuck.

So far I have done the following to be able to upgrade my Windows 10 64bit VM to Windows 11:

1. Switched to GUID partition map
2. Enable UEFI by adding the VMX flag firmware = "efi"
3. Added TPM 2.0 by adding the VMX flag managedVM.autoAddVTPM = "software"

Now the Heath check complains (only) about the Intel Core i7-7820HQ of my MacBook Pro 2017. According to Microsoft web page, it is only supported for "select devices" and the MacBook is of course not included. Seeing the requirement is for "modern drivers" with Declarative, Componentized, Hardware Support Apps (DCH), my first question is:

Do the drivers emulated by Fusion meet these requirements?

Secondly, I went ahead anyway without waiting for the answer to this question and added the DWORD AllowUpgradesWithUnsupportedTPMOrCPU.

But unfortunately the Windows 11 upgrade assistant continues to state that my PC does not meet the minimum requirements and the PC Heath Check app keep on saying the CPU is unsupported.

Hence, the second question: what am I missing?

[wila]

Hi,

Make sure your Windows 10 is booting via UEFI and not BIOS.

Note that just changing that in the settings won't work, you also have to migrate your disk from MBR to GPT, which by itself is probably the biggest problem.

See also here for more details:
https://communities.vmware.com/t5/VMware-Workstation-Pro/Convert-Windows-11-BIOS-VM-to-Windows-11-Co...

edit: Oh and about that autoaddvtpm option, please read the following as there's some things you should know before using that -experimental- option on a production VM.
https://www.vimalin.com/blog/what-you-should-know-about-vmwares-experimental-vtpm/

edit 2: ok.. I need to step away from the screen.. somehow I missed your point 1) and point 2) ugh..

--
Wil

[bluefirestorm]

The i7-7820HQ is the same CPU as that is on the Microsoft Surface Studio 2. That's probably the main reason why it is in the official list.

You can install and run the PC Health Check app and it will tell you exactly what requirement is not satisfied.
https://aka.ms/GetPCHealthCheckApp

It might be that with the Fusion 12.x bug that the VM is only seeing one core.

You might have to add the following line to the vmx configuration

cpuid.coresPerSocket = "2"

For the vTPM experimental feature to work and added, close the Fusion UI app first and open it again.