A Windows 11 desktop shows side-by-side PowerShell 5.1 and PowerShell 7 windows beneath an “Experimental build” preview banner.
Microsoft has released Windows 11 Insider Preview Build 29712.1000 to the Experimental (Future Platforms) channel. The release notes are short. They mention "a small set of general improvements and fixes" without listing any of them, and then say: PowerShell 7 is now in Windows.

For anyone who has kept two shells, two profile folders and two sets of module paths side by side for years, that's a significant change. It's also an early experimental build, though, so this article covers both what changed and how much of it you can rely on yet.

A Windows 11 desktop shows side-by-side PowerShell 5.1 and PowerShell 7 windows beneath an “Experimental build” preview banner. What Build 29712.1000 contains​

According to Microsoft's release notes, dated November 20, 2026:

  • General improvements and fixes. Microsoft says only that they improve the experience for Insiders running the build. There is no list, no KB number and no hardware or scenario detail. It would be pure guesswork to say what they fix, so we won't.
  • PowerShell 7 is now in Windows. This is the only named change. Microsoft points readers to the PowerShell team's blog for the details.
  • Gradual rollout. Microsoft marks the changes as rolling out over time. The notes say many features use Controlled Feature Rollout, which starts with a subset of Insiders and expands as Microsoft monitors feedback. Installing the build doesn't guarantee you get every change right away, and the notes don't mention any setting to force it.

The usual Experimental channel caveats apply. Microsoft says these builds can be unstable and may ship with limited documentation. They reflect platform work early in development and "shouldn't be seen as matched to any specific release of Windows." Features may change, be removed or never ship beyond Insiders. The desktop watermark is normal for pre-release builds, and some new features may not be fully localized yet. Report localization problems through Feedback Hub.

About Flight Hub: when we checked, Microsoft's Flight Hub still showed Build 29708.1003 from November 13 as the newest Future Platforms entry. The build-specific release notes for 29712.1000 are clear about the date, so treat this as Flight Hub lagging behind, not as a sign the build wasn't released.

Section summary: a light build with one important change. The unnamed fixes stay unnamed, and the PowerShell change may not reach every Insider at once.

PowerShell 7 in Windows: the announcement behind the change​

The build notes follow an announcement from the PowerShell team on November 17. Senior product manager Jason Helmick wrote that beginning with the next release of Windows, PowerShell 7 will be included as the upgrade for Windows PowerShell 5.1. The Windows team has published the details in KB5137172. Build 29712.1000 appears to be the first Insider build where Microsoft says that has happened.

The PowerShell team's main message is about compatibility: PowerShell 7 is designed to be used side by side with Windows PowerShell 5.1. Your existing automation needs no changes. Windows PowerShell 5.1 continues to run your scripts, scheduled tasks, and services, and you move to PowerShell 7 when you're ready. Techzine's coverage spells out the practical result: PowerShell 5.1 will remain available as powershell.exe, while PowerShell 7 runs via pwsh.exe.

That executable split is what keeps old automation working. A scheduled task that calls powershell.exe still runs 5.1. Nothing gets moved to PowerShell 7 unless you deliberately call pwsh.exe.

The deprecation behind it​

KB5137172 does more than announce PowerShell 7. Techzine describes it as a support document that marks Windows PowerShell 5.1 as deprecated. According to Microsoft, version 5.1 will remain part of Windows for now. For new scripts and automation, the company recommends PowerShell 7. According to German IT firm s-edv, the KB says Windows PowerShell 5.1 is no longer under active development and will receive no new features. It also names Windows Server 2025 and Windows 11 version 26H2 as the last Windows versions that include PowerShell 5.1 as a built-in, enabled-by-default component.

The change only applies to future releases. Asked in the blog comments about older clients, Helmick replied that this is forward only. Earlier versions, including 26H2, keep Windows PowerShell 5.1, which remains supported and receives security updates per each Windows version's lifecycle.

Section summary: PowerShell 7 is being added next to 5.1, not replacing it outright. Version 5.1 is now officially deprecated, but existing Windows versions keep it and continue to get security updates.

