Many persistent errors in Event Viewer after Windows 11 build 22598.ni_release.220408-1503: "Autopilot.dll wil error was reported"

Anonymous
2022-04-28T20:22:08+00:00

I used to be part of the the Windows 11 Insider Beta channel. After updating to build 22598.ni_release.220408-1503 I began to see the same error in Event Viewer extremely frequently:

The errors are all the same and read as follows:

Autopilot.dll WIL error was reported.

HRESULT: 0x80070491

File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 128

Message: NULL

I have never used any program called Autopilot or Modern Deployment. After seeing this problem I immediately left the insider program and am now queued for enrollment. However no new Windows update has happened and these errors persist. How do I prevent these errors?

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

338 answers

Sort by: Newest
  1. Anonymous
    2023-05-23T13:38:29+00:00

    Still, no solution! going on and on and on!

    This has worked for me...3 weeks later and no errors. Reset your TPM module.

    If I understood chris__74's 09-Feb-2023 post <above> (and Google Translate is accurate) they were able to stop these errors by resetting their TPM module . I haven't tried that yet, but on my Win 10 OS I assume a TPM reset can be done at at Windows Security | Device Security | Security Processor | Security Processor Details | Security Processor Troubleshooting and then clicking "Clear TPM" or by entering tpm.msc in a Run dialog box (Windows key + R) to open the TPM Management Console and clicking "Clear TPM". Have you tried this possible workaround? If these errors are related to the firmware for the TPM module on the motherboard then that might explain why your Windows 11 reinstall didn't stop the Autopilot.dll WIL errors.

    WARNING*: If you use* Bitlocker Disk Encryption and want to try resetting your TPM module I would advise that you suspend or disable Bitlocker first (e.g., at Control Panel | Security | Bitlocker Drive Encryption for Professional editions of Windows) and ensure that you have your 48-digit Bitlocker recovery key on hand before starting. Bitlocker is currently turned off on my Win 10 Pro v22H2 laptop and I have no idea what unexpected problems might arise if you reset your TPM module while Bitlocker is enabled.

    For chris_74, bonjour, merci pour l'information (now, back to English)

    For TSM007, attempted a TPM reset per the Windows Security process on 23May2023 as suggested by chris_74. The TPM reset was successful, but the Autopilot.dll WIL errors continue. Confirming NVFOX observation "Still no solution!" with my addition of "And none at MS are listening."

    Current device config:
    * Dell Alienware m17 R3
    * Processor: Intel(R) Core(TM) i9-10980HK CPU @ 2.40GHz/3.10 GHz
    * Installed RAM: 32.0 GB (31.8 GB usable)
    * Edition: Windows 10 Pro - Ver 22H2
    * OS build: 19045.2846

    All DELL Alienware system diagnostic/configuration bloatware apps are current as of 22May2023.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-05-23T05:39:07+00:00

    Still, no solution! going on and on and on!

    This has worked for me...3 weeks later and no errors. Reset your TPM module.

    If I understood chris__74's 09-Feb-2023 post <above> (and Google Translate is accurate) they were able to stop these errors by resetting their TPM module . I haven't tried that yet, but on my Win 10 OS I assume a TPM reset can be done at at Windows Security | Device Security | Security Processor | Security Processor Details | Security Processor Troubleshooting and then clicking "Clear TPM" or by entering tpm.msc in a Run dialog box (Windows key + R) to open the TPM Management Console and clicking "Clear TPM". Have you tried this possible workaround? If these errors are related to the firmware for the TPM module on the motherboard then that might explain why your Windows 11 reinstall didn't stop the Autopilot.dll WIL errors.

    WARNING*: If you use* Bitlocker Disk Encryption and want to try resetting your TPM module I would advise that you suspend or disable Bitlocker first (e.g., at Control Panel | Security | Bitlocker Drive Encryption for Professional editions of Windows) and ensure that you have your 48-digit Bitlocker recovery key on hand before starting. Bitlocker is currently turned off on my Win 10 Pro v22H2 laptop and I have no idea what unexpected problems might arise if you reset your TPM module while Bitlocker is enabled.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-05-22T19:02:00+00:00

    Still, no solution! going on and on and on!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-05-22T18:45:22+00:00

    Here is my post on Feedback Hub

    https://aka.ms/AAkqfpk

    JD

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-05-05T18:38:19+00:00

    nice! 👍

    Was this answer helpful?

    0 comments No comments