The supported next action is to open a Microsoft Support case for the AIK enrollment service and submit a Feedback Hub report containing the failing INTC-KeyId-1905ef77… authority, because end users cannot register AIK authorities or modify Microsoft’s backend trust database.^1^
Your evidence strongly indicates a service-boundary failure:
-
certreq -enrollaik -config "" reaches microsoftaik.azure.net.
-
GetCACaps returns 404 Not Found / 0x80190194.
- The response identifies the requested authority as nonexistent.
- The local EK chain validates.
- BIOS and CSME firmware are already current.
This matches the failure pattern in which the AIK service does not recognize an authority associated with the TPM endorsement hierarchy. There is no documented client-side method to onboard it.^1^ Public information does not, however, independently confirm whether 1905ef77… is absent, incorrectly mapped, or intentionally unsupported; Microsoft and Intel must verify that mapping.
1. Open the Microsoft Support case
Use the Get Help app or Microsoft Support and request routing to the team responsible for Windows TPM AIK certificate enrollment / Microsoft-hosted attestation service. Feedback Hub reports product defects, while Microsoft Support is the channel for direct assistance and escalation.^2^
Use a concise case title:
Intel MTP PTT AIK enrollment: GetCACaps returns 404 for INTC-KeyId-1905ef77 — request AIK authority/trust-onboarding investigation
Include:
- Hardware:
GIGABYTE Z890I AORUS ULTRA, BIOS F20
- TPM manufacturer/model:
INTC / MTP
- Issuer:
ODCA 2 CSME MTP PCH SVN 01 PTT CA
- Subordinate issuer:
ODCA 2 CSME MTP PCH SVN 01 Kernel CA
- Full AKI—not only the
1905ef77 prefix
- Exact failing
*.microsoftaik.azure.net hostname and SCEP path
- Complete
certreq -enrollaik -config "" output
- Event Viewer certificate-enrollment event, including timestamp and
x-ms-request-id
-
TpmDiagnostics.exe ekchain output showing dwErrorStatus: 0x10000
- Windows edition, version, build, and update level
- Confirmation that BIOS and CSME firmware are current
- Ricochet’s attestation result and timestamp
Ask Support to confirm:
- Whether the full AKI maps to a provisioned
INTC-KeyId authority.
- Whether the ODCA 2 CSME MTP PCH SVN 01 PTT CA is trusted/onboarded.
- Whether the hostname is generated from the expected certificate in the EK chain.
- Whether Microsoft requires an updated or corrected CA package from Intel.
- Whether an incident or service-side work item can be opened.
Do not publish the complete EK certificate if it contains device-identifying values; attach it privately to the support case.
2. File a linked Feedback Hub report
- Press Windows+F.
- Select Report a problem.
- Search for an existing report using
INTC-KeyId-1905ef77, 0x80190194, and AIK GetCACaps 404.
- If found, select Give similar feedback; otherwise create a new problem.
- Mark it as blocking, reproduce the enrollment attempt while recording diagnostics, and attach the sanitized logs.
- Save the Feedback Hub link and place it in the Support case.
Signing in allows searching, upvoting, and tracking existing reports.^2^
3. Open a parallel GIGABYTE/Intel case
Microsoft may need the TPM/firmware supplier to provide or correct the CA onboarding material. Give the vendor the same CA names, full AKI, failing hostname, firmware versions, and Microsoft case number. Ask specifically whether this PTT CA is approved for Windows AIK enrollment and has been submitted to Microsoft.
Do not clear or reset the TPM merely for this 404. Microsoft warns that TPM wipe/reset troubleshooting can cause data loss,^3^ and it would not create a missing service authority. The October 2026 Windows fix for AIK enrollment hanging with a malformed third-party CNG provider is also a different symptom from a completed HTTP request receiving an explicit 404.^4^
References
- Windows AIK Certificate Enrollment Fails with 404 Not Found (Pluton TPM / MSFT-KeyId) - Microsoft Q&A
- Send feedback to Microsoft with the Feedback Hub app | Microsoft Support
- Windows enrollment attestation
- October 28, 2026—KB5127653 (OS Builds 28000.3365) Preview | Microsoft Support