is configured to start with TPM (Trusted Platform Module) enabled but the TPM-related info cannot b

Intel Mac, current Parallels.
I want to do the Windows 11 upgrade, so I have added TPM to my Windows 10 image. Now when I boot, I see:
"...is configured to start with TPM (Trusted Platform Module) enabled but the TPM-related info cannot be read."
I have looked through the KB articles, but didn't find the one that addresses this. Does someone have a pointer for what I should search for? I have found no hits on this phrase.
Thanks.

 

Same problem. Sure would like to know how to "simply" add a TPM to the VM and have it work. If you choose "Start anyway" you get a 0xc0000428 error from Windows 11 booting.

 

Here you go...

 

Maybe it's worth noting that this is an insider build - perhaps that's part of the problem?

 

Is there a reason you're doing the upgrade path instead of installing the available ISO on MSFT's download page? I installed Windows 11 just fine using that.

 

The same reason everyone hates doing that - reinstalling everything again.

 

Fair enough, I just prefer 'clean installs' with new OSes like that, but that's not everyone's case of course.

 

I just saw the Insider build note, so Apples and Oranges for my use case. I guess I Could try what you're attempting though to have another data point.

 

I guess, reading what Parallels has said about adding the TPM - it should just work and boot OK and find it and then begin working. Alas, the boot error. I can remove the TPM and it continues to work still as before. I'm thinking it's because it's an insider preview build, maybe, so for now until the next proper RTM build is released I'll have to make do without the TPM. If it still has issues then I'll consider a fresh install.

 

Running 2019 MBP, Host is Monterey 12.4, Parallels 17.1.4 / Desktop Edition (not pro)

So I did manage the following, but none of it resulted in any errors. :/

1. Cloned most current version of my Win10 (vanilla) 21H2 build;
2. Added TPM;
3. Signed into MSFT account, activated the Dev path;
4. Used Windows Update to trigger the Win11 IP 10.0.15101.1010 (rs_prerelease) download;
5. Upgrade performs without complaint / assistance;
6. Shutdown VM;
7. Removed TPM;
8. Started VM;
9. Shutdown VM;
10. Added TPM;
11. Started VM;

 

Same here with a Win11 ARM VM on current macOS Monterey build with Parallels Version 17.1.4 (51567).

1. Create a fresh VM without a TPM module attached because I need to share the VM with others (with different keychain)
2. install OS, archive it to store as a template
3. import the VM, boot it: everything is fine
4. Add TPM Module to VM and try to boot:
5. "Win11ARM01" is configured to start with TPM (Trusted Platform Module) enabled but the TPM-related info cannot be read.
   What do you want to do with "Win11ARM01"?
6. 

Is this a BUG? Adding a TPM should just work, right?

Best regards, Flo.

 

Just double checked with "prlctl list -a"command:

Everything seems to be there, right?

 

Log shows:
08-05 11:12:22.814 F /LocalDevices:8067:4c165/ [TPM NVS] TVNS - invalid signature
08-05 11:12:22.814 F /vm:8067:4c165/ Sending question = PRL_WARN_TPM_NVRAM_INVALID