Trusted Platform Module not working in Windows 10 after OS recovery

[DBailey635]

Hi. I've recently had to drive wipe and rebuild my HP ENVY Notebook's OS after a boot failure (it's a long story involving a corrupted LiveCD/USB copy of Linux).

The supplied HP Recovery partition restore failed twice, so I installed Windows 10 from an ISO downloaded from the Microsoft website (thank-you for the Media Creation Tool!). I now have a working copy of Windows 10 Home on the machine, except that Windows Hello pin and the fingerprint reader don't work, and I can't get MS Office to remember my network and email / Exchange server passwords.

After some digging about in multiple forums, I've tracked the problem back to the Trusted Platform Module (TPM).

The TPM is enabled in the BIOS/EFI and is active. I have used the HP Support app to install the latest Intel chipset drivers for my machine. In Windows Device Manager, the TPM is identified and there is a working 2006 Microsoft Driver running. However, when I go to the tpm.msc, it says that the TPM was not found.

I can't continue restoring applications and my backups on my machine until I've got this TPM working. Is there a newer driver I should be using? Is there a command I need to run? Any help given will be greatfully received.

Thanks.

[erico]

Did you create USB recovery media via the HP Recovery Media creator utility?

What do you mean by "The supplied HP Recovery partition restore failed twice"? 

What build of Windows 10 have you installed?

What exactly did you install after you installed Windows 10?

I do hope that you did not erase the factory keys in the BIOS. Did you by chance happen to do that?

[DBailey635]

Hi Erico,

In answer to your questions...

> Did you create USB recovery media via the HP Recovery Media creator utility?

I wasn't aware this existed until after the computer went belly-up, so I didn't have one. I only had the HP Recovery partition to work with.

> What do you mean by "The supplied HP Recovery partition restore failed twice"? 

Exactly that. After the Windows boot loader was corrupted by the LiveCD/USB stick, the laptop went into Windows 10 recovery mode. I initially tried using command-line tools to recreate or repair the boot-loader, but they said it didn't exist, and it couldn't find a copy of Windows 10 on the machine (even though I could cd through the c:/Windows folders). I then tried to perform a recovery using the HP recovery partition, and two attempts failed..  the OS couldn't be recovered or repaired. I then tried to wipe and rebuild the disk and OS from the HP recovery partition, but that didn't work either. This was why I went to the Microsoft website and downloaded the Media Creation Tool to install a fresh copy of Windows 10 onto a USB stick to recover the machine (my OS licence is attached to my Microsoft ID).

The failure of the HP recovery partition makes me very wary of paying £45 for recovery media from HP's partner. They are probably identical.

> What build of Windows 10 have you installed?

Latest fully patched public build (not Windows Insider), so Fall Creators Update.

> What exactly did you install after you installed Windows 10?

After installing Windows 10, I added Firefox, as it has most of my passwords in its online keychain. I also installed MS Office 2016. I haven't installed anything else, or restored my file backups.

> I do hope that you did not erase the factory keys in the BIOS. Did you by chance happen to do that?

I have no idea. BIOS/EFI reports TPM as enabled and active, so I don't think so.

[erico · Accepted solution]

Any time you experiment with Live CDs or USB flash drives with a Linux OS and make changes to the partitions inadvertently or not, damage to the invaluable recovery partition is likely to happen.

You weren't supposed to try to use the recovery partition to run a factory image recovery. You were supposed to use the recovery media or the HP Recovery Manager. That should have been done before deleting the partitions on the hard disk.

The Fall Creators update is version 1709, so don't install the version 1607 drivers. 

Install the 

Intel Chipset Installation Utility and Driver

HP 3D DriveGuard Software

Realtek High-Definition (HD) Audio Driver

Intel Serial IO Driver

Intel Software Guard Extensions Device (SGX) Driver

Intel High-Definition (HD) Graphics Driver

HP Wireless Button Driver

Synaptics TouchPad Driver

Validity Fingerprint Sensor Driver

Install the wifi adapter driver that matches the model\brand that is installed in your notebook

Intel Rapid Storage Technology Driver

Realtek Card Reader Driver

CyberLink Power Media Player Software

Cyberlink Youcam Software

HP SimplePass Identity Protection Software

All of the drivers for your notebook are located at the following HP Support portal download webpage.

https://support.hp.com/gb-en/drivers/selfservice/hp-envy-13-d000-notebook-pc/7771341/model/8942403

"The failure of the HP recovery partition makes me very wary of paying £45 for recovery media from HP's partner. They are probably identical."   No, they are not. You dinked the recovery partition somehow. Hp tried to protect you by providing the ability to create USB recovery media on your own, but you did not take advantage of it. If you choose not to purchase the factory created version of the recovery media that is specific to your notebook, that is your own choice.  I kind of like having all of the required drivers,  the supplied software and the complete operating system available on a USB flash drive, but that is my own preference.

[DBailey635]

Thanks Erico,

Re-installing all of the drivers has now resolved my issue. The TPM is now listed as running as v2.0, rather than the v1.2 it was before. Not sure why Windows 10 didn't install this driver automatically.

I'll investigate backing up and creating a new system image, just in case.

[erico]

---

@DBailey635 wrote:

Thanks Erico,

Re-installing all of the drivers has now resolved my issue. The TPM is now listed as running as v2.0, rather than the v1.2 it was before. Not sure why Windows 10 didn't install this driver automatically.

I'll investigate backing up and creating a new system image, just in case.

---

It is good to hear that your system is back up and running as it should.

I am a firm believer in having a system image.

I believe in having a plan "B".