›_ Codex Issues
Codex Issues / #39458

[Windows ARM64] Codex 26.814 fails after Code Integrity rejects AutoSuperResolution SNPE.dll

Open 💬 0 comments Opened Aug 19, 2026 by MasatoMiyata

What version of the Codex App are you using (From “About Codex” dialog)?

26.814.5167.0 Microsoft Store/MSIX package: OpenAI.Codex_26.814.5167.0_arm64__2p2nqsd0c76g0

What subscription do you have?

ChatGPT Pro 5x

What platform is your computer?

Windows 11 26H1, OS build: 28000.2704, Architecture: ARM64, CPU: Snapdragon X2 Elite (X2E78100), GPU: Qualcomm Adreno X2-85, Codex package architecture: ARM64, Microsoft Auto Super Resolution package: Microsoft.AutoSuperResolution_1.0.11.0_arm64__8wekyb3d8bbwe. Auto Super Resolution is disabled in Windows Settings.

What issue are you seeing?

Codex Desktop on Windows ARM64 becomes unlaunchable after ChatGPT.exe attempts to load SNPE.dll from the Windows Microsoft.AutoSuperResolution package.

Windows Code Integrity rejects SNPE.dll with Event ID 3033 because the binary does not meet the signing level required by the Codex ChatGPT.exe process.

The Codex MSIX package then changes from:

Status : Ok

to:

Status : DependencyIssue

and subsequent attempts to launch Codex fail with AppModel Runtime error 0x3CFC.

The relevant Code Integrity Event 3033 is:

Event ID: 3033

ProcessNameBuffer =
\Device\HarddiskVolume3\Program Files\WindowsApps\
OpenAI.Codex_26.814.5167.0_arm64__2p2nqsd0c76g0\
app\ChatGPT.exe

FileNameBuffer =
\Device\HarddiskVolume3\Program Files\WindowsApps\
microsoft.autosuperresolution_1.0.11.0_arm64__8wekyb3d8bbwe\
SNPE.dll

RequestedPolicy = 8
ValidatedPolicy = 1
Status = 3221226536 (0xC0000428)

The correlated Event 3089 reports:

ValidatedSigningLevel = 6
VerificationError = 16

PublisherName = Microsoft Corporation
IssuerName = Microsoft Marketplace CA G 022

This occurs repeatedly when attempting to launch Codex.

What steps can reproduce the bug?

The following sequence was reproduced on this ARM64 machine.

  1. Restore the Codex package so that it reports:
Get-AppxPackage OpenAI.Codex |
Format-List Name,Version,Status

Result before launching Codex:

Name    : OpenAI.Codex
Version : 26.814.5167.0
Status  : Ok
  1. At the same time, the Windows Auto Super Resolution package reports:
Get-AppxPackage Microsoft.AutoSuperResolution |
Format-List Name,Version,Status

Result:

Name    : Microsoft.AutoSuperResolution
Version : 1.0.11.0
Status  : Modified, NeedsRemediation
  1. Confirm that Automatic Super Resolution is disabled in:
Settings
→ System
→ Display
→ Graphics
→ Automatic Super Resolution
  1. Launch Codex Desktop.
  1. Codex does not successfully open.
  1. Windows Code Integrity immediately records Event ID 3033 for:
ChatGPT.exe
→ Microsoft.AutoSuperResolution\SNPE.dll

with:

RequestedPolicy = 8
ValidatedPolicy = 1
Status = 0xC0000428

and correlated Event 3089:

ValidatedSigningLevel = 6
VerificationError = 16
  1. Check the Codex package again:
Get-AppxPackage OpenAI.Codex |
Format-List Name,Version,Status

It has changed to:

Name    : OpenAI.Codex
Version : 26.814.5167.0
Status  : DependencyIssue
  1. The AppModel Runtime subsequently reports 0x3CFC machine-level package-status errors and Codex remains unlaunchable.

This behavior has also persisted after uninstall/reinstall, Reset-AppxPackage, DISM, and SFC repair attempts.

A Windows recovery initially restored normal Codex operation, but the same failure later returned.

What is the expected behavior?

Codex Desktop should launch normally on supported Windows ARM64 systems.

If Windows attempts to load a Store/catalog-signed system component such as Microsoft.AutoSuperResolution\SNPE.dll, it should not conflict with the binary-signature policy applied to the Codex ChatGPT.exe process.

A failure to load an optional graphics/AI component should also not:

  • change the Codex MSIX package to DependencyIssue;
  • trigger 0x3CFC;
  • permanently prevent subsequent launches.

Since Automatic Super Resolution is disabled in Windows Settings, Codex should also not depend on successful loading of this component in order to start.

Additional information

SNPE.dll signature

PowerShell reports no embedded Authenticode signature:

Get-AuthenticodeSignature SNPE.dll

Result:

Status : NotSigned

SHA-256:

1139711A34A1AD6998B804958E7C2A5F0C678C2248FB9CDFADA581018A990B3C

However, the AutoSuperResolution MSIX catalog is correctly signed.

Get-AuthenticodeSignature `
  "...\Microsoft.AutoSuperResolution_1.0.11.0_arm64__8wekyb3d8bbwe\
AppxMetadata\CodeIntegrity.cat"

Result:

Status : Valid

Signer:
Microsoft Corporation

Issuer:
Microsoft Marketplace CA G 022

Therefore this does not appear to be simple package corruption or an invalid MSIX signature.

Instead, Windows Code Integrity appears to validate the component at signing level 6 while the Codex process requests policy level 8:

RequestedPolicy       = 8
ValidatedPolicy       = 1
ValidatedSigningLevel = 6
VerificationError     = 16
Status                = 0xC0000428

Package-state evidence

After failure:

Microsoft.AutoSuperResolution
PackageStatus : 2

and:

OpenAI.Codex
PackageStatus : 64

BinaryName :
...\Microsoft.AutoSuperResolution_1.0.11.0_arm64__8wekyb3d8bbwe\
SNPE.dll

Before launching Codex after package-state recovery:

AutoSuperResolution : Modified, NeedsRemediation
Codex               : Ok

Immediately after attempting to launch Codex:

AutoSuperResolution : Modified, NeedsRemediation
Codex               : DependencyIssue

This strongly correlates the Codex package-state transition with the Code Integrity rejection of SNPE.dll.

Relationship to existing Codex issues

This appears related to the existing Windows Code Integrity issues:

  • #34133
  • #35701

Those reports show a very similar pattern involving Codex ChatGPT.exe, Code Integrity Event 3033, and:

RequestedPolicy       = 8
ValidatedPolicy       = 1
ValidatedSigningLevel = 6
VerificationError     = 16
Status                = 0xC0000428

However, those reports involve the Codex-packaged vk_swiftshader.dll.

This ARM64 case is different because the rejected DLL is a Microsoft Windows component:

Microsoft.AutoSuperResolution\SNPE.dll

and the problem occurs even though Automatic Super Resolution is disabled.

This may indicate an interaction between the binary-signature mitigation applied to the Codex ChatGPT.exe process and a Store/catalog-signed Windows Auto Super Resolution component on Snapdragon/ARM64 systems.

I have intentionally not disabled Windows Code Integrity or weakened system security as a workaround.

I can provide sanitized Event 3033/3089 XML and AppModel/AppX logs if needed.

View original on GitHub ↗