A list of Wolvenkit error codes, and what they mean
Published: May 1 2024 by Last documented update: May 1 2024 by
This page contains an overview about Wolvenkit's internal error codes and what they mean.
For developers:
When editing this page (especially section headers), please update the internal mapping:
WolvenKit/Helpers/LogCodeHelper.cs
If you ended up on this page, you ran into a problem that needs to be fixed inside WolvenKit. You now have the following options:
If you are on the stable release, you should try The Wolvenkit Nightly. There's a good chance that your problem is already solved.
Make sure that you are on the most recent version of whatever tool's you're using. This includes, but is not limited to, the and .
Find our discord server and hit up the #wolvenkit-support
channel. (Don't bother if you aren't on the Nightly yet, it's the first thing anyone there will tell you.)
If your error still happens in the Nightly, you need to tell us about it. It's easy: bugs that don't get reported don't get fixed.
Head to Wolvenkit's github page and create a ticket (you need a github or Google account, but they won't send you spam).
To fix the bug, we need to watch it in action. Please include everything we need to make it happen!
WolvenKit ran into a problem during internal conversion. Here's what you can do:
Install The Wolvenkit Nightly
Re-create whatever file you were trying to work on at that time:
A game file from an earlier patch: Add it to your project again
A depot file: Delete the file from the depot and/or re-create the depot
If that doesn't work, please get in touch via Discord or browse the troubleshooting section.
You have an unspecified issue with your settings. Double-check them and make sure that everything is configured correctly.
If that doesn't help, remove or re-name your settings file and restart WolvenKit:
Check your Settings ->#game-executable-.exe-path and make sure that it points at your Cyberpunk2077.exe
. For more information, check the wiki link.
Check #id-0x5001-invalid-game-file-executable and make sure that all your settings are valid. If that doesn't fix your problem, you may have to reset your settings, see #id-0x5000-invalid-settings for detes.
A raw file: re-create the file with the latest version of whatever tool you used (Wolvenkit, the ...)