Blocked by policy, no rule shown

“The surfaced result did not include a numeric OS error, matched rule, policy ID, decision source, or actionable remediation.”

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/13915/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

Quiet. No reports in the last two weeks, down from 1 a week at the early-October peak.

exec_command rejected as blocked by policy with no rule shown. Launching a local desktop app was rejected at CreateProcess before the process existed, and no matched rule, policy ID, or approval path was returned.

Is this your bug?

File my report

Where: exec_command tool
Error text: exec_command failed: CreateProcess; rejected: blocked by policy
Platforms: Windows
How bad: Breaks a normal workflow. Some reports say it blocks them completely.

Part of: Windows opaque blocked-by-policy rejections4 bugs

Unexplained blocked by policy58 people
Opaque blocked by policy rejection3 people
PowerShell commands rejected when a URL and start appear together3 people

Not quite your bug?

Server start blocked by policy2 people

Original reports3, newest first

Oct 20, 2026Windows desktop: local QA app Start-Process rejected before PowerShell creation without policy provenanceOn GitHub#55721
Oct 17, 2026Windows: native application acceptance blocked before execution with no actionable approval pathOn GitHub#54942
Oct 4, 2026Windows 0.154.0-alpha.6.2: pre-process policy denial lacks rule diagnostic despite unmatched user execpolicy rulesOn GitHub#50979