Platform / 平台
Windows
OS version / 系统版本
Windows 11 Home China, 25H2, build 26200.8894, 64-bit
CPU / 架构
Windows x64
Codex Desktop version / source / Codex 桌面版版本或来源
Microsoft Store official package OpenAI.Codex 26.721.4979.0 (Status: Ok)
Dream Skin version / 皮肤工具版本
Official Release v1.5.6; installer SHA-256 e0b2dc47ec775a160ae620455ecc2433462595be1ab61a1122212f071efab947 (matches official SHA256SUMS.txt)
Problem category / 问题类型
Install failed / 安装失败
Self-check / 自检
Steps to reproduce / 复现步骤
- Download
CodexDreamSkin-Setup-v1.5.6.exe from the official GitHub Release and verify its SHA-256.
- Run the installer with the default destination and leave “Start Codex Dream Skin when I sign in” unchecked.
- When Setup reports that Codex is running, close Codex completely and click Retry.
- Setup begins initialization, then shows the PowerShell error below and aborts with exit code 1.
Expected behavior / 期望结果
The installer should load the system Microsoft.PowerShell.Security module, validate the bundled Node.js runtime signature, and complete installation.
Actual behavior / 实际结果
Dream Skin first shows this error:
在模块“Microsoft.PowerShell.Security”中找到“Get-AuthenticodeSignature”命令,
但无法加载该模块。有关详细信息,请运行
“Import-Module Microsoft.PowerShell.Security”。
Setup then reports:
Runtime error (at 9:623):
Codex Dream Skin could not be initialized (exit code 1).
No installed application files were changed.
Modified official Codex install? / 是否改过官方 Codex 安装?
No — official app only / 否,仅官方安装
Logs / Verify / doctor output(recommended)/ 日志与校验输出(强烈建议)
The installation aborts before the runtime is committed, so no Dream Skin verify/doctor log is available.
Host-side diagnostics after the failure:
Windows PowerShell: 5.1.26100.8894
Import-Module Microsoft.PowerShell.Security -ErrorAction Stop: succeeded
Get-Command Get-AuthenticodeSignature: succeeded
Bundled payload node.exe:
Status: Valid
Signer: CN=OpenJS Foundation, O=OpenJS Foundation,
L=San Francisco, S=California, C=US
After the failure, the following were absent:
%LOCALAPPDATA%\Programs\CodexDreamSkin
%LOCALAPPDATA%\CodexDreamSkin
HKCU uninstall registration for Codex Dream Skin
PowerShell 7.6.4 from Microsoft Store is also installed, but the direct validation above was explicitly run with 64-bit Windows PowerShell 5.1 and succeeded. The installer source appears to target {sysnative}\WindowsPowerShell\v1.0\powershell.exe, so this may be an installer-process module-loading/environment issue rather than a missing Windows component.
Screenshots / video / 截图或录屏
Attached:
- The
Microsoft.PowerShell.Security / Get-AuthenticodeSignature error dialog.
- The subsequent Inno Setup
exit code 1 dialog.
The screenshots contain no API keys, private chats, usernames, or private filesystem paths.
Extra context / 其他信息
- The installer itself is unsigned, as documented by the release page.
- No security check was bypassed and no system security setting was changed.
- Manual signature verification of the bundled Node.js binary succeeded, so the failure appears to be command/module auto-loading inside the installer bootstrap context.
Confirmation / 确认
Platform / 平台
Windows
OS version / 系统版本
Windows 11 Home China, 25H2, build 26200.8894, 64-bit
CPU / 架构
Windows x64
Codex Desktop version / source / Codex 桌面版版本或来源
Microsoft Store official package OpenAI.Codex 26.721.4979.0 (Status: Ok)
Dream Skin version / 皮肤工具版本
Official Release v1.5.6; installer SHA-256 e0b2dc47ec775a160ae620455ecc2433462595be1ab61a1122212f071efab947 (matches official SHA256SUMS.txt)
Problem category / 问题类型
Install failed / 安装失败
Self-check / 自检
Steps to reproduce / 复现步骤
CodexDreamSkin-Setup-v1.5.6.exefrom the official GitHub Release and verify its SHA-256.Expected behavior / 期望结果
The installer should load the system
Microsoft.PowerShell.Securitymodule, validate the bundled Node.js runtime signature, and complete installation.Actual behavior / 实际结果
Dream Skin first shows this error:
Setup then reports:
Modified official Codex install? / 是否改过官方 Codex 安装?
No — official app only / 否,仅官方安装
Logs / Verify / doctor output(recommended)/ 日志与校验输出(强烈建议)
The installation aborts before the runtime is committed, so no Dream Skin verify/doctor log is available.
Host-side diagnostics after the failure:
After the failure, the following were absent:
PowerShell 7.6.4 from Microsoft Store is also installed, but the direct validation above was explicitly run with 64-bit Windows PowerShell 5.1 and succeeded. The installer source appears to target
{sysnative}\WindowsPowerShell\v1.0\powershell.exe, so this may be an installer-process module-loading/environment issue rather than a missing Windows component.Screenshots / video / 截图或录屏
Attached:
Microsoft.PowerShell.Security/Get-AuthenticodeSignatureerror dialog.exit code 1dialog.The screenshots contain no API keys, private chats, usernames, or private filesystem paths.
Extra context / 其他信息
Confirmation / 确认