Shut down the VM and edit the vmx configuration. It is probably missing this line.
cpuid.coresPerSocket = "n"
It is best that the value of n is an even number (the only exception being 1).
The other parameter numvCPUs will affect the number of virtual sockets inside the Windows VM. For Windows Home, only 1 virtual socket is supported and 2 virtual sockets can be supported on Windows Professional.
So numvCPUs / cpuid.coresPerSocket should be equal value if your VM is Windows Home. Example
numvcpus = "4"
cpuid.coresPerSocket = "4"
For Windows Professional you can have
numvcpus = "2"
cpuid.coresPerSocket = "1"
or
numvcpus = "4"
cpuid.coresPerSocket = "2"
as 2 numvCPUs / 1 coresperSocket = 2 virtual sockets or 4 numvCPUs / 2 coresPerSocket = 2 virtual sockets
You don't indicate what version of Fusion you are using.
If you plan to add a virtual TPM, Fusion 12.x has an experimental feature to only partially encrypt the VM. It is experimental so there are issues (you won't be able to transfer and run the VM on another host, the password is not known and it is difficult to remove the partial encryption).
If you will encrypt the entire VM to add the virtual TPM (this is the standard feature since Fusion 10.x including the virtual disks in its entirety), the virtual disks should be preallocated. By definition, encrypted virtuald disks won't be able to write contiguous zeroes so you won't be able to shrink them (the Clean Up function in the General settings) and it will just continually grow.
You also of course can use the registry entries to bypass both the CPU and TPM check on the Windows 11 upgrade.
