You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original TPM firmware files from HP (from SoftPaq 76423 - ftp://ftp.hp.com/pub/softpaq/sp76001-76500/sp76423.html) listed only one file for the upgrade from TPM 1.2/FW 6.41 to TPM 2.0:
TPM12_6.41.197.0_to_TPM20_7.41.2375.0.BIN
However, the TPM firmware files update from January 2017 (SoftPaq 78910 - ftp://ftp.hp.com/pub/softpaq/sp78501-79000/sp78910.html) now lists two different files for TPM 1.2/FW 6.41 to TPM 2.0:
Note that these two files are only different in the BUILD part of the version: 6.41.197 vs. 6.41.198. It seems .198 is only used when downgrading TPM 2.0/FW 7.61 to TPM 1.2 again as the archive contains on file for this: TPM20_7.61.2785.0_to_TPM12_6.41.198.0.BIN.
The problem is that the Win32_TPM CIM class does not provide the BUILD part in the ManufacturerVersion field, only MAJOR.MINOR.
As we depend on this class, we can never detect if 6.41.197 vs. 6.41.198 is installed. This can lead to an error during the upgrade process.
The text was updated successfully, but these errors were encountered:
The original TPM firmware files from HP (from SoftPaq 76423 - ftp://ftp.hp.com/pub/softpaq/sp76001-76500/sp76423.html) listed only one file for the upgrade from TPM 1.2/FW 6.41 to TPM 2.0:
However, the TPM firmware files update from January 2017 (SoftPaq 78910 - ftp://ftp.hp.com/pub/softpaq/sp78501-79000/sp78910.html) now lists two different files for TPM 1.2/FW 6.41 to TPM 2.0:
Note that these two files are only different in the BUILD part of the version: 6.41.197 vs. 6.41.198. It seems .198 is only used when downgrading TPM 2.0/FW 7.61 to TPM 1.2 again as the archive contains on file for this:
TPM20_7.61.2785.0_to_TPM12_6.41.198.0.BIN
.The problem is that the Win32_TPM CIM class does not provide the BUILD part in the
ManufacturerVersion
field, only MAJOR.MINOR.As we depend on this class, we can never detect if 6.41.197 vs. 6.41.198 is installed. This can lead to an error during the upgrade process.
The text was updated successfully, but these errors were encountered: