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

338 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-22T16:28:26+00:00

    Nothing yet from from our old friends from MS. Chances of that have diminished somewhat - see in press MS making a lot of staff redundant globally!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-22T15:45:41+00:00

    Yea, I noticed while playing Warhammer 3 that sometimes my PC would just hard freeze and just restart itself. I would note the time on my phone and then when I checked my event viewer there it was, error spam from autopilot. I also noticed other random instability issues on my PC, which are just freaking odd. I had something like 200+ errors from an entire day most all of them are autopilot.

    At first I thought maybe it was a bad PSU, or software issues. I updated all my drivers, updated my windows, and even monitored my voltages etc. Nothing seemed to work. I have since disabled the service and seeing if it helps anything. It's just super odd...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-16T02:38:57+00:00

    Tried this. Pretty much a disaster. All sorts of things stopped functioning.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-01-15T13:40:59+00:00

    I tried a full in place upgrade on recommendation from a chst with Microsoft tech. As soon as it finished and I opened Windows it froze with multiple instances of the error messages in event viewer. So it does not appear to be accumulated corruption - but an inherent problem. Waiting for a future update with this noted repair appears to be only recourse.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-01-10T13:52:58+00:00

    Overworking the thread to contribute observations in hope MS will provide some relief.

    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.2364

    No Autopilot.dll WIL errors displayed in ver Win10 Pro-21H2, installed since 11Dec2021. Applied Win10 Pro-21H2 Dec2022 Cumulative Update (KB5021233) with no errors appearing. Performed a feature update from Win10 Pro-21H2 to 22H2 on 07Jan2022. Immediately, the Autopilot.dll WIL errors started logging in [Microsoft-Windows-ModernDeployment-Diagnostics-Provider/ManagementService]. Receiving between 30 and 40 log entries per average 16 hour day. Always have entries at boot-up and shutdown.

    Microsoft Account Sign-in Assistant service has Startup type = Manual using Local System account permissions. Windows Updates are always paused. All Windows Hello features disabled. OneDrive not used (service active, never signed-in). No system hardware modifications (e.g., overclock of CPU/memory) in use. Current Dell BIOS version installed.

    Noticed a pattern of MS Edge updates in Task Scheduler correspond to some, but not all Autopilot.dll error log entries. Second pattern of error log entry is associated with the Software Protection service performing a license check for the start of any Office 365 products.

    On my system, these errors appear to simply be noise and do not cause any operational or performance issue (yet). Hoping this issue does not evolve into a longer term problem as the Win op/sys ages.

    Was this answer helpful?

    0 comments