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

I had some errors caused by the file MicrosoftEdgeUpdate.exe located C:\Users\User_Name\AppData\Local\Microsoft\EdgeUpdate

It has a launch through the task scheduler. Temporarily replaced MicrosoftEdgeUpdate.exe with old version 1.3.147.37

I have this version does not cause errors on startup.

After replacing the file, MS Edge keeps throwing errors on startup.

I am on Windows 10 Home 21H2 19044.1889 and began receiving LOTS of occurrences of this error after accepting last week's Patch Tuesday (KB5012170 and KB5016616).

I am 100% certain I never had them before these updates.

So this issue is (A) STILL present today, (B) ALSO present in Windows 10, and (C) is triggered by SOMETHING included in KB5012170 or KB5016616.

I can roll back to a restore point, but I accept these updates for the protection they provide. Also, I prefer not losing changes in other software since the update. So would like to avoid rolling back.

I hope a fix is on its way. Thank you in advance.

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?

This error is crashing my new Alienware computer!

There must be some way to disable this "feature" almost no one wants or needs.

Fortunately, if you have Apple devices for office&communications, you can fix your PC to use local login, uninstall Microsoft 365, remove the Microsoft ID from the PC, switch to Chrome or Firefox as your browser and those errors stop. Seriously, do we have to remove Microsoft from the PC to keep it running properly?

Why are these errors getting through to users? A few years ago MS were releasing updates containing various issues, then then promised MORE testing before release. We also have the INSIDERS who apparently get pre-releases to test, how come this issue has got through TWO so called 'TESTINGS'?

I discovered the same error on a Dell Laptop running Windows 11 Home 22000.856

I delved into the AutoPilot.dll file and saw what I believe to be the incorrect path. There's no hash after onecore, compared to another path referenced earlier:

Incorrect?

Referenced Example?

Potentially modified path?

Any thoughts?