Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

TPM (Trusted Platform Module) firmware updates may take longer when installing on a Windows Vista or Windows Server 2008 based computer


View products that this article applies to.

Rapid publishing

Source: Microsoft Support

↑ Back to the top


Summary

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


More information



When installing TPM Firmware updates or updates that communicate through a TPM driver, the update may take longer depending on the TPM driver implementation.





Details:



Some TPM firmware updates send commands to the TPM from the Windows operating system.� In Windows Vista and Windows Server 2008 the firmware update may send commands to the TPM Base Services (TBS) which sends each command to the Microsoft TPM driver.� The Microsoft TPM driver sends each command to the TPM.� On earlier operating systems like Windows XP, Microsoft does not provide a TPM driver, so the firmware updates may send commands directly to an non-Microsoft TPM driver.� Microsoft recommends usage of the TBS and the Microsoft TPM driver on Windows Vista and Windows Server 2008, however, it is also possible for a firmware update to use a non-Microsoft TPM driver on� these operating systems too.�



While communicating with the TPM hardware, the Microsoft TPM driver thread may briefly sleep while waiting for the TPM hardware to respond.� Having the TPM driver sleep reduces CPU usage which improves the responsiveness of other processes running on the computer or may reduce system power consumption.� When the Microsoft TPM driver thread sleeps it may not be scheduled again until after the TPM hardware has responded, increasing the total command duration by the time the TPM hardware responded until the Microsoft TPM driver thread was scheduled.� Non-Microsoft TPM drivers may not sleep when communicating with the TPM hardware resulting in a shorter total command duration at the cost of using more system resources.



If a TPM firmware update involves sending a large number of commands through a TPM driver, different implementations of the TPM driver will impact the total time for the firmware update to complete.� Due to design trade-offs between speed and the balancing of system resources, a firmware update using the Microsoft TPM driver may take longer than a firmware update using a non-Microsoft TPM driver.



↑ Back to the top


Disclaimer



For more information about the TPM Base Service (TBS) in Windows, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/aa446792(VS.85).aspx

↑ Back to the top


Keywords: kbnomt, kbrapidpub, KB963704

↑ Back to the top

Article Info
Article ID : 963704
Revision : 3
Created on : 1/22/2009
Published on : 1/22/2009
Exists online : False
Views : 295