Works in Unreal Engine 5.0 to 5.8. Updated November 2026.
Quick answer: “Unknown Cook Failure” is a summary, not the real error. Find the first real error and fix that.
- Open Window > Output Log and search for
Error:. The first error above the failure is the cause. - Right-click your Content folder and choose Fix Up Redirectors.
- Open the asset named in the error, fix or delete it, then save.
- Package again.
Where the real error is
The packaging message only says the cook step failed. The reason is always further up the log.
- Output Log: in the editor, open Window > Output Log and type
Errorinto the search box. Scroll to the first match, not the last. - Full log file: if the Output Log was cleared, open the log the packaging tool writes in your user folder:
C:\Users\<you>\AppData\Roaming\Unreal Engine\AutomationTool\Logs\. The subfolder name matches your engine install path. OpenLog.txt(and anyCook-*.txtnext to it).
Look for lines with Error:, Failed to load or Assertion failed. They usually name an asset path.
Common causes and fixes
| What the log says | Fix |
|---|---|
Failed to load or a missing asset path | An asset points to something you deleted or moved. Open it and replace or clear the missing reference. |
| Errors after moving or renaming folders | Right-click Content > Fix Up Redirectors, then save all. |
| A Blueprint failed to compile | Open that Blueprint, click Compile, fix the errors and save. |
Path too long or a file can’t be created | Move the project closer to the drive root, for example D:\Projects\MyGame. |
| A plugin or module error | Disable plugins you don’t use in Edit > Plugins, or update the plugin for your engine version. |
| Out of memory during the cook | Close other programs and package again. Large projects need a lot of RAM. |
Step 1: Fix redirectors
When you move or rename assets, Unreal leaves small redirector files behind so old references still work. Broken redirectors are one of the most common cook errors.
- In the Content Browser, right-click the Content folder.
- Choose Fix Up Redirectors.
- Click File > Save All.
Step 2: Find broken Blueprints
Open each Blueprint the log names and press Compile. A Blueprint with a red error icon can play in the editor but still fail the cook.
To check many at once, open Tools > Find in Blueprints and search for a deleted variable or function name you suspect.
Step 3: Clear cached files
If the log points nowhere useful, close the editor and delete these folders in your project (not in the engine):
IntermediateSaved\CookedDerivedDataCache
Reopen the project and package again. Unreal rebuilds them, so the first launch is slower.
Don’t delete the Content or Config folders. They hold your game.
Test the cook without packaging
Use Platforms > Windows > Cook Content to run only the cook step. It’s quicker to repeat while you fix errors one by one.
FAQ
The log has dozens of warnings. Do I fix them all? No. Warnings rarely stop a cook. Fix the lines marked Error.
It packaged fine yesterday. What changed? Usually a moved or deleted asset, a new plugin or an engine update. Start with Fix Up Redirectors.
Does migrating to a new project help? Sometimes, because migrating leaves broken assets behind. Try the steps above first; they’re faster.