Forum Discussion
TPM 2.0 Windows 11 Pro Insider Preview Canary Build 27871 seems to be acting crazy persay...
Hello to all, I have been experiencing some pretty weird stuff regarding TPM 2.0 and just so happens it is enabled totally in the BIOS already also.. I have an AMD Ryzen 7 7700X Setup as well btw.. So, I do have some screenshots to better show you all what I mean anyways.. Anyways, Have a great day and stay safe also!.
4 Replies
Hello there, Thanks for the reply btw. Anyways, I have one more question as well.. Do you think it could be due to secure boot not being enabled at the time of the update to this build in question?? Just wondering anyways.. So, Have a wonderful day ahead and stay safe also.! Also, It seems that only sometimes under device security in that case that it seems that it would not detect tpm 2.0 at all and in that case I was using the FTPM or in other words Firmware TPM 2.0 on the CPU.. Anyways, Good News is at least is that I think Secure Boot being enabled in the BIOS at the time of installation of the Canary Build for Windows 11 Pro Insider Preview seems to have fixed it anyways although I will have to do some more testing to verify if I am correct on this matter.. But, bad news is my main Computer is down for now and won't be back up until at least Tuesday anyways!!.. Bummer!!..
If you have specific screenshots or error messages, sharing those can help diagnose further. Also, let me know exactly what "acting crazy" means—are there error messages, boot issues, TPM modules not recognized, or weird behavior during updates?
Hello there, Thanks for the reply btw.. Is it possible that if secure boot is not enabled that it would appear that way anyways perhaps?? Just wondering and all.. Mainly because I enabled secure upon reinstalling Windows 11 Pro 24H2 clean install route via reformatting and reloading and that believe it or not seems to have fixed my TPM issue at least on Windows 11 24H2 Pro altogether here!.. Anyways, Thanks again and have a great day ahead and stay safe out there..!!
In the Canary build, the anomalous behavior can be resolved by clearing and reinitializing the TPM through the TPM management feature in the Administration tool.
