Beginning with PowerShell 7.7-preview.1 (April 2026), the MSIX package will be the primary installation method for PowerShell on Windows. We will no longer ship the MSI installer package for new PowerShell releases.
For existing releases, including PowerShell 7.6, we will continue to provide MSI packages. However, MSI isn’t planned for future releases, including PowerShell 7.7 GA and beyond.
Why we’re making this change
MSIX provides a modern installation and servicing model and is supported by Windows deployment tools. It uses a declarative model that’s more predictable and reliable than MSI, which relies on custom actions and scripts that can lead to inconsistent behavior. MSIX supports built-in update mechanisms with differential updates. Microsoft is investing in improving MSIX.
MSI is a legacy technology. Servicing MSI installations requires external tooling and often results in full reinstalls. MSI doesn’t meet modern accessibility requirements, particularly for screen reader scenarios. To be accessible, MSI must present predictable tab stops and accurate announcements for screen readers, which it doesn’t. Accessibility is a core requirement for PowerShell.
This decision isn’t just about modernizing packaging for its own sake. It’s about ensuring that PowerShell installations are modern and accessible for all users, now and in the future.
Looking forward
Our goal is to provide a fully accessible, reliable, and enterprise-ready installation experience. At this time, MSIX doesn’t support all use case scenarios that MSI enabled, such as remoting and execution by system-level services (like Task Scheduler). We recognize this gap and are actively working to address it.
As part of this work, we’re investing in:
- Improving MSIX support for system-level and enterprise deployment scenarios
- Ensuring accessibility requirements are fully met across all installation paths
- Providing clearer guidance and tooling for deployment at scale
We will continue to share updates as this work progresses.
Closing
We understand this change may require adjustments, especially in environments that rely heavily on MSI-based deployment. We appreciate your patience as we make this transition.
Our focus is to ensure PowerShell remains accessible, predictable, and practical for all users.
— The PowerShell Team
