Try first: fully exit Steam, reopen it, confirm the account owns the full game, and start the game from the Steam Library—not from an old demo shortcut or the executable directly.
Run the checklist in order
- Exit Steam completely. Use Steam → Exit, then confirm the client is no longer running before reopening it.
- Confirm the full game license. In your Library, open the entry for Sir, We Have an Orc Problem. A demo that previously launched does not prove the full-game license initialized correctly.
- Launch from the Library. Avoid old desktop shortcuts, pinned demo entries or starting the executable outside Steam while diagnosing this message.
- Verify installed files. Open Properties → Installed Files → Verify integrity of game files, then retry after Steam finishes.
- Check for a Steam client update. Restarting applies a pending client update and refreshes the session used for ownership checks.
- Restart the computer. This clears a stuck Steam process or session that a normal window close did not end.
Rule out demo/full-game confusion
The game had separate playtest, demo and retail apps. If a shortcut was created before release, delete that shortcut and launch the retail Library entry again. Do not delete save folders while testing this; they do not need to be removed to refresh Steam initialization.
Avoid random DLL downloads and save deletion
Third-party DLL replacements and “cleaner” tools create more variables and can introduce security risk. Save deletion is also unrelated to a Steam ownership handshake. Back up your save and keep the troubleshooting reversible.
If the error remains
- Capture the exact message and whether the demo or full game is selected.
- Record your operating system and whether Steam is online.
- Check the current Steam Discussions for a developer-posted launch fix.
- Contact Mumpitz Games at the support address linked from its Steam data: contact@mumpitzgames.com.
What this page can and cannot claim
The error itself is confirmed by multiple public player reports. No current first-party post identifies one cause, so this page is a diagnostic decision path, not a promise that one step fixes every machine.