Repository navigation
PS7-packaged: pwsh not discoverable in SYSTEM / LocalSystem context #27562
Description
Summary
When PowerShell 7 is installed as an MSIX package, pwsh is not available in non-interactive system contexts. MSIX packages register per-user only — the SYSTEM account and other service identities cannot locate or invoke pwsh.
Affected scenarios
- Scheduled tasks running as SYSTEM
- Windows Services running as LocalSystem or a service account
- MDM-deployed scripts (Intune, ConfigMgr)
- Deployment agents and automation pipelines running in non-interactive contexts
Repro
From an elevated prompt:
psexec -s -i pwsh.exeExpected: PowerShell 7 launches.
Actual: The system cannot find the file specified.
Context
This is a known architectural constraint of MSIX packaging. We are working with the relevant Windows engineering teams on a resolution. We have internal tracking for this work and will update this issue as progress is made.
This is a blocker for the PS7 inboxing initiative.
Activity
ukdocCT commentedon Nov 11, 2026
Now that v7.7 is GA and there are still some major blockers on its deployment on a system wide basis, why has no MSI installer been made available?
Not being able to have system wide install will form a blocker for any enterprise deployment team and will severely restrict the take up of v7.7.
doctordns commentedon Nov 11, 2026
Sadly, Microsoft decided unilaterally to remove PowerShell's MSI. They were well aware that customers would have issues. Despite that, they did it anyway. They did not ask the community, nor is there a decent workaround. And since the fixes needed to make MSIX a suitable replacement are out side the ability of the PowerShell team to fix, the customers are left hanging. IMHO, the manager who signed off on this, without consulting the community first should be reassigned. And then maybe hire someone more community focused to bring back MSI (until MSIX parity is available).
In the meantime, we are left to figure this all out on our own. I suspect that MS will want to close this issue as ' Not Planned.