Intel PTT TPM 2.0 Attestation Failure – Microsoft AIK Enrollment Returns HTTP 404 (0x80190194) Despite Certificate Repairs

Job Simon 0 Reputation points
2026-11-20T02:27:52.61+00:00

Hello Microsoft Community,

I'm experiencing an ongoing TPM 2.0 attestation failure that is preventing Call of Duty from passing its security verification requirements. I've spent considerable time troubleshooting this issue, including following the certificate workaround recommended in another Microsoft Q&A thread, but the problem remains unresolved.

System Specifications

  • CPU: Intel Core i5-12400F

Motherboard: ASRock B660M-C

TPM: Intel PTT 2.0

TPM Firmware: 600.18.30.2264

Secure Boot: Enabled

BIOS: Updated

Troubleshooting Already Completed

Verified TPM 2.0 and Secure Boot are enabled.

Updated BIOS and checked TPM configuration.

Extracted the three Intel intermediate certificates directly from TPM firmware:

CSME ADL ROM CA

  CSME ADL SVN01 Kernel CA
  
     CSME ADL PTT 01SVN
     
     Verified their certificate signatures and imported them into the Local Computer Intermediate Certification Authorities store.
     
     Retrieved and verified additional Intel intermediate certificates from Intel's official certificate server.
     
     Discovered that Windows reported `EKCertState: NotPresent`.
     
     Successfully registered the TPM endorsement certificate using `TpmDiagnostics.exe InstallEkCertFromNVR`.
     
     Confirmed `EKCertState` now reports `Present`.
     

Despite these steps, Windows continues reporting:

Ready For Attestation: False
Is Capable For Attestation: False

Microsoft AIK Enrollment Error

When running:

certreq -enrollaik -config ""

I consistently receive:

GetCACaps: Not Found

"The authority does not exist."

HTTP/1.1 404 Not Found

Error: 0x80190194
HTTP_E_STATUS_NOT_FOUND

The failure occurs during GetCACaps, before Windows creates or submits the certificate enrollment request.

Questions for Microsoft

Is Microsoft aware of an issue with AIK Cloud CA authority registration or provisioning affecting Intel PTT systems?

Does this HTTP 404 indicate that the required authority is missing from Microsoft's backend?

Is Microsoft working with Intel to address this issue?

Is there an official workaround or an estimated timeline for a resolution?

Can this issue be escalated to the Windows TPM Attestation / AIK Cloud CA engineering team?

I've already attempted the commonly suggested certificate-chain workaround without success. At this point, I'm trying to determine whether further troubleshooting is possible locally or whether a Microsoft-side fix is required.

Any assistance from Microsoft engineers or others experiencing the same issue would be appreciated.

Thank you.Hello Microsoft Community,

I'm experiencing an ongoing TPM 2.0 attestation failure that is preventing Call of Duty from passing its security verification requirements. I've spent considerable time troubleshooting this issue, including following the certificate workaround recommended in another Microsoft Q&A thread, but the problem remains unresolved.

System Specifications

CPU: Intel Core i5-12400F

Motherboard: ASRock B660M-C

TPM: Intel PTT 2.0

TPM Firmware: 600.18.30.2264

Secure Boot: Enabled

BIOS: Updated

Troubleshooting Already Completed

Verified TPM 2.0 and Secure Boot are enabled.

Updated BIOS and checked TPM configuration.

Extracted the three Intel intermediate certificates directly from TPM firmware:

CSME ADL ROM CA

  CSME ADL SVN01 Kernel CA
  
     CSME ADL PTT 01SVN
     
     Verified their certificate signatures and imported them into the Local Computer Intermediate Certification Authorities store.
     
     Retrieved and verified additional Intel intermediate certificates from Intel's official certificate server.
     
     Discovered that Windows reported `EKCertState: NotPresent`.
     
     Successfully registered the TPM endorsement certificate using `TpmDiagnostics.exe InstallEkCertFromNVR`.
     
     Confirmed `EKCertState` now reports `Present`.
     

Despite these steps, Windows continues reporting:

Ready For Attestation: False
Is Capable For Attestation: False

Microsoft AIK Enrollment Error

When running:

certreq -enrollaik -config ""

I consistently receive:

GetCACaps: Not Found

"The authority does not exist."

HTTP/1.1 404 Not Found

Error: 0x80190194
HTTP_E_STATUS_NOT_FOUND

The failure occurs during GetCACaps, before Windows creates or submits the certificate enrollment request.

Questions for Microsoft

Is Microsoft aware of an issue with AIK Cloud CA authority registration or provisioning affecting Intel PTT systems?

Does this HTTP 404 indicate that the required authority is missing from Microsoft's backend?

Is Microsoft working with Intel to address this issue?

Is there an official workaround or an estimated timeline for a resolution?

Can this issue be escalated to the Windows TPM Attestation / AIK Cloud CA engineering team?

I've already attempted the commonly suggested certificate-chain workaround without success. At this point, I'm trying to determine whether further troubleshooting is possible locally or whether a Microsoft-side fix is required.

Any assistance from Microsoft engineers or others experiencing the same issue would be appreciated.

