2 people reported
All time, since Oct 11.
Server start blocked by policy
“No actionable rule ID, policy layer, justification, or approval prompt was shown.”
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/11529/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
Local Next.js server start rejected as blocked by policy on Windows. Commands the user authorized fail before process creation with no rule ID, policy layer, justification or approval prompt, even with Full access shown.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
CreateProcess: rejected: blocked by policy- Versions
- 26.1016.8622.0
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Related: Windows opaque blocked-by-policy rejections
Not quite your bug?
- Unexplained blocked by policy58 people
- Blocked by policy, no rule shown3 people
- Opaque blocked by policy rejection3 people