Accessing powershell is not the issue - that Windows is broken, with a sprinkle of bad permission management by corporations using it is the issue. And the bad permission practices are a direct result of how broken Windows is - I tried a while ago to use it with a fully unprivileged user, just like I do for decades on UNIX and now Linux. It pretty much is impossible without privilege elevation prompts every few minutes.

In a proper environment a user should be able to destroy data they’re working with - but not have the ability to alter the operating system.

Shit like that is how you got here in the first place. To make computers easy enough to be fool proof is to make them nearly useless and requires someone to administer the system (even if that someone is the genius bar at apple.)

The issue isn’t access, its literacy. This shit was acceptable 20-30 years ago. But we’re at the point where everyone who’s at working age has spent most of if not all of their adult life at a time where basic computer use was considered a standard skillset.

Now that mobile OS’s have been the norm for a decade or so, we have comp sci students who can’t even navigate a fucking file explorer despite growing up on the internet.

Hand-holding design is a positive-feedback loop.

That being said you should probably disable, or at least severely limit their use for standard users in a corporate environment via group policy.

That’s not a hot take, that’s empirical fact: https://lifehacker.com/this-chart-shows-how-computer-literate-most-people-are-1789761598

You can’t in S mode

This is similar to how casual users on Windows should be limited to a non-admin account, to limit vectors for malware.

Isn’t it what happens on Mac? I’m told there is a command line on there, but I’ll be damned if I’ve ever met* a Mac addict who’s heard of it, let alone used it.