3 people reported
All time, since Sep 28.
Opaque blocked by policy rejection
“This report requests diagnostics and safe remediation guidance, not a way to bypass policy.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/15101/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Windows exec_command rejected as blocked by policy without a reason. Commands are rejected before the PowerShell process starts with "CreateProcess ... rejected: blocked by policy", with no reviewer rationale or denying rule shown.
Is this your bug?
File my report- Where
- exec_command on Windows
- Error text
exec_command failed: CreateProcess ... Rejected ... rejected: blocked by policy- Versions
- 26.1013.31256
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Part of: Windows opaque blocked-by-policy rejections4 bugs
Original reports3, newest first
- Windows: pre-execution policy rejection lacks actionable diagnostics for bounded Gradle test invocationOn GitHub#56513
- Windows: blocked by policy on legitimate PowerShell file creation despite Unrestricted AccessOn GitHub#54543
- Windows app: opaque policy denial while preparing an owner-approved maintenance scriptOn GitHub#48974