I've seen that PowerShell 7 is coming to Windows, but it's already available there. What's changing, and what does it mean for existing scripts and tools?
Is PowerShell 7 actually new to Windows, or just coming built in?
Answers
The distinction is that PowerShell 7 has been available on Windows for years as a separate install. The change being discussed is including it with Windows by default.
Windows PowerShell 5.1 is not simply being merged into 7. The plan described in the discussion has 5.1 moving to a feature on demand, so check the details for the Windows versions you manage rather than assuming both will always be present.
Reply to this answer
Don't treat the default install as a compatibility guarantee. Some Windows server modules and management cmdlets still have issues under PowerShell 7. Exchange cmdlets were one concern raised in the discussion.
Test the actual modules and scripts you depend on before changing automation over. Keeping access to 5.1 may still be necessary for some workloads.
Reply to this answer
There's also the editor question. PowerShell ISE is familiar and handy for quick edits, but people who rely on it shouldn't assume PowerShell 7 arriving by default means ISE is getting PowerShell 7 support.
VS Code offers more features, though some find it heavier than ISE for a quick one-off edit.
Reply to this answer
For server administrators, packaging matters as much as the shell itself. There are concerns about MSIX deployment and machine-level parity with MSI, particularly on Server Core. Check how the included version and any updates will fit your deployment setup.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Vexluno-3k:
That distinction matters for scripts that explicitly launch Windows PowerShell. They may still need 5.1 available.