PowerShell moves to MSIX
PowerShell 7.7 is shifting its default package format from MSI to MSIX and deprecating MSI installers, which affects how organisations deploy and manage PowerShell across endpoints. The change raises questions about existing deployment methods, script assumptions and rollback paths for administrators (windowsnews.ai).
Microsoft is dropping MSI installers for new PowerShell releases and making MSIX the default Windows package starting with PowerShell 7.7-preview.1 in April 2026. (devblogs.microsoft.com) The PowerShell team said on April 10, 2026 that MSI packages will continue for existing releases, including PowerShell 7.6, but are not planned for PowerShell 7.7 general availability or later. PowerShell 7.6, released March 12, 2026, still ships Windows MSI files alongside MSIX bundles. (devblogs.microsoft.com) (github.com) MSIX is Microsoft’s newer app packaging format, and the company says it uses a more predictable install model than MSI, which often depends on custom actions and scripts. Microsoft also said MSI does not meet its accessibility requirements, especially for screen-reader use. (devblogs.microsoft.com) For administrators, the change lands in the middle of a release process Microsoft says already spans 29 packages in eight package formats, four architectures, eight operating systems and four repositories. The team said packaging problems were part of what delayed PowerShell 7.6 into March 2026. (devblogs.microsoft.com) Microsoft is pitching MSIX as an enterprise deployment format, not just a consumer installer. Microsoft Learn says organizations can deploy MSIX packages through Microsoft Intune, Microsoft Endpoint Configuration Manager, App Installer and PowerShell, with standardized metadata, install strings and detection methods. (learn.microsoft.com) The command-line path also changes. Microsoft’s MSIX documentation points administrators to PowerShell cmdlets such as Add-AppxPackage for install and Remove-AppxPackage for removal, rather than the MSI workflows many Windows teams have scripted for years. (learn.microsoft.com) Microsoft also said MSIX does not yet cover every MSI scenario that PowerShell supported. The company specifically called out remoting and execution by system-level services such as Task Scheduler as gaps it still needs to address. (devblogs.microsoft.com) Older Windows environments have another wrinkle. Microsoft’s MSIX Core can install MSIX packages on Windows 7 Service Pack 1, Windows 8.1, supported Windows Server with Desktop Experience and Windows 10 versions earlier than 1709, but Learn says it only provides a subset of native MSIX features and does not include MSIX container benefits. (learn.microsoft.com) That leaves PowerShell 7.6 as the last branch with first-party MSI packages while Microsoft pushes Windows admins toward MSIX before PowerShell 7.7 reaches general availability. (devblogs.microsoft.com)
