Since March windows 11 update TPM change issue

Soldato
Joined
18 May 2010
Posts
22,897
Location
London
As with many of you I use the AMD ftpm feature to meet the requirements of Windows 11 to use TPM 2.0.

However MS have changed something with the latest March Windows 11 update.

Both my machines are telling me I do not have a TPM device installed and yet it also says I do and it is working.

See the screen shots below:

1.png



2.png

I am able to press the dismiss button and the warning goes away it just seems a little weird.

I imagine many of you will hit this issue when you apply the March 2023 windows 11 updates.

I thought it could be something to do with the beta bios I am using with the Agessa 1.0.0.8 but that was working fine previous to the March updates.

And my other pc with the same problem is not on this beta bios so its definitely the updates that changed something.
 
Last edited:
Noticed this too on my Steam Deck with windows 11. I just assumed it's because I disabled core isolation so it was for some reason prodding me to turn it back on. Secure boot bug makes sense though since the Deck doesn't have any keys.
 
Dunno if related but there is a massive bug with autopilot.dll with one of the more recent updates related to sign in and TPM attestation - can cause quite a lot of underlying problems - system lag, crashing, TPM problems, etc.
 
Dunno if related but there is a massive bug with autopilot.dll with one of the more recent updates related to sign in and TPM attestation - can cause quite a lot of underlying problems - system lag, crashing, TPM problems, etc.

Interesting to know... I say that only because, I think, since the latest update that has caused the TPM issue, my PC upon shut down is taking at times much longer to do so, that's to say the keyboard has stopped illuminating and the monitor blank and going into energy save mode. This has only been happy over the last week or so, fortnight at best.
 

I dont have this issue because I used Norton 360, it seemed Windows Security caused this bug.

I thought Local Security Authority protection is a new feature introduced in Windows 11 Canary build 25314.

 
Back
Top Bottom