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

Question

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?

Answer 1

Because they don't know what "a.." stand for! 😂

I think they do know at MS. I have other examples where they don't move their A..! For them, we the users are a bunch of idiots. So why take care of us resp. take us seriously?

Answer 2

MS a monopoly, and 99% of their users who have this error have no idea that this problem even exists. We are the 1% that are not the idiots, and I think MS knows that, but they have to take care of the other 99% first.

(Of course, as soon as I start bragging about being smart, I accidentally do something really idiotic (which keeps me humble). I wonder what it will be this time... )

Answer 3

I know a fair amount about coding. Building a huge (really huge) application like Windows involves probably nearly billions of individual machine language instructions. One of the original coding levels for Windows apparently had an error in it, an error that was likely unfindable and required either rewriting Windows or writing a workaround. I discovered one and tried to report it; and was ignored, but the error was remedied within the year, ostensibly by a workaround.

I have little doubt that these workarounds left Windows vulnerable and that these vulnerabilities have been what made Windows susceptible to so many viral attacks. And still the only solution would be to dive impossibly deep into the present coding.

The problem - my guess - is that simply removing a sequence of problematic code would very likely make things worse rather than better. So the best strategy would be to come up with another workaround and patch up the problem. But there are probably other areas that need work in terms of new developments and they may be focusing on that first.

I really don't think it's arrogance for the simple reason that it doesn't pay off in the long run. It might be a mistake to ignore this issue and they might realize that soon. Or it may be that this error will be fixed since so many more users are noticing the problem. I will say that after two years of observing this issue, I cannot attach a single behavioral issue to it. Yes, there have been some issues that seemed related (inevitable coincidences), but everyone of them turned out to be related to something different, such as the computer company (not MS) and was rectified by the company.

For me, I've finally stopped worrying about the issue (essentially, it appears to be a message that relates a problem because it is treating me as though I was a company with all my computers networked, but it doesn't get verification, hence it aborts the attempt). But no discernible home.

Best,

Michael

Answer 4

MarkDaniels2 - Notice you reinstalled 31st May which means you have not received June's WUD's. Be interesting to se if that update brings back the issue when June updates come thru'.

Answer 5

Well thanks for letting us know you've personally given up. The rest of us are still holding out for a solution.