Windows: Codex Desktop and CLI crash with 0xC0000005 in Avest CSP avsspc.dll

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

Версия 26.825.51511

What subscription do you have?

plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

После обновления падал desktop и точно так же падал CLI. Вся проблема была в Avest. Решение: добавить в Avest в исключениях codex.

Environment

• Windows x64
• Codex Desktop for Windows
• Codex CLI 0.152.0
• Model: gpt-5.6-sol
• Avest CSP installed
• avsspc.dll version: 6.1.3.1697

Problem

Both Codex Desktop and Codex CLI crashed immediately or shortly after starting a request.

Desktop showed the Restart screen.

CLI returned silently to PowerShell.

Example:

codex -s read-only exec --skip-git-repo-check "Reply with one word: works"

The request was submitted, but codex.exe exited before receiving the response.

codex doctor also crashed at:

Checking desktop...

Exit code:

-1073741819

which corresponds to 0xC0000005 (ACCESS_VIOLATION).

Windows Event Viewer

Faulting application:
codex.exe

Faulting module:
C:\Program Files\Common Files\Avest\Avest CSP\avsspc.dll

Module version:
6.1.3.1697

Exception code:
0xc0000005

Fault offset:
0x0000000000013ca9

This happened repeatedly with the same module and offset.

Workaround

Adding:

codex.exe

to the Avest CSP process exclusion file fixed the problem immediately.

Path:

C:\Program Files\Common Files\Avest\Avest CSP\process

After adding the exclusion:

• Codex CLI started working
• codex exec completed successfully
• Codex Desktop started responding normally
• Windows reboot was NOT required

Expected behavior

Codex should either be compatible with Avest CSP injection or detect/report the incompatible DLL instead of crashing with an access violation.

It may also be useful to document Avest CSP as a known Windows compatibility issue.

What steps can reproduce the bug?

Решение: добавить в Avest в исключениях codex

What is the expected behavior?

No response

Additional information

No response

Start by reproducing the crash on Windows with Avest CSP installed, using codex, codex doctor, and the provided codex exec command. Check the Windows Event Viewer details for avsspc.dll and compare behavior with the codex.exe process exclusion; done means the crash is prevented or the incompatible DLL is clearly detected and reported.