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

Anonymous

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?

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

Anonymous

2022-10-26T18:57:27+00:00

Hello everyone. I thought I would add my voice to this fiasco created by Microsoft. Last night I was cleaning up files on my wife's HP Envy Laptop and behold I see 263 of these Event 1010 Autopilot.dll WIL errors. Her laptop is running Win 10 Home Version 22H2 OS build 19045.2193. I noticed that these errors did not start until the laptop was updated from 21H2 to 22H2 on Oct. 18th. I believe it had something to do with that Feature Update. Now I have an HP OMEN desktop running Win 10 Home with the same version and build as my wife's laptop and I updated my computer from 21H2 to 22H2 at the same time and I have not seen the Event 1010 errors on my Omen......yet. Now last night I updated our computers to Cumulative updates KB5018202, KB5018482 and KB4023057 and no fix for this error on wife's laptop seen. It seems to be always a problem or problems associated with monthly updates to where I cringe when cumulative updates come out or Patch Tuesday comes around. Users seem to be using more time chasing errors caused by Microsoft than enjoying their computer.

My question is has any Community Moderators escalated this up? Does Microsoft know that many users are experiencing this problem and has anyone from Microsoft even acknowledged this and are working on it? Has anyone submitted this problem via the Feedback Hub or heard back from them.

"MICROSOFT" WAKE UP AND ACKNOWLEDGE THIS PROBLEM TO THE USERS WHO SPENT HUNDREDS OR THOUSANDS OF DOLLARS FOR YOUR PRODUCT WHO ARE EXPERIENCING THIS AND TELL US WHAT IS BEING DONE TO CORRECT THIS AND WHEN IT WILL BE FIXED.

Respectfully
Was this answer helpful?

0 comments No comments
Anonymous

2022-10-26T14:16:52+00:00

Interesting. Have you had any errors related to your TPM implementation show up around this? And do you happen to use Visual Studio 2022?

My TPM version is 2.0. I don't have or use Visual Studio. I also don't use developer options or software

The error seems to trigger when I use a Microsoft App.
Was this answer helpful?

0 comments No comments
Anonymous

2022-10-26T12:40:22+00:00

My system is Intel based. Everything was fine on Windows 11 21H2. No modifications.

I'm Intel-based too. My issue started after an August update. This is prior to 22H2. I've subsequently updated to 22H2 but the problem persists.
Was this answer helpful?

0 comments No comments
Anonymous

2022-10-26T12:15:34+00:00

Interesting. Have you had any errors related to your TPM implementation show up around this? And do you happen to use Visual Studio 2022?
Was this answer helpful?

0 comments No comments
Anonymous

2022-10-26T12:14:36+00:00

Do you use fTPM and can you check on which version (curious if it's either 1.2 or 1.3)?

EDIT: Also, have you at any point used developer options or software, like Dev Mode in the advanced settings or Visual Studio Community or the latest 2022?
Was this answer helpful?

0 comments No comments