Share via

Microsoft-Windows-TPM-WMI "system cannot find the file specified" 1796 12238

tocguy 90 Reputation points
2025-10-20T18:01:54.2533333+00:00

OS: Win 11 24H2

Mobo: MSI X870e Carbon

CPU: 9950X3D

RAM: 48GB

Beginning on Oct 15th and every re-start that followed the subject event is logged indicating an issue with TPM. This is always the first event on a given start so it does not appear to be dependent upon a preceding event.

- <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event ">
- <System> <Provider Name="Microsoft-Windows-TPM-WMI" Guid="{7d5387b0-cbe0-11da-a94d-0800200c9a66}" />
<EventID>1796</EventID>
<Version>2</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-10-20T14:59:31.4518296Z" />
<EventRecordID>12238</EventRecordID>
<Correlation />
<Execution ProcessID="21816" ThreadID="20660" />
<Channel>System</Channel>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="HResult">-2147024894</Data>
<Data Name="UpdateType">1024</Data>
</EventData>
</EventUser's image

How to troubleshoot this event?

Windows for home | Windows 11 | Security and privacy
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Richard Trinidad 3,205 Reputation points Independent Advisor
    2025-10-20T19:09:54.6666667+00:00

    Hi Tocguy, Thanks for posting here in Microsoft community, possibly related to KB5066131 (.NET Framework) and KB5068332 (.NET 9.0.10) on Oct 14, you can try these steps.

     

    First, Uninstall KB5066835 simply go to Settings > Windows Update > Update History > Uninstall Updates then Remove KB5066835 after that Reboot and check if the TPM error disappears.

    Next, Check TPM & Secure Boot in BIOS then Enter BIOS (press Del or F2 during boot), next Ensure TPM is enabled look for AMD fTPM and Toggle Secure Boot off then reboot then then back on.

    Also, you can Pause Updates, In Windows Update, pause updates for a few weeks to avoid reinstallation until the issue is resolved.

     

    I hope this helps you out.

    Chard

  2. Richard Trinidad 3,205 Reputation points Independent Advisor
    2025-10-22T13:29:43.47+00:00

    Hi Tocguy, Thanks for the detailed update, it sounds like you’ve been thorough with the troubleshooting so far.

    Given that the TPM delay started before applying any of the suggestions and persists even after clearing CMOS and reinstalling BIOS, it’s likely we’re dealing with a deeper firmware or OS-level issue.

    Since the uninstall of KB5066835 fails, you might try removing it via DISM or Windows Update Standalone Installer in Safe Mode, if you haven’t already. Sometimes Safe Mode bypasses certain protections that block update removal.

    As for TPM, I totally understand your hesitation. Resetting TPM can be risky if you're unsure about the implications, especially with BitLocker or secure boot dependencies. Before considering a reset, it might be worth checking, TPM status in Windows (tpm.msc) does it show any errors or readiness issues? Event Viewer logs any consistent TPM-related warnings or errors?

    BIOS version is it the latest from the OEM? Sometimes even a minor revision can address TPM quirks.

    If all else fails and TPM functionality is critical, a clean OS reinstall might be the safest route but only as a last resort.

    Let me know what you find from those checks, and we can figure out the next best step.

     

    Chard

  3. Richard Trinidad 3,205 Reputation points Independent Advisor
    2025-10-22T16:18:47.6+00:00

    Hi Tocguy, sounds like you’ve exhausted most of the usual repair paths, at this point, a full clean install with firmware and disk prep might be the best shot.

    I’d recommend, backing up everything and doing a full format during install. and Using Rufus to create a bootable USB with bypass options, also resetting BIOS/UEFI, disabling Secure Boot temporarily, and clearing TPM if safe.

    Then running full disk diagnostics from another PC before reinstalling.

    After install, avoid CleanMgr and aggressive cleanup tools. If 24H2 still fails, maybe stick with 23H2 for now and block feature updates until Microsoft irons this out.

    Chard

  4. Richard Trinidad 3,205 Reputation points Independent Advisor
    2025-10-23T13:34:45.5033333+00:00

    Hi Tocguy, I hear your situation loud and clear, and you're right to expect better tools and support from Microsoft especially when dealing with something as critical as TPM errors after a clean install.

    You've done a commendable job digging into this, and it's baffling that there's no straightforward way to trace the root cause through logs or get meaningful help beyond “do a clean install.”

     The lack of transparency and diagnostic tooling for TPM-related issues is a real gap, and the automated support loop only adds to the frustration.

    Honestly, this kind of experience shouldn't be considered acceptable, especially when updates introduce regressions and users are left to fend for themselves, you're not alone feeling this way, and I hope Microsoft steps up with clearer guidance or a fix soon.

    Hang in there, and if you uncover anything new or need help exploring alternative routes like DISM or Safe Mode removal, feel free to reach out.

    Chard

    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.