Procedure to Update an Infineon TPM Chip I got Infineon software compiled for Windows plus some common BIN files here: https://download.schenker-tech.de/package/infineon-tpm-firmware-update/ I copied the unzipped Schenker folder to the desktop (with an x suffix). The Schenker .BAT files didn't work for me so I used info from Silvenga to decide how to proceed: https://silvenga.com/upgrading-firmware-infineon-tpm/ >>> Clearing the TPM clears all the keys it holds - so do what is needed to avoid loss of data. >>> This worked for me but I can't say if it will work for others. If you have doubts, don't proceed. (Execute PowerShell as Administrator throughout.) Disable-TpmAutoProvisioning Clear-Tpm (If you attempt to update the TPM without disabling it in BIOS, it will fail. However, this will verify that TPMFactoryUpd sees the chip and whether it will update it once you disable the TPM in BIOS.) (Disable TPM in UEFI/BIOS here!!! Then ReBoot to Win11 and run PowerShell again) (I used "copy path" to point PowerShell to the desktop Schenker folder.) Set-Location "C:\Users\John\Desktop\CallTpmBatx" (Replace the BIN file at end of this line to match the firmware in the TPM. This line does the update) .\TPMFactoryUpd.exe -update tpm20-emptyplatformauth -firmware TPM20_5.0.1089.2_to_TPM20_5.62.3126.2.BIN (Update takes less than 1 minute. ReBoot computer and Re-enable TPM in UEFI/BIOS. ReBoot Win11) (After updating and re-enabling TPM:) Enable-TpmAutoProvisioning Clear-TPM Then ReBoot Win11 again... Verify TPM has a good version of firmware using the .ps1 script found here: https://msrc.microsoft.com/update-guide/en-us/vulnerability/ADV170012 This script seems to have a bug - it always says the firmware version has changed and you need to reboot. ======================================================= Info about the Infineon program: https://github.com/crass/infineon-firmware-updater/blob/master/Doc/TPMFactoryUpd_UserManual.pdf There are more BIN files for other firmware versions here: https://premamod.wordpress.com/ The password is in the Disclaimer.