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

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.

I am suffering this issue now for several weeks. Event Viewer just full of Autopilot.dll WIL errors. Really regretting my upgrade to Win 11.

I live in hope - and disgust at the lack of action.

Or even some admission of guilt.

Yours tearfully.

Poor MS employees! I burst into tears! I say this: Fix it, fix it, fix it! It is absolutely unnecessary what is happening here... as usual. Who at MS really cares? Certainly not the CEO or any other management. Why am I having over 1600 unnecessary errors in the Event viewer?

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.

Of course I agree that it should be fixed. And I think it will.

We have to remember the context here: Microsoft has thousands of people spending all their time thinking of ways to pull users and their information into the Microsoft datatank. They lose sleep over the very thought that some users escape their reach. They will make even the smallest Hello World app sign into your Microsoft Account, and thus become part of the Windows data suction plumbing. And preferably as automatically and discreetly as possible, so users don't decide to disable it or uninstall the app.

Like with Android, that is the entire purpose of Windows. (And yes, I am an Android and Gmail user as well.)

Evidently, this Sign-in Assistant service is an integral part of the plumbing used to facilitate the data suction. I think there is a good chance Microsoft will fix this to keep the suction running as smoothly and quietly as possible, and avoid threads like this, and avoid people disabling the auto sign-in service like we're doing here.

I kept Microsoft Account Sign-in Assistant disabled, and except for Edge being unable to sign-in and sync (which I can live with for a while) I have had no other problems so far. No other Edge problems, and no other error events.

I didn't have any crashes or other issues, even before disabling the service (about a week after receiving the update). And my PC runs 24/7, only rebooted after the monthly Patch Tuesdays.

I keep everything from Microsoft uninstalled, disabled and/or logged out, unless I specifically need it, such as OneDrive. Again, I use a local Windows account. Maybe Office 365 or some of the other apps that rely on the Sign-in Assistant are the ones causing instability when they are unable to phone home like they were designed to do.