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

I agree 100% with what you said Kevin. By design my *** LOL. Thank you for your response.

Respectfully

I wish that were the case. But I was told that this behavior is by design. Also, I don't think any manufacturers can be blamed for a new error that pops up in Windows on machines that were manufactured in some cases, several years ago. It's been across numerous machines, AMD and Intel, and seems to span nearly every combination of parts.

Most of the time it is as you say and I'm usually the first to point that out but this one I'm pretty sure is entirely owned by MS. The funny thing is, my last reply to them nearly a month ago was that if it is intended behavior and letting us know something has been attempted that shouldn't be and it was stopped by design, the proper notation would be INFO and not ERROR. I just checked and as of today they never replied.

I can't speak for others but I dropped it into Feedback hub back in May. Moderators have told me that this error is by design. lololol Of course my response was that if that's the case and it's just dropping info that's supposed to be there, they could save a lot of time and energy wasted by many people by simply changing it to an INFO line instead of ERROR, pointing out that the word ERROR means that something isn't working as it should be.

Because there is some third-party involvement somewhere in here and for various, obvious reasons Microsoft can't acknowledge that (business/financial partnership reasons, NDA umbrella contracts, etc.) or the vendor or partner (thinking a major one, like an MSI, AMD, Intel, etc.) just hasn't had enough time or investment or luck or whatever in the debugging and patching during a huge transition to 11 and being compliant with 11 and all the vast changes in driver compatibility.

That all sounds like a big word mashup, but what I mean is the problem involves more than just Microsoft and their team working on patching and that maybe the other party just hasn't been provided the tools or time to do their part. Driver developers are my main suspect, and integral ones like AMD or Dell or someone working direct.

That's my overall guess on this, not just a technical guess. Although it clearly concerns a C++ compilation (just in time or on-demand compilation of something probably).

I have a Dell XPS 15 Windows 11 22H2 old 21H2 old windows 10 and exactly the same situation.

The problem has persisted for me in all versions'

I also wonder why Microsoft is completely silent.