• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
We have new content about Hotkey issue, Click here to check it out!
Locked

‎08-28-2018 12:43 PM

HP Recommended
Product: Pavilion 24-b171ny
Operating System: Microsoft Windows 10 (64-bit)

Hello, after the Windows update in october 2017 my Pc have problems with TPM, in device maneger under secutity devices appears an exclamation point and under TPM properties : "Device ACPI\MSFT0101\1 was migrated." and "Device ACPI\MSFT0101\1 had a problem starting." and "A protocol error was detected between the driver and the device."

Any advice how to fix it?

 

The second problem maybe is connected with the 1st one is:

 

After shutdown of the PC the power button stays illuminated and inside the PC can hear the fans turned on. Than to restart the PC i must press the power button more then 6 sec to power on, but it takes more time than usually.

 

thanks for any advices

12 REPLIES 12

‎08-28-2018 02:18 PM

HP Recommended

Greetings,

Welcome to the forum.

I am not an HP employee.

 

This is a strange error message. To the best of my knowledge HP consumer PCs don't ship with Trusted Platform Module hardware. I have never run across a HP or a Dell or a Lenovo consumer PC having aTPM chip on the mainboard.

 

Did you install TPM software or are you running TPM emulation? Did you install and are you running any kind of boot time security software?

 

Uninstall the unknown device in Device Manager.

 

I would suggest resetting CMOS but I am pretty sure your PC did not ship with a TPM integrated in the motherboard.

 

Regards

Was this reply helpful? Yes No

‎08-29-2018 07:34 AM

HP Recommended

Thanks for the quick answer, i think TPM is integrated on motherboard, because i tryied to disabled/enabled in BIOS, but after the reboot the TPM appeared again in the device manager, also i tryied to disinstall the device, but after the reboot same story.

