TPM event logger error after cpu swap, Event id 86

Question

I just swapped out my cpu, my previous chip had died and just received my replacement, both 5950x, Upon boot I received " New cpu installed, fTPM/PSP NV corrupted" and it asked me to reset, which I did, now im receiving the following error:

SCEP Certificate enrollment initialization for Local system via https://AMD-KeyId-578c545f796951421221a4a578acdb5f682f89c8.microsoftaik.azure.net/templates/Aik/scep failed:

GetCACaps
GetCACaps: Not Found
{"Message":"The authority \"amd-keyid-578c545f796951421221a4a578acdb5f682f89c8.microsoftaik.azure.net\" does not exist."}
HTTP/1.1 404 Not Found
Date: Thu, 02 Sep 2021 14:27:28 GMT
Content-Length: 121
Content-Type: application/json; charset=utf-8
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000;includeSubDomains
x-ms-request-id: d623448f-ee97-4ff8-a54c-c552e6a999be

Method: GET(203ms)
Stage: GetCACaps
Not found (404). 0x80190194 (-2145844844 HTTP_E_STATUS_NOT_FOUND)

How can I fix this?

Answer 1

It's far more likely it is a combination of Microsoft's inability to get on-board w/ AMD prior to launch. It's no mystery Microsoft wrote their TPM module (attestation) with Intel and not with AMD - you only need to review/research the plethora of documentation on the Internet demonstrating both Intel & Microsoft were writing in collaboration. The ability to employ UEFI/TPM encryption & attestation should not be Intel processor specific - which it is turning out to be just the exact case. AMD & Intel most likely secure processor UEFI/TPM module encryption in vary similar manners. It's my understanding the delta resides in the fact AMD employ the best "core" CPU for running the OS & accommodating applications loaded within the OS when it boots. The best "core" may change during any particular boot operation on an AMD CPU. I'm implying that a Intel does not use the best "core" feature but instead uses the same steady configuration of each core - IOW the best "core" does not change as it does on the AMD CPU architecture. I do know the architecture is different at the hardware and software level. I don't know how the Microsoft TPM module secures the required TPM encryption algorithm to provide attestation; but, it's the attestation which fails repeatedly. These combinations are difficult to understand but it appears this is a Microsoft + AMD issue and not a Microsoft + Intel issue.

I'm curious if anyone has noticed POST often changes during any particular BIOS boot process. One day it's one set of POST beeps & on any other day it's a different set of POST beeps. Interesting.

Answer 2

Let's face it. No one should have to purchase a dedicated aftermarket discrete TPM chip for their MoBo....period. You find anyone on the Intel side having to buy TPM chips for their MoBo's? No you do not. There is absolutely no reason an end-user should have to be forced to purchase an add-on discrete TPM chip for any MoBo when the MoBo you currently own is UEFI/TPM 2.0 certified....period. Wait until the next release when Microsoft "finally" writes their TPM module attestation to meet industry standards as opposed to sleeping with Intel.

Answer 3

Look, just follow the link in browser, you will see its not your computer, its the server.

Answer 4

Hello Arun K,

The 404 error at the bottom clearly states that the host is not existing or there is a Client-Server connectivity failure, since the site appears to be accessible (I have just tried and got a 200 hit, it seems that something might be blocking the access.

Temporary disable firewall or proxy software allowing testing a direct connection to the internet. You can also set a Firewall rule to Allow c:\Windows\System32\taskhostw.exe to the internet.

Other workaround is to disable temporary TPM in the BIOS. After completing a reboot and the potential request for reset, you can reenable again.

Hope it helps in your case!

Best regards,

Answer 5

I advise you to report this issue using the Feedback Hub app.
Also check and make sure you have installed all drivers and required firmware, if any.