I hit launch and the screen went black. A tiny dialog blinked up: CreateProcess() returned 11c7. My session died before the intro cutscene finished.
I’ve chased this bug through an early-access build and through forums; you aren’t the only one staring at that code. I’ll walk you through what I tested, why it seems tied to Windows’ app defenses, and a quick repair that let me get back to playing.
My first run crashed with the 11c7 popup — what’s actually happening
The error appears when Windows blocks a component Steam or DREADMOOR tries to spawn, and the game exits with the message CreateProcess() returned 11c7. That makes the fault feel mechanical and sudden, like a flat tire on a highway. The developer team has acknowledged the issue and is working on a patch, but there’s a workable temporary workaround you can apply in minutes.
On my machine Smart App Control was the common denominator — the step-by-step fix
I ran a few experiments across machines and the ones where Smart App Control was set to On or Evaluation were the same ones that crashed. If that matches your setup, try this:
- Open the Start Menu.
- Type Smart App Control and run it as administrator.
- If Smart App Control shows On or Evaluation, switch it off.
- Change your save in-game and return to the desktop/home screen.
- Launch DREADMOOR from Steam and check whether the crash still happens.
On my rig this stopped the crash every time. Think of Smart App Control as a strict bouncer that sometimes rejects harmless guests.
What does Error 11c7 mean?
It’s a Windows-level rejection code thrown when CreateProcess fails to start a process the game requests. In practice, that’s usually an OS security policy blocking an executable or helper tool that Steam or the game tries to launch. Microsoft’s Smart App Control and similar protections are the usual suspects.
How do I fix Error 11c7 in DREADMOOR?
The clearest, repeatable fix I’ve used is the Smart App Control toggle described above. If you don’t have Smart App Control enabled, also try these standard steps:
- Verify the game files in Steam (Steam client → Library → right-click DREADMOOR → Properties → Local Files → Verify integrity of game files).
- Run Steam and the game as administrator once to seed any needed permissions.
- Update Windows via Settings → Update & Security so system files and Defender definitions are current.
- If you run any third-party antivirus (Norton, Bitdefender, Malwarebytes), temporarily disable it and test the game.
If you use Windows Insider builds, try a stable release if possible — some early-channel updates change security behavior rapidly.
One test that separates system faults from game faults — quick observation then action
When the crash happens immediately on start, it’s usually a permissions or security block; if it crashes after a certain script or scene, it could be a corrupted asset. Use this to triage fast:
- Crash at launch: suspect Smart App Control or AV. Toggle off and test.
- Crash mid-session: verify files in Steam and try a clean save or a different graphic settings profile.
Is a permanent fix coming?
The developers have acknowledged the bug on the project’s early-access roadmap, and I expect a proper patch from the team or a compatibility tweak from Microsoft within a few updates. Until that arrives, the Smart App Control toggle is low-friction and reversible.
If the error resurfaces after you try these steps, repeat the toggle and run the verification steps above; if that still fails, capture the exact crash text and open a support thread on the game’s Steam Community Hub and tag the devs so they can correlate logs. I walked this path myself and the temporary fix held on my test machines — will yours behave the same way or reveal a deeper Windows oddity?