PowerShell 7.7: transition to MSIX instead of MSI

# PowerShell 7.7 Switches to MSIX Instead of MSI for Installation

Microsoft is changing its approach to PowerShell installation: starting with version 7.7-preview.1, available at the end of this month, MSI installers will become a thing of the past. MSIX will be used by default — a format that provides greater predictability and reliability in deployment.

Advantages of MSIX over MSI

MSIX offers a modern servicing model with differential updates, which minimizes the amount of downloaded data and simplifies updates. MSI, on the other hand, relies on custom scripts, which often leads to inconsistent installation behavior.

Key differences:

• Built-in updates: MSIX supports incremental patches without full reinstallation.
• Accessibility: Complies with modern WCAG standards, unlike MSI, which requires external tools.
• Predictability: Less reliance on custom scripts reduces the risk of failures in enterprise environments.

MSIX still falls short of MSI in some scenarios: it lacks full support for system services like the Task Scheduler or remote connections. Microsoft is investing in improvements.

Plans to Address MSIX Limitations

The company is focusing on key areas for enterprise deployments:

• Support for system-level installation and corporate policies.
• Full compliance with accessibility requirements in all scenarios.
• Tools and guidelines for scalable deployment.

These improvements will make MSIX a full replacement for MSI. Existing PowerShell 7.6 versions will retain MSI packages, but for 7.7 and above, MSIX will become the standard.

The transition will affect environments with automated MSI deployments but will increase stability. Developers and sysadmins will be able to use familiar tools like Winget or direct MSIX packages from the Microsoft Store.

Key Points

• Installation standard: PowerShell 7.7 uses MSIX by default, MSI remains for legacy versions.
• Differential updates: Simplify servicing without full reinstallation.
• Enterprise focus: Microsoft is improving system scenarios and accessibility.
• Predictability: Reducing script dependency minimizes deployment errors.
• Compatibility: The transition is gradual, without immediate discontinuation of MSI.

This shift reflects the overall trend in the Windows ecosystem toward unified packages. MSIX integrates with modern tools like Intune and SCCM, which is relevant for mid/senior DevOps specialists.

— Editorial Team