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
{count} votes

338 answers

Sort by: Most helpful
  1. 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????

    0 comments No comments
  2. 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?

    0 comments No comments
  3. Anonymous
    2022-08-23T14:46:37+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.

    This ^

    0 comments No comments
  4. Anonymous
    2022-08-23T15:16:10+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?

    Thank you for confirming that you're seeing this with a Microsoft account.

    My main reason for mentioning that I use a local account and the fact that I minimize the number of apps logging into my Microsoft account, is to stress that this allows me to disable the Microsoft Account Sign-in Assistant with few adverse effects.

    You disable the service by opening SERVICES.MSC, locate Microsoft Account Sign-in Assistant in the list, right click and select right-click > Properties > Startup type > Disable. You can also stop the service right there, but I prefer restarting Windows after making such changes.

    For me, the only adverse effect of disabling the service is that Edge no longer signs in and syncs, which I can live with. Until MS fixes this, I will just temporarily enable the service once a month in order to sync my Edge settings, before accepting Windows Updates, then disable it again after the updates if the error is still present.

    0 comments No comments
  5. Anonymous
    2022-08-24T06:33:59+00:00

    Hallo AustinTran

    es ist wirklich zum Verzweifeln, auch ich habe genau dieselben Probleme, so wie Sie es beschrieben haben. Schon seit Tagen versuche ich das Problem zu lösen, doch leider ohne Erfolg. Microsoft sollte wenigsten mehr Infos über dieses Problem herausgeben.

    0 comments No comments