{"id":21040,"date":"2026-11-17T12:07:20","date_gmt":"2026-11-17T20:07:20","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/powershell\/?p=21040"},"modified":"2026-11-17T12:07:20","modified_gmt":"2026-11-17T20:07:20","slug":"powershell-7-coming-to-windows","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/powershell-7-coming-to-windows\/","title":{"rendered":"PowerShell 7 is coming to Windows"},"content":{"rendered":"<p><!-- markdownlint-disable MD041 --><\/p>\n<p>PowerShell 7 is coming to Windows. Beginning with the next release of Windows, PowerShell 7\nwill be included as the upgrade for Windows PowerShell 5.1. The Windows team has published the details in <a href=\"https:\/\/support.microsoft.com\/help\/5137172\">KB5137172<\/a>.\u00a0Here is what this means for you, your scripts,\nyour automation, and where our work stands.<\/p>\n<h2>The top question we always get asked<\/h2>\n<p>For years, PowerShell has lived in two places. Windows PowerShell 5.1 is the one in the box, and\nit has carried a great deal of the world&#8217;s automation: the scheduled tasks, services, and admin\nscripts that have run quietly for years. PowerShell 7 is the modern PowerShell: the one we develop\nin the open, across platforms, and where new features go.<\/p>\n<p>Bringing those together has been the request we heard most from you: the PowerShell that comes with\nWindows should be PowerShell 7. Including PowerShell 7 in Windows is a milestone we&#8217;ve been working\ntoward since PowerShell went cross-platform. But we couldn&#8217;t have reached this milestone without\nyour persistent requests.<\/p>\n<h2>What happens to your scripts?<\/h2>\n<p>Nothing. PowerShell 7 is designed to be used side by side with Windows PowerShell 5.1. Your existing\nautomation needs no changes. Windows PowerShell 5.1 continues to run your scripts, scheduled tasks,\nand services, and you move to PowerShell 7 when you&#8217;re ready.<\/p>\n<h2>What we&#8217;re still finishing<\/h2>\n<p>Windows PowerShell 5.1 earned its place as the trusted automation platform for Windows, and\nPowerShell 7 needs to earn its place too. PowerShell 7 is delivered as an MSIX package. MSIX still\nneeds work to match some things that worked with the MSI installer. We&#8217;re working to close these\ngaps:<\/p>\n<ul>\n<li>Running as the SYSTEM account, which affects scheduled tasks, services, device-management scripts,\nand remoting<\/li>\n<li>Support for the DISM cmdlets, such as <code>Add-WindowsCapability<\/code>.<\/li>\n<li>Support for machine-wide settings, such as the all-users profile.<\/li>\n<\/ul>\n<p>These changes are in progress now. We track the status of each in the <a href=\"https:\/\/github.com\/PowerShell\/PowerShell\/issues\/27565\">MSIX tracking issue<\/a>.<\/p>\n<h2>When you&#8217;re ready to move<\/h2>\n<p>Many scripts run in PowerShell 7 without changes. Some need changes before they work, and some may\nneed to keep running in Windows PowerShell 5.1. That&#8217;s because Windows PowerShell 5.1 and\nPowerShell 7 differ in some places.<\/p>\n<p>Test your scripts in PowerShell 7 before you move them. That&#8217;s how you find out which kind you have.<\/p>\n<p>If a script of yours depends on one of those differences, we have documentation to help you decide\nwhat to do:<\/p>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/powershell\/scripting\/whats-new\/differences-from-windows-powershell\">Differences between Windows PowerShell 5.1 and PowerShell 7.x<\/a> lists the differences<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/powershell\/scripting\/whats-new\/migrating-from-windows-powershell-51-to-powershell-7\">Migrating from Windows PowerShell 5.1 to PowerShell 7<\/a> covers how the two run side by side,\nincluding modules, profiles, and remoting<\/li>\n<\/ul>\n<p>Knowing which of your scripts, if any, need a change is the harder job, especially across many\nmachines. To help you with that, we are investing in community-built tools, documentation, and\nimprovements to PSScriptAnalyzer&#8217;s compatibility checks. Together they are meant to cover three\nthings:<\/p>\n<ul>\n<li><strong>Inventory:<\/strong> find what you have, including scheduled tasks and services.<\/li>\n<li><strong>Analysis:<\/strong> flag what in your scripts needs attention before it runs in PowerShell 7.<\/li>\n<li><strong>Guidance:<\/strong> for each finding, what to change and why.<\/li>\n<\/ul>\n<p>We&#8217;ll share each piece, with documentation, as it&#8217;s ready.<\/p>\n<h2>Inbox Working Group<\/h2>\n<p>We&#8217;re starting an Inbox Working Group to triage issues that affect PowerShell 7 in Windows. The job\nof this group is to make sure that the issues you report reach the people who can act on them.<\/p>\n<h2>Run your scripts, tell us what you find<\/h2>\n<p>The best way to know how your scripts will do is to run them in PowerShell 7. We want your\nfeedback. Follow our progress and describe your issues in our GitHub repository:\n<a href=\"https:\/\/github.com\/PowerShell\/PowerShell\/issues\">PowerShell\/PowerShell<\/a>. We&#8217;re listening.<\/p>\n<p>The PowerShell Team<\/p>\n","protected":false},"excerpt":{"rendered":"<p>PowerShell 7 is coming to Windows, beginning with the next release of Windows.<\/p>\n","protected":false},"author":7527,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3201],"class_list":["post-21040","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-powershell-windows"],"acf":[],"blog_post_summary":"<p>PowerShell 7 is coming to Windows, beginning with the next release of Windows.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/21040","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/7527"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=21040"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/21040\/revisions"}],"predecessor-version":[{"id":21042,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/21040\/revisions\/21042"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=21040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=21040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=21040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}