To clarify, though, this is just an issue for people who are deliberately getting preview builds (aka beta testers), correct? The article feels pretty click-baity with that critical detail not part of the title.
With that said, I get that things go bad in betas - this is the point of a beta release - but this still feels egregiously bad. It also highlights the direction Windows is going, which is cause for criticism even if this worked perfectly.
It's right there.
Sure, it relies on the surrounding context that Windows 11 is in beta, but that's pretty common knowledge.
like, even in a buggy system, it shouldn't happened, and there is clearly not enough isolation, something that isn't gonna get fixed in a release candidate and be prepared for this to somehow turn into a ring0 exploit later down the line.