TPM event logger error after cpu swap, Event id 86

Arun Kandasamy 131 Reputation points
2021-09-02T14:44:56.32+00:00

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?

Windows for business | Windows Client for IT Pros | User experience | Other

94 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Maison da Silva 8,151 Reputation points MVP
    2022-01-07T11:00:28.213+00:00

    Send here bug https://aka.ms/AAeqtvb

    Was this answer helpful?

  2. steven kang 1 Reputation point
    2022-01-09T21:57:08.57+00:00

    Is it at all possible that a faulty keyboard could cause this error? I've been getting this error too when my computer freezes up suddenly. I stopped using my keyboard cause it had been acting weird and I'm worried it was short-circuiting my computer. Since I've stopped using that keyboard, my computer hasn't frozen but it's only a couple of days.

    My issues are so inconsistent so it's hard to tell if it's ever back to normal. Of course, it's also possible I was just having equipment issues and now this event issue. It's just all so confusing. No one has a root cause yet huh?

    Was this answer helpful?

  3. Norm Geltz 171 Reputation points
    2022-01-09T22:19:11.507+00:00

    It is most CERTAINLY going to be a HARDWARE device issue and it will MOST likely result from incompatible h/w - whether it is the hardware device itself, or the driver for the h/w device. As previously stated, DOUBLE-CHECK your h/w drivers for all h/w devices. Attestation occurs as the result of being able to "certify" the device via a cryptographic key. If the h/w device driver is not certified, it will fail attestation. Check all h/w device drivers on each of the h/w device manufacturer's support website.

    Was this answer helpful?

    0 comments
  4. Norm Geltz 171 Reputation points
    2022-01-09T22:32:02.3+00:00

    I ran down this issue for some time. This is a follow-up to my resolution. The issue was the result of my graphic card driver was not up-to-date. ASUS PRIME x470-PRO (mobo), BIOS Ver. 5861, AMD Ryzen 5 2600x, NVIDIA GeForce GT1030. I purchased my GT1030 from Gigabyte. The correct driver was recently (Dec 15, 2021) updated on Gigabyte website. Since installation of the up-to-date graphic card driver, the issue has been resolved - complete attestation, no TPM SCEP Certificate enrollment error w/ Evend ID 86 i.e. complete resolution.

    NOTE: Double-check ALL h/w drivers not simply via Windows Update, double-check all h/w drivers from the device manufacturer where you purchased the h/w device - this is critical. Good Luck.

    Was this answer helpful?

  5. Norm Geltz 171 Reputation points
    2022-01-10T00:28:57.733+00:00

    In the long of it, I believe you have "some" knowledge of what attestation involves I believe. The h/w & s/w must be trusted (e.g. UEFI/TPM = Trusted Computing [TC]). You CANNOT maneuver around the requirement for TC; albeit, every device must be certified and an Attestation (encrypted) Key generated on your device (PC). MS "Azure" server operates as the intermediary to negotiate the authenticity of the Attestation Key. In a nutshell, all h/w & s/w must roll up into the creation of the Attestation Key. Again, this occurs via UEFI/TPM - each device asserts it is certified - this effectively means an outdated driver, an old(er) incompatible h/w device or its associated outdated s/w will not pass certification to create an Attestation Key if the h/w or s/w device cannot be "attested". Each h/w & s/w device rolls up into the Attestation Key (I realize I'm repeating myself). That key is generated within two layers: (1) UEFI (which must be enabled=BIOS) and TPM (which must be enabled=BIOS); however, there's a small catch to this. While both UEFI and TPM are BIOS provisioning factors, that Attestation Key is created by the OS (in other words Microsoft). So, the Attestation Key is produced and sent to the MS Azure Server (intermediary) to certify the authenticity of the device (your PC - which includes all h/w & s/w running on your PC). If the Attestation Key fails on your machine, it can/will cause disruptions to either or both h/w &/or s/w running on the PC.

    This will be a two part answer - I've exceeded the character(s) limit.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.