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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-08-23T14:46:17+00:00

    Quick search on community appears to show three current threads for this subject with AutoPilot.dll mentioned a number of times in various contexts, some of them posted by MS re updates etc.. has this being going on longer than we think?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-23T14:25:40+00:00

    To repeat: no workarounds! Or shutting off services. MS fix it and no longer ignore this error since it is produced by you, MICROSOFT.

    The question is whether MS loses quality. Everything appears to go automatically. Human interference disappears. Where is the big call for QUALITY in Windows 10 or 11????

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-23T14:14:38+00:00

    It is because his posts are untrustworthy. He doesn't provide any documentation or rationale.

    Never delete a file or run a code if you are not 100% sure of what that will do exactly. Generally, don't take any post written here, which suggests interfering with your system, at face value.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-08-23T14:01:22+00:00

    This issue is not exclusive to users who have only a local account.

    I have this error(s, they are increasing exponentially!) as well and I use a Microsoft account to log in.

    Specifications: Windows 11, Version 21H2, build 22000.856

    I also confirmed that the process responsible for the error is wlidsvc (Microsoft Account Sign-in Assistant).

    The only difference in my error log is that the error occurs at line 138, rather than 128.

    How can you disable the Sign-in Assistant?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-08-19T16:22:07+00:00

    I kept Microsoft Account Sign-in Assistant disabled, and except for Edge being unable to sign-in and sync (which I can live with for a while) I have had no other problems so far. No other Edge problems, and no other error events.

    I didn't have any crashes or other issues, even before disabling the service (about a week after receiving the update). And my PC runs 24/7, only rebooted after the monthly Patch Tuesdays.

    I keep everything from Microsoft uninstalled, disabled and/or logged out, unless I specifically need it, such as OneDrive. Again, I use a local Windows account. Maybe Office 365 or some of the other apps that rely on the Sign-in Assistant are the ones causing instability when they are unable to phone home like they were designed to do.

    Was this answer helpful?

    0 comments