OpenAI does document a way around this, and it comes from OpenAI itself rather than a mirror site. The company's enterprise Windows deployment guide includes an offline MSIX package, a matching license file and one PowerShell command. How2Shout recently published a walkthrough of that route. We checked it against OpenAI's documentation and Microsoft's own reference for the cmdlet. Here's how it works, where people get stuck, and what changes when you skip the Store.
First, a naming quirk: Codex now ships as "ChatGPT"
You'll download files called ChatGPT, not Codex. OpenAI's Help Center says that when you update the Codex app, it becomes the new ChatGPT desktop app, with Chat, Work and Codex in one window. Existing Codex chats and projects should carry over, and the updated app opens in Codex for existing Codex users.
The package names reflect that. OpenAI's deployment guide offers ChatGPT-x64.msix and ChatGPT-arm64.msix and describes them as the latest Store-signed package for each architecture. Inside Windows, the package identity is still OpenAI.Codex. OpenAI uses that name in its own removal example: Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'OpenAI.Codex' | Remove-AppxProvisionedPackage -Online -AllUsers
Two things to keep straight:
- ChatGPT Classic is a different app. OpenAI's Help Center says the previous ChatGPT desktop app can stay installed next to the new one under the name ChatGPT Classic. It still gets updates, but some new agent features only come to the new app.
- There's no official .exe or .msi. OpenAI's guide says standalone MSI and non-Store EXE packages aren't available for the desktop app. If a site offers you "Codex.exe," it isn't from OpenAI.
Summary: You're installing the new ChatGPT desktop app, which includes Codex. It comes as a Store-signed MSIX plus a license file, both hosted by OpenAI.
What you need before you start
- A Windows 11 PC with an account that has administrator rights. This method doesn't work without them.
- The right package for your processor: x64 for most Intel and AMD machines, Arm64 for Windows on Arm devices such as Snapdragon-based Copilot+ PCs.
- The offline license file,
ChatGPT-License.xml. You can't skip it. - Internet access afterwards. OpenAI is explicit that offline installation doesn't provide offline access to ChatGPT. "Offline" only describes how the app gets installed. You still need a connection to sign in and use it.
- The AppX Deployment Service (AppXSvc) enabled. This one comes from general Windows knowledge, not OpenAI's guide. Every MSIX install goes through AppXSvc, which is separate from the Store. If a hardening baseline has disabled AppXSvc, no MSIX will install, and changing that is your IT team's call.
Step-by-step: install Codex on Windows 11 without the Store
Step 1: Check your architecture
Open Settings > System > About and look at System type. It says either x64-based or ARM-based processor. This is the most reliable check.
How2Shout also suggests running $env:PROCESSOR_ARCHITECTURE in PowerShell, where AMD64 means x64 and ARM64 means Arm64. Treat that as a secondary check. Based on general Windows behaviour, a shell running under x64 emulation on an Arm PC can report AMD64, so trust the Settings page if the two disagree.
Step 2: Download the package and the license
All three files are on OpenAI's persistent.oaistatic.com domain, under the codex-app-prod path:
| File | Purpose |
|---|---|
ChatGPT-x64.msix | App package for Intel/AMD PCs |
ChatGPT-arm64.msix | App package for Windows on Arm PCs |
ChatGPT-License.xml | Offline license, required for either package |
Your browser may get in the way. How2Shout notes that clicking the MSIX can launch Windows App Installer, and clicking the XML usually just shows the license as text. In both cases, right-click and choose Save link as, or press Ctrl + S on the license page.
If you'd rather download from PowerShell, this is How2Shout's snippet for an x64 machine. On an Arm PC, change x64 to arm64 in the first URL:
New-Item -ItemType Directory -Path C:\Install\ChatGPT -Force
Set-Location C:\Install\ChatGPT
$ProgressPreference = 'SilentlyContinue'
Invoke-WebRequest -Uri [url]https://persistent.oaistatic.com/codex-app-prod/ChatGPT-x64.msix[/url] -OutFile ChatGPT.msix
Invoke-WebRequest -Uri [url]https://persistent.oaistatic.com/codex-app-prod/ChatGPT-License.xml[/url] -OutFile ChatGPT-License.xml
This saves the package directly as ChatGPT.msix, so there's nothing to rename later. If the target PC has no internet access, download the files on another machine and copy them over. The installation step itself works fully offline.
Step 3: Rename and keep both files in one folder
OpenAI's instructions: Rename the package to ChatGPT.msix and keep both files in the same folder. A short path such as C:\Install\ChatGPT makes typos less likely. Turn on file name extensions in File Explorer (View > Show > File name extensions) so you don't end up with ChatGPT.msix.msix.
Before installing, you can confirm the file is genuine: right-click ChatGPT.msix, open Properties > Digital Signatures, and check that the signature is valid.
Step 4: Run OpenAI's command from an elevated PowerShell
Open PowerShell or Terminal with Run as administrator, switch to your folder (Set-Location C:\Install\ChatGPT), and run the command from OpenAI's guide:
Add-AppxProvisionedPackage -Online `
-PackagePath .\ChatGPT.msix `
-LicensePath .\ChatGPT-License.xml `
-Regions all
The backticks at the end of each line are PowerShell line continuations, so you can paste the whole block at once. Microsoft's DISM documentation explains what each part does:
-Onlineapplies the change to the copy of Windows that's currently running, not to a mounted offline image.-PackagePathand-LicensePathpoint to the MSIX and the XML license.-Regions allmatters more than it looks. Microsoft's reference says that if you don't specify regions, the package is provisioned only if it's pinned to the Start layout. Leave out-Regions alland the install can appear to work but leave you with nothing usable.
Step 5: Sign out and sign back in
This is where many people get confused. Microsoft describes Add-AppxProvisionedPackage as adding a package that installs for each user, and the Advanced Installer packaging guide notes that a provisioned package is installed per user when they log into the device. OpenAI's guide says the same: Windows registers the provisioned package at sign-in.
If ChatGPT isn't in the Start menu, sign out and back in. How2Shout's author says a full restart also fixed it in their testing.
What success looks like: ChatGPT appears in Start, opens to a sign-in screen, and after you sign in, Codex appears next to Chat and Work.
Summary: Download, rename, run one elevated command, then sign out and back in. Leaving out -Regions all or the license file is the most common way to get this wrong.
Why this isn't the same as a Store install
Store installs are per-user and fairly self-contained. This method is a system-level change. The admin rights are needed because the app is being provisioned into Windows for every account on the PC, not just yours. On a shared family PC or a lab machine, every user will see ChatGPT at their next sign-in. You should know that before you run the command.
Updates behave differently too. OpenAI says the app still checks for updates by default after an offline install and downloads them from persistent.oaistatic.com. If a firewall or proxy blocks that domain, updates won't arrive, and you'll need to allow it or deploy newer packages yourself.
Troubleshooting the common failures
- "Requires elevation" errors, or 0x80073D28: How2Shout links 0x80073D28 to needing admin or System context. We couldn't confirm that mapping in OpenAI's documentation, but the fix is the same either way: run the command from an elevated window.
- Error 0x80070422 from the regular installer: How2Shout cites a community report where the standard installer and
winget install Codex -s msstoreboth failed with this code because the Microsoft Store Install Service had been disabled. Treat that as an anecdote, but it's exactly the situation the offline route exists for. - Path or "not found" errors: Check that you're in the right folder and that the files are named exactly
ChatGPT.msixandChatGPT-License.xml. - Tempted to use
-SkipLicense? Don't. Microsoft's documentation says it should only be used with apps that don't require a license on Enterprise or Server editions, and that using it in other cases can compromise an image. - Install fails on a Snapdragon laptop: You probably downloaded the x64 package. Check System type in Settings again.
- App still missing after you sign back in: Run
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'OpenAI.Codex'from an admin window to see whether provisioning actually happened. - ChatGPT opens but Codex isn't there: Make sure you didn't open ChatGPT Classic. On a work account, also check with your admin. OpenAI's Help Center says the new app doesn't change a workspace's existing access permissions or governance controls, so an admin may have restricted Codex.
- Got the package from a mirror like store.rg-adguard.net? Delete it and download from OpenAI. How2Shout mentions a user whose mirrored package installed without its license and then wouldn't open.
For IT admins: the managed-deployment route
The same offline package works with your device-management tools. OpenAI's guide covers Intune and Configuration Manager:
- Intune: To let users install from Company Portal, OpenAI recommends deploying the offline package as a Windows app (Win32) with an Available for enrolled devices assignment. A script version of the command uses
$PSScriptRootpaths, and OpenAI says to set Install behavior to System, and target the package's architecture. - Configuration Manager: Use the Windows app package deployment type, not the Store-link type.
- A note on Store blocking: OpenAI points out that blocking access to the Microsoft Store app does not prevent deployment through Intune's Microsoft Store integration. So a Store block on its own doesn't force you onto the offline route.
- Pilot first: OpenAI's advice is to confirm that employees can open ChatGPT under their normal Windows accounts before expanding deployment.
Third-party patching tools may not help here. In 2025, Patch My PC told customers asking for this app that it does not currently support MSIX installers, and supports the deployment of apps in .EXE, .MSI, or .MSP formats only. That may have changed since, so check before you rely on it.
Just want the terminal? Install Codex CLI instead
If you don't need the graphical app, Codex CLI avoids both the Store and the admin prompt. OpenAI's GitHub repository describes it as a coding agent that runs in your terminal, and gives this Windows install command:
powershell -ExecutionPolicy ByPass -c "irm [url]https://chatgpt.com/codex/install.ps1[/url] | iex"
Contenox's Windows guide says the script installs into your user profile and adds it to your user PATH, so a regular, non-admin PowerShell window is enough. Open a new window afterwards, run codex --version to confirm it installed, then run codex in a project folder and sign in. You don't get the graphical interface or the Chat and Work modes.
The bottom line
If the Store is the only thing stopping you from installing Codex, this method solves it, and it's an approach OpenAI documents itself, not a hack. The costs are admin rights, a device-wide install that every user on the PC will see, and handling updates yourself if your network blocks OpenAI's update domain. If those are fine, use the official MSIX and license. If you don't have admin rights, either ask your IT team or use the CLI.
References
- Download Codex for Windows 11 Without the Microsoft Store: Official MSIX and PowerShell Install Guide - H2S Media H2S Media · 2026-11-16T17:03:20+00:00
- Moving to the new ChatGPT desktop app | OpenAI Help Center help.openai.com
- github.com github.com