{"id":10773,"date":"2019-08-17T00:03:00","date_gmt":"2019-08-16T22:03:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=10773"},"modified":"2019-08-17T07:51:14","modified_gmt":"2019-08-17T05:51:14","slug":"windows-10-v1903-bitlocker-issue-tpm-2-0-drops-error-10","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/08\/17\/windows-10-v1903-bitlocker-issue-tpm-2-0-drops-error-10\/","title":{"rendered":"Windows 10 V1903 Bitlocker issue: TPM 2.0 drops error 10"},"content":{"rendered":"

[German<\/a>]Is there an issue with the Trusted Platform Module 2.0 on Windows 10 version 1903? I got reports that TPM is causing error code 10 in Device Manager. Then of course Bitlocker does not work anymore.<\/p>\n

<\/p>\n

Background: Bitlocker and TPM<\/h2>\n

\"\"Microsoft's Bitlocker<\/a> can be used for hard disk encryption under Windows. This feature is available from the Pro version of the operating system. Bitlocker has the possibility to perform the encryption with or without Trusted Platform Module 2.0.<\/p>\n

If a TPM module is missing, a PIN must be entered to decrypt the Bitlocker-encrypted files. If there is a Trusted Platform Module 2.0<\/a> in the form of a chip on the motherboard, Bitlocker can use it for authentication. The encrypted media are then bound to this hardware via TPM.<\/p>\n

Issues with the TPM chip in Windows 10 V1903<\/h2>\n

Bitlocker and the Trusted Platform Module 2.0 are always good for problems under Windows (see links to other articles at the end of this article). Now German blog reader Andreas E. (thank you for that) has informed me about a problem with Bitlocker in connection with TPM 2.0 and Windows 10 May 2019 Update (Version 1903) via a private message on Facebook. He himself as well as his colleagues have noticed problems with TPM on several computers running Windows 10 Version 1903.<\/p>\n

\"TPM
\n(Source: Technet)<\/p>\n

The Trusted Platform Module 2.0 cannot be started. In the Device Manager you will find the error message shown in the screenshot above.<\/p>\n

The device cannot start. (Code 10)<\/p>\n

(Operation Failed)
\nThe requested operation was unsuccessful.<\/p><\/blockquote>\n

If the device (TPM 2.0) cannot be started, the device manager reports error 10, of course the TPM protector for bitlockers is omitted. Then Bitlocker is stopped – and you can no longer access the encrypted information or use Bitlocker with TPM. Andreas writes about it:<\/p>\n

And the [Bitlocker] protection is stopped
\nBut you will find very little information about it
\nMaybe worth doing some research.<\/p><\/blockquote>\n

That's the information I have so far. But a short search on the internet shows that Bitlocker and TPM are not fool proof at all, but can cause trouble. Dell has published a Support article How to troubleshoot and resolve common issues with TPM and BitLocker<\/a> on various bugs.<\/p>\n

Whether there are issues with a TMP 2.0 firmware update, as described here by Microsoft<\/a>, isn't known so far.<\/p><\/blockquote>\n

What can I find about TPM Code 10?<\/h2>\n

If you search for TPM 2.0 and the error code 10 in the internet, you will get some hits.<\/p>\n

Virus scanners and filter drivers<\/h3>\n

In the Technet forum there is this post<\/a>, which deals with the code 10 with TPM 2.0. There a user describes he deleted UpperFilters and LowerFilters (injected by a virus scanner), because they seem to have caused TPM problems.<\/p>\n

But you can't just delete the filter drivers from the registry – the system didn't boot anymore. The affected person had to reinstall Windows 10 V1809 – and then the TPM 2.0 chip was detected cleanly in the device manager.<\/p>\n

Somewhere in forums I found the hint that you should always use the Windows TPM driver – but not the OEM TMP driver (it is also mentioned here<\/a>). I also found the information (e.g. here<\/a>) that the UEFI boot mode can have an influence.<\/p><\/blockquote>\n

Conflict with other hardware?<\/h2>\n

In this HP forum post<\/a>, a user also describes the error image that the TPM 2.0 device displays Code 10 in the Device Manager. Microsoft Windows 10 is used, but no version is specified (based on the post it can have been at most Windows 10 V1803).<\/p>\n

However, the poster also reports issues with Windows 10 Hello logon and a fingerprint sensor. What I took with me from this (unsolved) thread is to pay attention to the following:<\/p>\n