I didn`t install any software or emulation for TPM, i just installed an update for BIOS F.41 and the updates suggested by HP technician.

 

Thanks

Was this reply helpful? Yes No

‎09-07-2018 06:25 AM

HP Recommended

Hi, any advices about?

 

 

Thanks

Was this reply helpful? Yes No

‎09-07-2018 07:05 AM

HP Recommended

Hi,

 

Sorry for not getting back to you.

 

I don't know why you are having this problem.

 

I have not run across a consumer PC with an integrated TPM module on the motherboard.

 

There are no firmware updates for this at your PC's HP Support site (link). There is a Intel MEI update available, sp90139exe (download).

 

I cannot find a detailed MB diagram at HP's Support site to check for an integrated MB TPM module.

 

Maybe a different forum member has additional thoughts on this.

 

You stated this problem first started after the latest W10 update. Maybe the error message is related to this.

 

Regards

 

Was this reply helpful? Yes No

‎09-07-2018 07:30 AM

HP Recommended

Hi, i installed the IMEI update, but with this error:Error.jpg

Was this reply helpful? Yes No

‎09-07-2018 07:32 AM

HP Recommended

And i also contacted the Microsoft forums about that, so far without any usefull solution.

 

Thanks

Was this reply helpful? Yes No

‎09-07-2018 07:49 AM - edited ‎09-07-2018 07:51 AM

HP Recommended

Hi,

 

The image is not yet viewable.

 

Try installing sp88092 (link) before installing the MEI firmware update, sp90139.exe.

 

There is a Intel Trusted Execution Engine Interface Driver you can look at here. (link). It was released in 2016 so I don't know if this will help.

 

Maybe this older version is causing the problem. You may need a newer version which appears to be missing at this time.

 

Regards

Was this reply helpful? Yes No

‎09-07-2018 09:03 AM

HP Recommended

Hi, intalled sp88092, but with error again: "The platform is not supported"

 

Brez naslova.jpg

Was this reply helpful? Yes No

‎09-07-2018 09:06 AM

HP Recommended

Maybe this help:

 

 

2018:09:07 16:52:39:723: >>>Dumping deffered logs
2018:09:07 16:52:39:711: Adding XP-x86 (0x50000501 == 0x40000501)
2018:09:07 16:52:39:711: Adding XP-x64 (0x90000502 == 0x80000502)
2018:09:07 16:52:39:711: Adding W2K3-x64 (0xA0000502 == 0x80000502)
2018:09:07 16:52:39:711: Adding W2K3-x86 (0x60000502 == 0x40000502)
2018:09:07 16:52:39:711: Adding Vista-x64 (0x90000600 == 0x80000600)
2018:09:07 16:52:39:711: Adding W2K8-x64 (0xA0000600 == 0x80000600)
2018:09:07 16:52:39:711: Adding Vista-x86 (0x50000600 == 0x40000600)
2018:09:07 16:52:39:711: Adding W2K8-x86 (0x60000600 == 0x40000600)
2018:09:07 16:52:39:711: Adding Windows7-x64 (0x90000601 == 0x80000601)
2018:09:07 16:52:39:711: Adding W2K8R2-x64 (0xA0000601 == 0x80000601)
2018:09:07 16:52:39:711: Adding Windows7-x86 (0x50000601 == 0x40000601)
2018:09:07 16:52:39:711: Adding Windows8-x64 (0x90000602 == 0x80000602)
2018:09:07 16:52:39:711: Adding W2K12-x64 (0xA0000602 == 0x80000602)
2018:09:07 16:52:39:711: Adding Windows8-x86 (0x50000602 == 0x40000602)
2018:09:07 16:52:39:711: Adding Windows8.1-x64 (0x90000603 == 0x80000603)
2018:09:07 16:52:39:711: Adding W2K12R2-x64 (0xA0000603 == 0x80000603)
2018:09:07 16:52:39:711: Adding Windows8.1-x86 (0x50000603 == 0x40000603)
2018:09:07 16:52:39:711: Adding Windows10-x64 (0x90000A00 == 0x80000A00)
2018:09:07 16:52:39:711: Adding W2K16-x64 (0xA0000A00 == 0x80000A00)
2018:09:07 16:52:39:711: Adding Windows10-x86 (0x50000A00 == 0x40000A00)
2018:09:07 16:52:39:714: Checking .NET version...
2018:09:07 16:52:39:714: Expected version: v2.0.50727
2018:09:07 16:52:39:714: Found registry key for the expected .NET version.
2018:09:07 16:52:39:714: Checking .NET version...
2018:09:07 16:52:39:714: Expected version: v3.0
2018:09:07 16:52:39:714: Found registry key for the expected .NET version.
2018:09:07 16:52:39:714: Checking .NET version...
2018:09:07 16:52:39:714: Expected version: v3.5
2018:09:07 16:52:39:714: Found registry key for the expected .NET version.
2018:09:07 16:52:39:714: Checking .NET version...
2018:09:07 16:52:39:714: Expected version: v4\Client
2018:09:07 16:52:39:714: Found registry key for the expected .NET version.
2018:09:07 16:52:39:714: Checking .NET version...
2018:09:07 16:52:39:714: Expected version: v4\Full
2018:09:07 16:52:39:714: Found registry key for the expected .NET version.
2018:09:07 16:52:39:714: Checking .NET version...
2018:09:07 16:52:39:714: Expected version: v4.5\Client
2018:09:07 16:52:39:715: Found registry key for the expected .NET version.
2018:09:07 16:52:39:715: Looking for .NET version 4.5 or above
2018:09:07 16:52:39:715: Found version: 4.7.03056
2018:09:07 16:52:39:715: Checking .NET version...
2018:09:07 16:52:39:715: Expected version: v4.5\Full
2018:09:07 16:52:39:715: Found registry key for the expected .NET version.
2018:09:07 16:52:39:715: Looking for .NET version 4.5 or above
2018:09:07 16:52:39:715: Found version: 4.7.03056
2018:09:07 16:52:39:715: Loading saved properties
2018:09:07 16:52:39:721: Effective command line: "C:\swswtup\SP88092\SetupME.exe"
2018:09:07 16:52:39:724: >>> Log start
2018:09:07 16:52:39:725: Mutex with given name doesn't exist. Creating new one.

2018:09:07 16:52:39:726: Obtained mutex succesfully.
2018:09:07 16:52:39:727: Single-instance mutex has been obtained
2018:09:07 16:52:39:727: Core version: 2.7.3
2018:09:07 16:52:39:728: Setup version: 2.3.22.0
2018:09:07 16:52:39:729: Command line: "C:\swswtup\SP88092\SetupME.exe"
2018:09:07 16:52:39:729: OS data: 10-0-1-0 64-bit
2018:09:07 16:52:39:730: System up time: 15434 sec
2018:09:07 16:52:39:730: Reboot pending: No
2018:09:07 16:52:39:731: Current UI language: 0424
2018:09:07 16:52:39:732: Language folder: C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp
2018:09:07 16:52:39:752: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\ar-SA\IntelCommon.dll. Lang 0401. Rank 0
2018:09:07 16:52:39:766: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\cs-CZ\IntelCommon.dll. Lang 0405. Rank 0
2018:09:07 16:52:39:782: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\da-DK\IntelCommon.dll. Lang 0406. Rank 0
2018:09:07 16:52:39:796: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\de-DE\IntelCommon.dll. Lang 0407. Rank 0
2018:09:07 16:52:39:812: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\el-GR\IntelCommon.dll. Lang 0408. Rank 0
2018:09:07 16:52:39:825: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\en-US\IntelCommon.dll. Lang 0409. Rank 1
2018:09:07 16:52:39:839: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\es-ES\IntelCommon.dll. Lang 0C0A. Rank 0
2018:09:07 16:52:39:856: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\fi-FI\IntelCommon.dll. Lang 040B. Rank 0
2018:09:07 16:52:39:871: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\fr-FR\IntelCommon.dll. Lang 040C. Rank 0
2018:09:07 16:52:39:885: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\he-IL\IntelCommon.dll. Lang 040D. Rank 0
2018:09:07 16:52:39:899: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\hu-HU\IntelCommon.dll. Lang 040E. Rank 0
2018:09:07 16:52:39:913: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\it-IT\IntelCommon.dll. Lang 0410. Rank 0
2018:09:07 16:52:39:927: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\ja-JP\IntelCommon.dll. Lang 0411. Rank 0
2018:09:07 16:52:39:941: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\ko-KR\IntelCommon.dll. Lang 0412. Rank 0
2018:09:07 16:52:39:955: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\nb-NO\IntelCommon.dll. Lang 0414. Rank 0
2018:09:07 16:52:39:970: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\nl-NL\IntelCommon.dll. Lang 0413. Rank 0
2018:09:07 16:52:39:986: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\pl-PL\IntelCommon.dll. Lang 0415. Rank 0
2018:09:07 16:52:40:001: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\pt-BR\IntelCommon.dll. Lang 0416. Rank 0
2018:09:07 16:52:40:015: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\pt-PT\IntelCommon.dll. Lang 0816. Rank 0
2018:09:07 16:52:40:031: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\ru-RU\IntelCommon.dll. Lang 0419. Rank 0
2018:09:07 16:52:40:045: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\sk-SK\IntelCommon.dll. Lang 041B. Rank 0
2018:09:07 16:52:40:061: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\sl-SI\IntelCommon.dll. Lang 0424. Rank 3
2018:09:07 16:52:40:076: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\sv-SE\IntelCommon.dll. Lang 041D. Rank 0
2018:09:07 16:52:40:092: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\th-TH\IntelCommon.dll. Lang 041E. Rank 0
2018:09:07 16:52:40:107: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\tr-TR\IntelCommon.dll. Lang 041F. Rank 0
2018:09:07 16:52:40:121: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\zh-CN\IntelCommon.dll. Lang 0804. Rank 0
2018:09:07 16:52:40:136: Found C:\Users\mirko\AppData\Local\Temp\IIF83EE.tmp\zh-TW\IntelCommon.dll. Lang 0404. Rank 0
2018:09:07 16:52:40:139: Loading language 0424
2018:09:07 16:52:40:156: Setup mode: Update
2018:09:07 16:52:40:157: Looking for OS: 5.1 5.2
2018:09:07 16:52:40:157: Preparing to check for Kernal Mode Driver Framework 1.11 or higher
2018:09:07 16:52:40:158: KMDF 1.11 or higher detected!
2018:09:07 16:52:40:158: Checking .NET version...
2018:09:07 16:52:40:159: Expected version: v3.5
2018:09:07 16:52:40:160: Found registry key for the expected .NET version.
2018:09:07 16:52:40:160: .NET version check passed
2018:09:07 16:52:40:161: Looking for OS: 5.1 5.2 6.0 6.1 6.2 6.3 10.0
2018:09:07 16:52:40:161: OS check passed
2018:09:07 16:52:40:162: Checking .NET version...
2018:09:07 16:52:40:162: Expected version: v3.5
2018:09:07 16:52:40:163: Found registry key for the expected .NET version.
2018:09:07 16:52:40:164: .NET version check passed
2018:09:07 16:52:40:164: Resolving driver source
2018:09:07 16:52:40:165: Using embedded driver(s). Temp source is 'C:\Users\mirko\AppData\Local\Temp\IIF8595.tmp'
2018:09:07 16:52:40:187: Using folder 'C:\Users\mirko\AppData\Local\Temp\IIF8595.tmp' as the driver source
2018:09:07 16:52:40:187: Scanning all active devices
2018:09:07 16:52:40:206: Scanning HECI_REL\win10\heci.inf (Name: HECI_REL_WIN10_HECI, Version: 11.7.0.1057)
2018:09:07 16:52:40:206: Section with the best match: Intel.NTamd64.10.0
2018:09:07 16:52:40:208: Device: PCI\VEN_8086&DEV_8C3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:208: Device: PCI\VEN_8086&DEV_9C3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:208: Device: PCI\VEN_8086&DEV_8D3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:209: Device: PCI\VEN_8086&DEV_9CBA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:210: Device: PCI\VEN_8086&DEV_8CBA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:210: Device: PCI\VEN_8086&DEV_9D3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:211: Device: PCI\VEN_8086&DEV_A13A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:212: Device: PCI\VEN_8086&DEV_A2BA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:213: Device: PCI\VEN_8086&DEV_A1BA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:213: Device: PCI\VEN_8086&DEV_A23A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:214: MUP OS bits: 0x1FF000
2018:09:07 16:52:40:220: Scanning HECI_REL\win7\heci.inf (Name: HECI_REL_WIN7_HECI, Version: 11.7.0.1057)
2018:09:07 16:52:40:221: Section with the best match: Intel.NTamd64.6.1
2018:09:07 16:52:40:222: Device: PCI\VEN_8086&DEV_8C3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:222: Device: PCI\VEN_8086&DEV_9C3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:223: Device: PCI\VEN_8086&DEV_8D3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:224: Device: PCI\VEN_8086&DEV_9CBA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:224: Device: PCI\VEN_8086&DEV_8CBA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:225: Device: PCI\VEN_8086&DEV_9D3A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:226: Device: PCI\VEN_8086&DEV_A13A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:226: Device: PCI\VEN_8086&DEV_A2BA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:227: Device: PCI\VEN_8086&DEV_A1BA (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:228: Device: PCI\VEN_8086&DEV_A23A (Intel(R) Management Engine Interface )
2018:09:07 16:52:40:228: MUP OS bits: 0x1B6FFE
2018:09:07 16:52:40:230: E Win32 exception occurred!!
2018:09:07 16:52:40:231: Error code: 0x4E24 (20004)
2018:09:07 16:52:40:232: Error text: ''
2018:09:07 16:52:40:233: Extended error text: 'Error in device matching'
2018:09:07 16:52:40:233: Debug info: 'Setup.cpp (824)'
2018:09:07 16:52:40:241: Reading storyboard
2018:09:07 16:52:40:242: Page count: 7
2018:09:07 16:52:40:243: Added: Welcome
2018:09:07 16:52:40:243: Added: Modify
2018:09:07 16:52:40:244: Added: License
2018:09:07 16:52:40:245: Added: Destination
2018:09:07 16:52:40:245: Added: Progress
2018:09:07 16:52:40:246: Added: Finish
2018:09:07 16:52:40:247: Added: Error
2018:09:07 16:52:40:247: Reading string map
2018:09:07 16:52:40:248: No string map present
2018:09:07 16:52:40:285: Showing page: Error
2018:09:07 16:53:01:518: Link: Launching 'C:\Users\mirko\Intel\Logs'

Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.

Didn't find what you were looking for? Ask the community

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.