Windows 11--most recently opened Explorer window keeps popping up into the foreground

I have the same problem, and I can reproduce it when having 2 explorer windows in the background and running gpupdate.

Edition Windows 11 Enterprise

Version 22H2

OS build 22621.2134

Windows Feature Experience Pack 1000.22659.1000.0

We have also observed the same symptom on Windows 10 running in Virtual Box nodes every now and then for the last three years. There, gpupdate does NOT trigger the effect though. Very annoying when it happens during User Interface Integration tests, because it makes the tests fail if it happens in the wrong moments...

Mine happens when I move the mouse... The mouse glitches for a few milliseconds like vibrating.

you know what's funny...

as Microsoft continues to ignore us, we as a community are figuring out by ourselves how to remedy the situation with File Explorer
we haven't come up with a proper fix yet, but we have been able to figure out that using /gpupdate forces File Explorer to the foreground on Windows 11 Enterprise and Pro Versions
Unfortunately we haven't found the true culprit yet as Windows 11 Home cant replicate the same thing using /gpupdate (trust me, I've tried)
so there is something else causing it to happen within the OS itself

we have come this far, and Microsoft support has all but refused to lend a few of their team in helping figuring out this conundrum
its sad to see this happen this way, but at the end of the day, we've came together to try and figure this out by ourselves...and in doing so, we've done more than they have since the issue started waaaay back in October of last year (possibly later or earlier for others)

...it really makes you wonder if this issue can only be fixed by removing some kind of windows feature that when disabled will trigger some sort of security vulnerability and Microsoft hasn't been forthright with us because they can't seem to find a way to fix it without causing a potentially high security risk within their infrastructure.

its pure speculation, but its the only reasonable explanation I can come up with as to why they went completely silent on this

...it really makes you wonder if this issue can only be fixed by removing some kind of windows feature that when disabled will trigger some sort of security vulnerability and Microsoft hasn't been forthright with us because they can't seem to find a way to fix it without causing a potentially high security risk within their infrastructure.

its pure speculation, but its the only reasonable explanation I can come up with as to why they went completely silent on this

Azure Flair, thank you for the thoughtful response. If this is indeed a side-effect of a security solution (that Microsoft won't own up to), then that brings to mind the old metaphor, "Killing the dog to get rid of its fleas."

Would I recommend Windows 11? No, I would not recommend Windows 11 nor any other Microsoft product given this and other ongoing issues; 2023 may be the year users ask, What the heck happened to Microsoft?

When are these сodemonkeys going to fix this?