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: Most helpful
  1. Anonymous
    2022-08-03T13:34:50+00:00

    Actually windows hello services does not have to use the webcam, it can also refer to IR Camera or the fingerprint scanner, regardless I get the windows hello events too (I am using IR face unlock) so this issue clearly corrupts drivers or internal device communication in some way or another

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-08-02T14:55:54+00:00

    Update:

    Normally I return to my PC in the morning and it has rebooted, however after disabling the Microsoft Account Sign-in Assistant and found my PC had not rebooted overnight. I'm not claiming this to be the answer but may be worth testing.

    Warning: I do not use a Microsoft account to login to my PC. If you do, this potentially could negatively impact you. Proceed with caution.

    Status: Device is still running. I will edit this post if it crashes once more.

    How to [screenshots below]:

    1. Press Windows Key + R on your keyboard to open the Run option.Image
    2. Type services.msc and press enter. This will open a new window with the header Services. Don't randomly stop and start services unless you enjoy potentially crashing your device.
    3. Find the service entitled Microsoft Account Sign-in Assistant. Double click the aforementioned service to open a new window for the Microsoft Account login service.![Image](https://learn-attachment.microsoft.com/api/attachments/60b8f214-4e51-47c3-89d0-bd14c193ef37?platform=QnA
    4. Press Stop.
    5. Change startup type from its' current setting to Disabled.![Image](https://learn-attachment.microsoft.com/api/attachments/91dd34fb-a617-446e-a6f1-e361f818e8f2?platform=QnA
    6. Press Apply followed by OK to close the dialogue box.
    7. Reboot your device and cross your fingers, send your thoughts and prayers, throw salt over your shoulder, or whatever else you do for good luck.

    I saw one guy putting Automatic (delayed start) does it work?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-08-02T13:11:44+00:00

    I encountered the same problem in Windows 10, the latest update. 136 errors in Event viewer this morning. So far. I have not found a solution to the problem.

    It appears - as usual - that Microsoft does not care. I ask myself what the programmer was programming here. Did he actually test it? I do not think so.

    The suggestion to reinstall W 10 or 11 is unacceptable. This is a programming error and can only be corrected by MS even though, it does not hinder normal operation in WiFi (in my case). So, MS please investigate and fix it.

    Maybe uninstalling the latest update and use the old update might help but need to test

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-07-31T17:11:23+00:00

    dllmain.cpp does not exist in Windows 11.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-07-25T01:53:03+00:00

    I don't know for certain, but I'm going to guess your system is not crashing because of this issue.

    Was this answer helpful?

    0 comments No comments