If the argument is to try to prohibit it, then it just won't work as a platform, because too much existing software won't work on it. There's a lot of garbage I'd love to not have (all the stupid hardware config apps all the manufacturers push on you) but just having that functionality not work can't be the answer.
Similar pet peeve, and I think the solution to this is the platform setting, adopting, and enforcing conventions. Something like what has happened with notebook trackpads[1] about a decade ago, and more recently RGB peripherals[2]—no more cancerous giant Electron app to move a few sliders and set an RGB hex code.
[1]: https://learn.microsoft.com/en-gb/windows/win32/input-precis...
[2]: https://learn.microsoft.com/en-gb/xbox/gdk/docs/features/com...
That said, knowing Microsoft they WOULD release something like this but cripple it by doing something stupid like disallowing the use of virtualization technology, even as an installed package.
I disagree. .NET is fundamental to the Windows platform. It's like having a Python runtime installed by default in some Linux distros, which makes sense for that distribution's use-case.