PowerShell 7.7 moves to MSIX
PowerShell 7.7 is shifting to MSIX as the default installer and is deprecating MSI packages, a change that will affect enterprise deployment, software distribution and update workflows. Analysts say packaging changes like this typically appear first as deployment friction for large organisations. (windowsnews.ai)
Microsoft will make MSIX the default installer for PowerShell starting with PowerShell 7.7 and will stop shipping MSI packages for new releases. (devblogs.microsoft.com) The PowerShell team announced the change on April 10, 2026 and said it begins with PowerShell 7.7-preview.1 in April 2026. (devblogs.microsoft.com) Microsoft said MSIX is a “modern installation and servicing model” that is more predictable than MSI, supports differential updates, and better meets accessibility requirements. (devblogs.microsoft.com) The blog also warned that MSIX today does not cover every scenario MSI enabled, specifically remoting and execution by system-level services such as Task Scheduler. (devblogs.microsoft.com) Packaging specialists note enterprises often face compatibility and remediation work when moving formats, with MSIX projects frequently uncovering legacy dependencies that require repackaging. (turbo.net) Microsoft and third parties say MSIX is supported by Windows deployment tools and can integrate with Intune and System Center Configuration Manager for enterprise distribution. (petri.com) There is an ecosystem of tooling—Microsoft’s MSIX Toolkit on GitHub and third‑party packagers—to help convert and manage MSIX packages at scale. (github.com) The PowerShell team said it will keep providing MSI for existing releases like PowerShell 7.6 while it invests in MSIX support for system-level and enterprise scenarios, and it will publish guidance as work progresses. (devblogs.microsoft.com)
