We are facing a weird issue regarding vTPM and already opened a support case without much luck.
Our cluster is fully updated and we are even using PC 2023.x build.
If we create a new Windows 11 22H2 virtual machine, the “Get-TPM” cmdlet works fine and BitLocker can be enabled.
If we do the same but with Windows 10 22H2, the cmdlet fails, which means we can’t use the additional security features like BitLocker or even upgrade to Windows 11.
Have you ever seen something similar?
Many thanks!
Bruno Martins
Best answer by bmartins-EMCDDA
bmartins-EMCDDA wrote:
And running the Windows 11 hardware readiness script returns the following:
{"returnCode":1,"returnReason":"Processor, ","logging":"Storage: OSDiskSize=119GB. PASS; Memory: System_Memory=16GB. PASS; TPM: TPMVersion=Undetermined. UNDETERMINED; TpmWmiException Object was not found. (Exception from HRESULT: 0x80090011); Processor: {AddressWidth=64; MaxClockSpeed=3000; NumberOfLogicalCores=2; Manufacturer=GenuineIntel; Caption=Intel64 Family 15 Model 6 Stepping 1; }. FAIL; SecureBoot: Capable. PASS; ","returnResult":"NOT CAPABLE"}
I’m having a similar issue where I can build new Windows 11 systems no problem, but if I try to upgrade a Windows 10 with vtpm it fails with “incompatible processor” (even though the processors are on the HCL and I’m building new systems on the same hardware without issue). If anyone figures out the details for this one let me know…
I’m having a similar issue where I can build new Windows 11 systems no problem, but if I try to upgrade a Windows 10 with vtpm it fails with “incompatible processor” (even though the processors are on the HCL and I’m building new systems on the same hardware without issue). If anyone figures out the details for this one let me know…
Have you also tried opening a support case?
I did and for the moment, the support agent says everything is fine with my configuration and would double check it internally.
