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

I'm really sick of this error. It keeps making my games gag when it occurs, and sometimes even crashes them. As soon as I get a crash I open the windows event tool and see that the error ocurred exactly at the same time.

It's been a while now and patches haven't fixed this issue.

Also, this bs is completely random. I reinstalled windows and it popped up on a fresh windows install while in an old install I had, this error didn't exist at all, and now I'm suddenly plagued by it causing all sort of anomalies in my system.

Autopilot.dll wil error was reported.

HRESULT: 0x80070491

File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 138

Message: NULL

This morning at starting my laptop, event viewer recorded 139 errors, event id 1010.

I think MS does not care a bit to fix this at all. Why for heaven's sake?????

I am still on Windows 10 & also getting the issue so not specific to your upgrade to version 11, for items recorded in event viewer commence on restart after installing August WUD's on 10th August, no entries prior to this. I don't appear to have the issue on an old Windows 8.1 laptop but that is close to EOS - sometimes wonder if you are better turning off monthly updates altogether, years ago when WUD's did not exist, computers had no problems. Once again, fair to assume that this is something initiated by MS for some underhand reason.

Being bit of a nerd, try & keep records of updates etc:

August 5th - MS Edge Webview2Runtime appeared automatically in Programs & Features

August 7th - Edge Update

August 8th - MS Edge Webview2Runtime update

August 10th - Installed August WUD's (UK based - get on first boot Wednesdays)

August 10th - Noticed issue when checking event viewer, issue started immediately after re-boot - no history prior to this time & date.

August 13th - Edge Update

August 14th - MS Edge Webview2Runtime update

Edge settings Start Up Boost OFF, Background Extensions OFF - both of these if ON apparently means when CLOSING Edge, it is not really closed, but still runs in background, supposedly to make opening Edge quicker to open & loading last opened web-pages.

Checked this morning, issued first recorded timed as on boot-up, did not load Edge till 10-15 minutes after.

Been mention of using Feedback hub - between January & December last year had issue with WassMedic. 533 postings on community, 4075 views. THREE responses from some-one allegedly working for MS, all three near identical word for word. Numerous postings of logs being submitted, no acknowledgments or progress reports from MS, another case of MS deserting users. Issue finally sorted last December - still no MS response that issue had been fixed.

I know only one thing. MS appears not interested in fixing it. Typical for MS.

Workarounds are not good enough, fixing it is the subject.