Known gaps in PowerShell 7 in Windows​

This is the part admins should read carefully. PowerShell 7 is delivered as an MSIX package, and the PowerShell team says MSIX doesn't yet match the older MSI installer in three areas. Work is in progress on:

GapWhy it matters
Running as the SYSTEM accountAffects scheduled tasks, services, device-management scripts and remoting
DISM cmdlets (for example Add-WindowsCapability)Common in imaging and feature-provisioning scripts
Machine-wide settings (for example the all-users profile)Affects standardized environments across a whole machine

The PowerShell 7.7 release on November 10 shows how much these gaps matter. When a user asked about installing system-wide, Helmick said installing for all users and service accounts wasn't yet supported by the MSIX package, and he suggested the 7.6 MSI in the meantime. He also called MSIX on Windows Server Core a known gap. Comments on that post were openly frustrated. Several admins said they would stay on 7.6 until the MSI-to-MSIX transition is fixed.

These are PowerShell packaging issues. Microsoft hasn't said that Build 29712.1000 introduces or fixes any of them. Still, a PowerShell that can't yet run as SYSTEM won't take over your Intune remediation scripts or service-account jobs anytime soon.

Section summary: the inbox PowerShell 7 works well for interactive and user-context use. Automation that runs as SYSTEM, needs DISM cmdlets or relies on machine-wide settings should stay on 5.1 or the MSI-based 7.6 until Microsoft closes these gaps.

What admins should do now​

You don't need to run an Experimental build to start preparing. Based on the PowerShell team's guidance:

  1. Take inventory. Find scheduled tasks, services, installers and management agents that call powershell.exe or load Windows PowerShell modules. s-edv notes that KB5137172 itself recommends this step.
  2. Test before you migrate. The PowerShell team says many scripts run unchanged in PowerShell 7, some need changes, and some may have to stay on 5.1. Running a script in PowerShell 7 is the only reliable way to find out which group it falls into.
  3. Check the differences documentation. Microsoft's guides on the differences between 5.1 and 7.x, and on migrating from 5.1, cover modules, profiles and remoting.
  4. Don't count on the ISE. In the blog comments, Helmick said the Windows PowerShell ISE is built for 5.1, won't switch to PowerShell 7, and isn't supported with it. He recommends Visual Studio Code with the PowerShell extension, which has an ISE mode.
  5. Ask the owning product teams. When readers asked about SharePoint Online, RSAT and SCOM support for PowerShell 7, Helmick said those modules belong to their own product teams and that feedback should go to them directly.
  6. Report what breaks. The team is starting an Inbox Working Group to triage issues that affect PowerShell 7 in Windows, and it collects feedback in the PowerShell GitHub repository.

Microsoft also says it is working on inventory and analysis tools, including better compatibility checks in PSScriptAnalyzer. It describes these as coming "as it's ready," so don't plan around them yet.

Our take​

This change has been a long time coming. For years, the PowerShell that shipped with Windows was the one Microsoft had stopped developing, while the actively developed version had to be installed separately. Shipping PowerShell 7 in the box fixes that mismatch.

There are fair objections. Shipping PowerShell 7 inside Windows while its packaging still can't do SYSTEM-context or all-users installs is a bit like delivering a new car before the seatbelts are fitted. The side-by-side approach and the forward-only promise reduce the risk considerably, though. Nothing on 24H2, 25H2 or 26H2 changes underneath you, and powershell.exe keeps meaning what it always has.

Build 29712.1000 itself is minor: a few unspecified fixes and one important addition, rolling out gradually on a channel Microsoft says isn't tied to any shipping release. Its value is as an early chance to test PowerShell 7 in Windows. If you have spare hardware, try your scripts on this build now and find out which ones still depend on 5.1.

 

References

  1. Windows 11 Insider Experimental Future Platforms Preview Build 29712.1000 Microsoft Learn - Windows Insider release notes 2026-11-20T18:05:27Z
  2. PowerShell 7 will be included by default in the next Windows release - Techzine Global techzine.eu
  3. PowerShell 5.1 abgekündigt: was Admins jetzt planen s-edv.com