Skip to content

Powershell from Microsoft Store is causing problems on Codex. #27603

Open
Open
Powershell from Microsoft Store is causing problems on Codex.#27603
Labels
Needs-TriageThe issue is new and needs to be triaged by a work group.Package-MSIXIssue occurs with MSIX package

Description

@kasumikira
kasumikira
opened on Jun 15, 2026

Prerequisites

Steps to reproduce

See openai/codex#9062. Since MSIX has become the default install method for PowerShell via winget, this behavior is likely to affect more users.

Expected behavior

Powershell starts successfully.

Actual behavior

execution error: Io(Custom { kind: Other, error: "windows sandbox: runner error: CreateProcessAsUserW failed: 1920" })

Error details



Environment data


Name                           Value
----                           -----
PSVersion                      7.6.2
PSEdition                      Core
GitCommitId                    7.6.2
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0


Visuals


No response
Activity
  1. kasumikira
    added 
    Needs-TriageThe issue is new and needs to be triaged by a work group.
     on Jun 15, 2026
  2. 237dmitry commented on Jun 15, 2026 
    @237dmitry
    237dmitry
    on Jun 15, 2026
    I heartily sympathize with you, but this is Microsoft's policy.
  3. jhoneill commented on Jun 17, 2026 
    @jhoneill
    James O'Neill (jhoneill)
    on Jun 17, 2026
    

    I heartily sympathize with you, but this is Microsoft's policy.
    

    

    I just installed from the MSIX for the first time and the newly installed version is ignored by VSCode and by Windows terminal .
    

    Jeffery Snover liked to say Microsoft wasn't capable of sustained error, but this smacks of being a decision made by people who won't need to live with it.  It adds to a growing feeling of disappointment with those in charge. I can only hope the MSIX distribution is the price to pay for the current version being distributed with Windows.
  4. 237dmitry commented on Jun 17, 2026 
    @237dmitry
    237dmitry
    on Jun 17, 2026
    I also hope that these difficulties associated with the decision to abandon MSI-packages will sooner or later cease to be a topic of discussion. And that users will forget about the inconvenience.
  5. jhoneill commented on Jun 17, 2026 
    @jhoneill
    James O'Neill (jhoneill)
    on Jun 17, 2026
    

    I also hope that these difficulties associated with the decision to abandon MSI-packages will sooner or later cease to be a topic of discussion. And that users will forget about the inconvenience.
    

    

    You can always hope. I can see the bank I just retired from working at saying "See! we told you it was better to keep everything on Windows PowerShell 5."  You run the MSIX, Terminal and VS code keep on using the old version, what are people going to do, spend time working out how to fix or just keep on using the old version.
  6. Ryan Yates (kilasuit)
    added 
    Package-MSIXIssue occurs with MSIX package
     on Jun 20, 2026
  7. Karl-WE commented on Sep 21, 2026 
    @Karl-WE
    Karl Wester-Ebbinghaus (Karl-WE)
    on Sep 21, 2026
    That this early change causes headache in terms of fallback and forget aka user adoption is a good point. Thanks for the incompatibility report.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    Needs-TriageThe issue is new and needs to be triaged by a work group.Package-MSIXIssue occurs with MSIX package
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions