I've run into several compatibility issues because I installed the "new" PowerShell from the windows store, as it constantly nags you to do, and it's not fully

I've run into several compatibility issues because I installed the "new" PowerShell from the windows store, as it constantly nags you to do, and it's not fully compatible with the one that ships with Windows. Just yesterday some chocolatey packages failed to install when chocolatey was invoked from the new PowerShell, but succeeded when chocolatey was invoked from the old one, for some godforsaken reason. Microsoft should have just adopted an existing shell. They may have problems but the problems are well known and workarounds are well known too. PowerShell is NIH syndrome in action. It has an equally large set of different problems that are unknown. It's a whole new set of quirks and workarounds to learn when you just want to get something simple done. The only good thing I have to say about it is that it respects my "ls" and Ctrl-R muscle memory.