Windows Codex APP installation error

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #13575

Powered by Codex Action

我也遇到了这个问题，不知道该怎么解决

If the Microsoft Store install/update path is blocked, there is an unofficial mirror that publishes the current Windows MSIX package here:

• Project: https://github.com/Wangnov/codex-app-mirror
• Latest Windows package: https://codexapp.agentsmirror.com/latest/win

It is not an official OpenAI installer, but it may help as a temporary workaround when Store/winget cannot fetch the Codex Desktop package.

You can decode it using the decoding platform via the Microsoft Store Codex URL to bypass store installation; I've already resolved it, thank you.

I hit a very similar Microsoft Store 0x80080005 install failure and found one concrete Windows-side root cause.

In my case the Store error was caused by broken Windows Update/BITS services. BITS and wuauserv failed to start with SCM event 7023 / The specified module could not be found. Procmon showed SCM launching C:\Windows\SysWOW64\svchost.exe -k netsvcs -p -s BITS, which then looked for C:\Windows\SysWOW64\qmgr.dll. That was wrong because these services should be hosted by the 64-bit System32\svchost.exe and load the 64-bit DLLs.

The bad registry value was WOW64=0x14c on these Windows services:

• BITS
• wuauserv
• UsoSvc
• WaaSMedicSvc

This fixed it for me without a reboot:

# Run in an elevated PowerShell.
$services = 'BITS','wuauserv','UsoSvc','WaaSMedicSvc'
$backup = "$env:TEMP\codex-store-0x80080005-service-backup-$(Get-Date -Format yyyyMMdd_HHmmss)"
New-Item -ItemType Directory -Path $backup | Out-Null

# Back up first and inspect the suspicious value.
foreach ($s in $services) {
  reg.exe export "HKLM\SYSTEM\CurrentControlSet\Services\$s" "$backup\$s.reg" /y
  reg.exe query "HKLM\SYSTEM\CurrentControlSet\Services\$s" /v WOW64
}

# Only do this if the query above shows WOW64 REG_DWORD 0x14c on these Windows svchost services.
foreach ($s in $services) {
  reg.exe delete "HKLM\SYSTEM\CurrentControlSet\Services\$s" /v WOW64 /f
}

Start-Service BITS,wuauserv,UsoSvc,WaaSMedicSvc
Get-Service BITS,wuauserv,UsoSvc,WaaSMedicSvc

Optional verification:

$session = New-Object -ComObject Microsoft.Update.Session
$searcher = $session.CreateUpdateSearcher()
$result = $searcher.Search("IsInstalled=0 and Type='Software'")
$result.HResult

After deleting those four WOW64 values, BITS, wuauserv, UsoSvc, and WaaSMedicSvc all started successfully, Windows Update COM search returned 0x00000000, and the Store/Codex install path worked again.

Caution: do not remove WOW64 globally from every service. Some third-party 32-bit services may legitimately have it. This workaround is specifically for the Windows Update/BITS svchost services being incorrectly forced into the 32-bit host.

Failures trace to disabled Windows Store/Update services, not Codex.