If Steam shows Zombies Aren't Real launch error 0x11C7 and says an application control policy has blocked the file, Windows stopped the game before it could open. Developer JoGameDev attributed that exact message to a Windows code signing issue in a pinned Steam post and said signing was still in progress at the time. Check for a follow-up from the developer, then try any available Windows updates: one player reported that updating Windows cleared the error, but it may not work on every PC. If you're trying to play with a friend, make sure both copies reach the main menu before troubleshooting the co-op session itself.

Confirm that Steam shows the policy block
Select Play in your Steam Library and read the full dialog before closing it. The developer's post describes the message “Failed to start process for this game, an application control policy has blocked this file” with the code 0x11C7. If both the wording and the code match, save a screenshot or copy the message so you can compare it with the result of your next launch attempt. If the game opens and displays a different error later, record that wording and the last action you took before it appeared.
Steam lists 64-bit Windows 10 and Windows 11 in the game's system requirements, so include your Windows version when you record the error. Note whether this is your first launch or whether the game used to open on the same PC. If you're testing with a friend, record which computer shows the dialog and whether the other copy reaches the menu. That distinction matters even if the problem first came up while you were arranging a co-op game: the PC showing 0x11C7 needs to get past launch before you can test joining.
Check for a signed build and try Windows Update
In the game's Steam General Discussions, find the pinned topic with 0x11C7 in the title and look for a follow-up from JoGameDev. The original post said the developer was working on code signing and had been told it could take a few days. That estimate was for work in progress, and the post does not confirm when or whether a signed build became available. If the developer announces one and Steam offers an update, let Steam finish installing it before you retry, then note whether you reach the menu or see another dialog.
Open Windows Update in Settings and check whether an update is available or a restart is needed to finish one. After applying an update and restarting if prompted, launch the game from Steam again in the same way you did before. The pinned post mentions one player who could launch after updating Windows, but it gives no specific Windows update to look for and no assurance that the same step will clear your error. If you still get 0x11C7, keep the exact message and note that you already tried Windows Update.
The pinned post also relays player reports that turning off Smart App Control bypassed the block. Turning it off changes a protection for the whole PC, so start with the game and Windows update checks, which leave that protection in place. If this is a work or school computer and the same policy message persists, pass the exact wording and code to the person who manages the device. On a personal PC, send the details to JoGameDev and ask whether a signed Steam build is available for you to try.
Find where online co-op stops working
Steam lists online co-op with one friend, so have both players launch their copies independently before anyone tries to join. If one person sees the policy block, that player can follow the launch checks while the other confirms how far their own copy gets. Once both players reach the main menu, retry with the same person hosting and the same friend joining. Keeping the setup the same makes it easier to tell whether getting both copies to launch was enough or whether there is a second problem once you try to play together.
Watch for the first step that fails: trying to join, getting into the session, or loading a mission after both players appear to be connected. Ask your friend what was on their screen at the same moment, since one player may see an error while the other is still waiting. Copy any message exactly, even if it differs from the Steam launch dialog. If neither player sees an error, describe what does happen and the last action each player completed, such as selecting a mission before being sent back to the menu.
If both copies reach the menu but a mission fails to load in co-op, have the affected player try opening a single-player mission and record the result. If it loads, see whether the co-op failure happens again at the same point with your friend. If the trouble seems limited to one mission or Workshop map, note its name and whether you can reproduce the problem with another map. These comparisons give JoGameDev a smaller set of steps to try, even when neither player gets an error code.
Send JoGameDev a useful bug report
For a launch report, begin with the exact Steam message, your Windows version, and whether the game has ever reached the main menu on that PC. Say when 0x11C7 first appeared and what happened after each update you tried, including whether the wording changed on the next launch. The pinned Steam topic is the place to check for news about signing, and JoGameDev also invited players with issues to get in touch through the official Discord linked in that post. If you attach a screenshot, crop it to the error so the message is easy to read.
For co-op, start by saying whether both players reached the menu, then explain who hosted, who tried to join, and what each player saw when the attempt failed. If Windows Update cleared the launch block but joining still failed, give the two events in order and include both messages if you captured them. Mention whether a single-player mission loaded and whether the co-op problem followed a particular map. If the developer asks you to retry after a game update, repeat the same steps where possible and report how far you got this time.