Windows 10: Fix Alert! TPM device is not detected error on Dell computers

​

TPM or Trusted Platform Module is a security chip on the motherboard which stores all passwords and security-related data. It offers hardware-based, security-related functions if you are receiving an error message Alert! TPM Device Is Not Detected, then this post will help you resolve the problem. Before we go ahead, you need to make sure […]

This article Fix Alert! TPM device is not detected error on Dell computers first appeared on TheWindowsClub.com.

read more...

 

Windows 10 v.1709 Error 0x8000FFFF & TPM is not usable?

We appreciate the update that you provided. Upon reviewing the steps you've mentioned in the past, it seems you haven't tried uninstalling the TPM driver yet. An outdated version of this driver can directly affect the Hardware Troubleshooter and cause the 0x8000FFFF
error. To uninstall the TPM driver, follow these steps:

• Right-click Start.
• Click Device Manager.
• Expand Security devices.
• Right-click Trusted Platform Module 1.2 and choose Uninstall.
• Restart your computer and let Windows automatically reinstall the driver.

Let us know if the error disappears after following these steps.

----

If you think this was useful, you may "mark it as an answer" to help those who are facing the same problem.

 

Windows 10 devices now requires hardware encryption/TPM

Stolen from Sweclockers, but it's in swedish.

So from now on devices (OEM built) needs a TPM module. Relevant bit:

Pretty interesting, but there's tons of questions I guess. I don't actually now anything about how TPM works, just that it's hardware, meaning the key is stored in a physical chip and that the decryption has to run through this chip. But I have no idea how let's say biometrics is tied to this. Or what the implications will be, or what exactly is encrypted. The entire storage or just the log in details as such?

 

TPM Console Error 0x8007007A

PS.

1. I've also just tried to uninstall the TPM device, like suggested
   here.
2. I've also just tried

1. 
   

Code:

$tpm = gwmi -n root\cimv2\security\microsofttpm win32_tpm$tpm.SetPhysicalPresenceRequest(6)

as suggested
here and
here.

Nothing changed.

Here's some additional info, just-in-case:

Code:

PS C:\WINDOWS\system32> gwmi -n root\cimv2\security\microsofttpm win32_tpm__GENUS                     : 2__CLASS                     : Win32_Tpm__SUPERCLASS                :__DYNASTY                   : Win32_Tpm__RELPATH                   : Win32_Tpm=@__PROPERTY_COUNT            : 10__DERIVATION                : {}__SERVER                    : MY-PC-NAME__NAMESPACE                 : root\cimv2\security\microsofttpm__PATH                      : \\MY-PC-NAME\root\cimv2\security\microsofttpm:Win32_Tpm=@IsActivated_InitialValue    : TrueIsEnabled_InitialValue      : TrueIsOwned_InitialValue        : TrueManufacturerId              : 1112687437ManufacturerIdTxt           : BRCMManufacturerVersion         : 7.11ManufacturerVersionFull20   : Not SupportedManufacturerVersionInfo     :PhysicalPresenceVersionInfo : 1.0SpecVersion                 : 1.2, 2, 1PSComputerName              : MY-PC-NAMEPS C:\WINDOWS\system32> get-tpmTpmPresent                : TrueTpmReady                  : TrueManufacturerId            : 1112687437ManufacturerIdTxt         : BRCMManufacturerVersion       : 7.11ManufacturerVersionFull20 : Not Supported for TPM 1.2ManagedAuthLevel          : FullOwnerAuth                 :OwnerClearDisabled        : FalseAutoProvisioning          : EnabledLockedOut                 : FalseLockoutHealTime           : Not Supported for TPM 1.2LockoutCount              : Not Supported for TPM 1.2LockoutMax                : Not Supported for TPM 1.2SelfTest                  : {128, 159, 126, 96}