Beast of Reincarnation: CreateProcess() return 11c7 on Launch
One reporter traced it to Windows Smart App Control refusing a self-signed executable. That reading is unconfirmed, and this page will not tell you to switch off a security feature to launch a game — here is why, and what to do instead.
One player reported this and traced it themselves to Windows Smart App Control refusing to run a self-signed executable. Nobody has confirmed that reading and no developer has replied. If it is right, the fix belongs to the publisher — the executable needs signing — and not to you.
Where this is being asked · By players whose game does not start at all and who searched the exact error string, which is the only thing on screen. It is in the launch bug megathread once, with a diagnosis attached, which is more than most entries there have.
A grade describes sourcing, not truth. Inferred means we concluded it and the reasoning is shown; unverified means someone asserted it and nobody stands behind it.
UnverifiedThe game can fail to launch with CreateProcess() return 11c7.
One reporter in the launch bug megathread. No second report and no developer reply.
UnverifiedThe cause is Smart App Control refusing a self-signed executable.
The same reporter, reading their own machine. Coherent and uncorroborated — graded on who said it, because nobody has reproduced it and no developer has addressed it.
InferredDisabling Smart App Control is not the right fix even if the diagnosis is correct.
Ours, and it rests on two facts rather than on taste: the setting cannot be re-enabled without reinstalling Windows, and an unsigned executable is a defect in the shipped build that a certificate fixes once for everyone.
§01
What the error is, in plain terms
`CreateProcess()` is the Windows call that starts a program. A non-zero return means Windows declined to start it, and 11c7 in hexadecimal is the code that comes back when something on the system blocked the executable rather than when the file is missing or corrupt. That distinction is the useful part: the game is there, and Windows is refusing to run it. It tells you nothing on its own about *what* refused.
§02
What one reporter found, and how far that goes
The player who posted it traced the refusal to Smart App Control — a Windows feature that blocks executables it cannot establish trust for, including ones signed by their own developer rather than by a recognised authority. That is a coherent explanation and it is one person reading their own machine. No second player has confirmed it, no developer has replied, and this site has not reproduced it. If the diagnosis is right it would also explain why the problem is rare: Smart App Control is only active on some Windows installs, and it switches itself off permanently once turned off.
§03
Why this page will not tell you to disable Smart App Control
It is the obvious workaround and it is the wrong advice, for two reasons that both outlast this bug. Smart App Control cannot be re-enabled without reinstalling Windows — it is a one-way switch by design — so "just turn it off" is not a temporary step, it is a permanent reduction in what your machine will refuse to run, taken for one game. And if the cause really is an unsigned executable, then the defect is in the shipped build and the fix is a signing certificate the publisher applies once for everybody. Guides that tell you to lower a security setting are moving the publisher's problem onto your computer.
§04
What is worth doing instead
Verify the game files through Steam first, because a blocked launch and a broken install look identical from the outside and only one of them is this problem. Then open Windows Security and look at the Smart App Control log: if it lists the game's executable, you have confirmed on your own machine what one forum post asserts, and that is worth posting to the thread, because a second confirmed report is what turns this from one person's reading into something the publisher has to answer. If it is not listed, this page is not your problem and the general launch-failure symptoms are the place to go.
Expiry condition
What would have to change for this answer to be wrong
An answer about a live-service game without this is an answer with a hidden expiry date.
A second player confirms the Smart App Control trace, the publisher signs the executable, or a developer replies naming a different cause. The first of those is the one a reader can supply, which is why the section above says how.
Citations
Every source, with its date
A complaint posted before 30 July 2026 describes the playtest, not the game you bought, and a source whose publication date nobody captured cannot show that it postdates launch either. Both are flagged rather than quietly mixed in.
That one player reported a launch failure returning CreateProcess() return 11c7 and attributed it to Windows Smart App Control blocking a self-signed executable. Read 2026-08-05; the post carried a relative timestamp, so the date is approximate. It establishes the report and the reporter's own diagnosis — not that the diagnosis is correct, and not how common the failure is.
Related questions
Windows declined to start the program. The game is installed and something on the system blocked it from running — the code does not say what.