Thank you.

Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Ronald Sabiiti 2,250 Reputation points Independent Advisor
    2026-11-20T04:01:06.13+00:00

    Hi Simon,

    Since the EK certificate is now present, but AIK enrollment continues to fail during the GetCACaps phase with HTTP 404 (0x80190194), the failure appears to occur before the certificate enrollment request is submitted.

    Similar reports involving Intel PTT systems have documented the same behavior, suggesting a possible AIK service-side authority recognition issue. However, based on the available information, this does not conclusively confirm a Microsoft backend issue.

    At this stage, we do not recommend further TPM resets, certificate imports, or additional local remediation steps. Please retain the full error details, including the authority hostname, timestamp, and any request IDs, as these may be required for further investigation.

    If the issue persists, we recommend opening a Microsoft Support case for review by the TPM Attestation/AIK enrollment team, as there is currently no verified client-side workaround for this specific error.

    References:

    Hope this helps!

    Ronald.

    Was this answer helpful?


  2. AI answer

    2026-11-20T02:29:03.2533333+00:00

    The appropriate next step is to capture the failing AIK enrollment and escalate it through Feedback Hub and Microsoft Support, because the completed EK-certificate repairs do not address a GetCACaps response in which the AIK service says that the requested authority does not exist.

    What the 404 establishes

    Windows uses the TPM endorsement certificate to establish TPM authenticity, then obtains an Attestation Identity Key (AIK) certificate from a Microsoft cloud service. An AIK certificate must be provisioned before Windows can report health through TPM attestation.^1^

    Your results distinguish two stages:

    • EKCertState: Present shows that the missing local EK certificate was repaired.
    • GetCACaps: Not Found is returned while contacting the AIK enrollment authority, before request submission.
    • Therefore, reinstalling the same intermediate certificates or repeating InstallEkCertFromNVR is not a useful next step.
    • The 404 proves that the requested authority name was not found by that service request. It does not, by itself, establish whether the underlying cause is an absent backend record, unsupported Intel endorsement hierarchy, incorrect authority derivation by Windows, or another provisioning problem.

    A closely matching Intel PTT report describes the same certreq -enrollaik 404 across current systems and found no published Microsoft KB, Intel advisory, confirmed universal workaround, or announced resolution date.^2^

    Escalate with a reproducible trace

    1. Install any outstanding Windows quality update, without repeating the BIOS, Secure Boot, TPM firmware, or certificate work already completed. Microsoft recommends current Windows updates for successful attestation.^3^
    2. Open Feedback Hub with recording enabled:
      • Press Windows+F.
      • Select Report a problem.
      • Choose the closest Windows Security / Device security category available.
      • Start Recreate my problem recording.
      • In an elevated Command Prompt, reproduce the failure:
         certreq -enrollaik -config ""
      
      • Stop recording and attach the relevant exported Event Viewer entries and diagnostic output. Feedback Hub supports screenshots and reproduction recording; Microsoft Support or the Get Help app is the channel for direct assistance.^4^
    3. Include these facts in the report:
      • Intel Core i5-12400F, ASRock B660M-C, Intel PTT firmware version, BIOS version, Windows edition/build.
      • Exact time and time zone of the attempt.
      • Full certreq output: stage GetCACaps, HTTP 404, and 0x80190194.
      • The x-ms-request-id, if present in the CertificateServicesClient event.
      • Before/after evidence showing EKCertState changed from NotPresent to Present.
      • Current Ready For Attestation: False and Is Capable For Attestation: False.
      • Confirmation that the Intel intermediate chain was installed and validated.
      • A link or identifier for the Feedback Hub submission when opening the support case.
    4. Open Microsoft Support/Get Help and request routing to the Windows security/TPM attestation component. Phrase the escalation narrowly:

      Intel PTT AIK enrollment receives HTTP 404 at GetCACaps before request submission. The EK certificate is present and its chain has been repaired and validated. Please investigate authority resolution/provisioning for the INTC KeyID and correlate the attached x-ms-request-id.

    Do not post the complete EK certificate, TPM identifiers, authority hostname, serial number, or request identifiers publicly. Provide them only in the private support case if requested.

    Answers to the specific questions

    • Known issue? Similar Intel PTT failures are publicly reported, but the available material does not contain an official Microsoft advisory confirming a specific incident or root cause.
    • Missing backend authority? The response says that the requested authority does not exist, but only Microsoft service telemetry can determine why it was not resolved.
    • Microsoft/Intel investigation? No public source here confirms a joint investigation.
    • Official workaround or ETA? No published case-specific workaround or resolution date is available. A TPM clear is not supported by the evidence as a remedy for this exact 404 and risks removing TPM-protected material; do not perform it merely to retry this case.
    • Engineering escalation? Yes, but Q&A cannot directly assign an engineering incident. Feedback Hub supplies product diagnostics, while Get Help/Microsoft Support provides the direct case and escalation route.

    Windows explicitly collects TPM diagnostic events related to attestation artifacts used by services including Call of Duty, so a recorded reproduction is materially more useful than another certificate-store repair.^5^


    References

    1. Device health attestation
    2. Windows AIK enrollment fails with HTTP 404 for Intel PTT EK authority - Microsoft Q&A
    3. Windows enrollment attestation
    4. Send feedback to Microsoft with the Feedback Hub app | Microsoft Support
    5. Windows 11, versions 25H2 and 24H2 required diagnostic data events and fields
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.