Symptoms
Consider the following scenario:
-
You have a Tablet PC that is running Windows 8.
-
You drain the tablet battery completely.
-
You connect the tablet to the charger.
In this scenario, the tablet may try to turn on and turn off on its own multiple times. This can cause Trusted Platform Module (TPM) anti-hammering logic to lock the TPM. Additionally, the tablet goes into Bitlocker lockout state, and after you enter the recovery key, the Bitlocker drive cannot be unlocked.
Cause
This issue occurs because after you drain the battery, you connect the tablet to the charger, and then the tablet automatically powers on and begins to startup. When the operating system starts, it determines that the battery is too low to run and shuts down. The tablet continues to cycle in this manner until it hits the Trusted Platform Module (TPM) lockout. This leads to Bitlocker recovery mode.Â
Resolution
After you apply this hotfix, you have to clear the TPM for the update to be in effect.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows 8.
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8 file information notesImportant Windows Server 2012 hotfixes are included in the same Windows 8 hotfix packages. However, only Windows 8 is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8". Always refer to the "Applies To" section in an article to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.2.920 0.20 xxx
Windows 8
RTM
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Fveapi.dll |
6.2.9200.20930 |
614,400 |
31-Jan-2014 |
06:03 |
x86 |
Fveapibase.dll |
6.2.9200.20930 |
189,952 |
31-Jan-2014 |
06:03 |
x86 |
Win32_tpm.dll |
6.2.9200.20930 |
254,976 |
31-Jan-2014 |
06:04 |
x86 |
Win32_tpm.mof |
Not applicable |
21,236 |
02-Jun-2012 |
14:47 |
Not applicable |
For all supported x64-based versions of Windows 8
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Fveapi.dll |
6.2.9200.20930 |
755,200 |
31-Jan-2014 |
06:18 |
x64 |
Fveapibase.dll |
6.2.9200.20930 |
240,640 |
31-Jan-2014 |
06:18 |
x64 |
Win32_tpm.dll |
6.2.9200.20930 |
310,784 |
31-Jan-2014 |
06:20 |
x64 |
Win32_tpm.mof |
Not applicable |
21,236 |
02-Jun-2012 |
14:47 |
Not applicable |
Win32_tpm.dll |
6.2.9200.20930 |
254,976 |
31-Jan-2014 |
06:04 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows 8
Additional files for all supported x86-based versions of Windows 8
File property |
Value |
---|---|
File name |
X86_617dba5c0dfcf1328e8e56b5e9fcbc26_31bf3856ad364e35_6.2.9200.20930_none_e3c2c9a736f3169c.manifest |
File version |
Not applicable |
File size |
706 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
19:43 |
File name |
X86_b20cabe210827b7c8b1f4cda6e597b41_31bf3856ad364e35_6.2.9200.20930_none_133d431f4a4a02e3.manifest |
File version |
Not applicable |
File size |
702 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
19:43 |
File name |
X86_microsoft-windows-securestartup-core_31bf3856ad364e35_6.2.9200.20930_none_32416686dc7e5e0f.manifest |
File version |
Not applicable |
File size |
58,530 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
07:00 |
File name |
X86_microsoft-windows-tpm-driver-wmi_31bf3856ad364e35_6.2.9200.20930_none_6cf3cefeaaa32baf.manifest |
File version |
Not applicable |
File size |
21,849 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
07:00 |
Additional files for all supported x64-based versions of Windows 8
File property |
Value |
---|---|
File name |
Amd64_1a0fa4d26b4b878a49a28a26681ddfa7_31bf3856ad364e35_6.2.9200.20930_none_b26d4a3004a57b89.manifest |
File version |
Not applicable |
File size |
706 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
19:47 |
File name |
Amd64_a2727d77ae800e4bbe6821591ce1c3ad_31bf3856ad364e35_6.2.9200.20930_none_5f8353fa454d6429.manifest |
File version |
Not applicable |
File size |
710 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
19:47 |
File name |
Amd64_d312e457ddbfe65fba712329b13dea67_31bf3856ad364e35_6.2.9200.20930_none_ecbecf71bc509509.manifest |
File version |
Not applicable |
File size |
1,054 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
19:47 |
File name |
Amd64_microsoft-windows-securestartup-core_31bf3856ad364e35_6.2.9200.20930_none_8e60020a94dbcf45.manifest |
File version |
Not applicable |
File size |
58,534 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
08:38 |
File name |
Amd64_microsoft-windows-tpm-driver-wmi_31bf3856ad364e35_6.2.9200.20930_none_c9126a8263009ce5.manifest |
File version |
Not applicable |
File size |
21,853 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
08:39 |
File name |
Wow64_microsoft-windows-tpm-driver-wmi_31bf3856ad364e35_6.2.9200.20930_none_d36714d497615ee0.manifest |
File version |
Not applicable |
File size |
21,015 |
Date (UTC) |
31-Jan-2014 |
Time (UTC) |
06:59 |