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

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.

Same issue on two computers. The first runs win11 22H2 build 22622.575 and the second win10 build 19044.1889.

The problem on the Win10 pc leading to kernel critical errors and system restarts once per day. Disabling Microsoft signin assistant service eliminates the errors AND the system crashes but has major side effects (problems with Office 365, cant sign in on Game pass etc).

At least i haven't experienced system crashes on the win11 pc.

Chill out people! It takes time to diagnose and fix bugs, then test them and get them into the servicing pipeline. You don't want to rush a fix and then create an even bigger problem. And yes, it can be a problem to get proper attention paid to a new issue.

How many of you have used the Feedback tool to report this issue? If not then do so now. All you need to do is search for the event error and +1 the issue. That's it. That will draw attention to the problem. Be part of the solution.

Update 8/3/2022: My device has crashed and rebooted unexpectedly once in 24 hours. Thus far disabling the service has provided a huge boost in stability. Troubleshooting and diagnosing continues. There are two interesting alerts (on my device) for Windows Hello for Business right as the device crashes.

• The driver \Driver\WudfRd failed to load for the device ROOT\WINDOWSHELLOFACESOFTWAREDRIVER\0000
• Windows Hello for Business provisioning will not be launched.

I explicitly choose not to configure Windows Hello, so why it is even trying to load a driver is confusing to me, outside of the fact that clearly Microsoft wants access to your webcam regardless of what you tell it during install.