Not Quite Dead Black Screen Fix - Previous Playtest Save Cleanup
Quick answer
Previous playtest saves are the confirmed black-screen risk. Use the game's legacy save migration prompt first; only manually clear local save data if you understand that old progress may be removed.
This page is for players who see a black screen while launching or loading Not Quite Dead: Open World Survival, especially if they played an older playtest build.
Quick Answer
If you played the previous Not Quite Dead Playtest and now see a black screen, old local save data is the first confirmed thing to check. The developer's Steam news post says old playtest saves may no longer be compatible with the current version.
Use the in-game legacy save migration prompt if it appears. If you choose the old-version path and confirm, the August 25 update says the game closes safely, removes old local data after exit, confirms the removal on next launch, and starts fresh.
Manual save cleanup can help only when the problem is actually old local data. It can also remove old progress, so do not use it as a general fix for controller, WASD, graphics, or network symptoms.
When This Fix Applies
This guide applies best when:
- You participated in an earlier Not Quite Dead Playtest.
- The game launches to a black screen.
- Loading into the game shows a black screen.
- The problem started after moving from an older playtest build to the current launch/playtest build.
- The official migration prompt appears and asks about an older version.
This guide may not apply when:
- The game crashes before opening any window.
- Only the controller does not work.
- WASD or mouse focus is the only problem.
- Multiplayer joining fails but the game menu loads normally.
- You changed graphics settings and only visuals are affected.
Use The Official Migration Prompt First
The August 25 update describes a legacy save migration system that runs before normal player data is loaded. Players may be asked whether they played an older version of Not Quite Dead.
If you select No, existing data is left untouched and the game continues normally.
If you select Yes, the game shows another confirmation warning. After confirmation, the game closes safely, removes old local game data after the process exits, confirms the removal on the next launch, and then starts with fresh data.
That flow is safer than guessing at folders because it is the official path described by the developer.
Manual Cleanup Fallback
Only use manual cleanup if the official prompt does not resolve the problem or you cannot reach it. Before deleting anything, close the game completely and understand that local progress from older builds may be lost.
The likely Unreal Engine local data area players should inspect is:
%LOCALAPPDATA%\NotQuiteDead
Some systems may use a spaced folder name instead:
%LOCALAPPDATA%\Not Quite Dead
Clear caveat: the public Steam post confirms that old local save files may cause black screens, but it does not publish a full Windows folder map in the visible page text checked here. If both folders are absent, do not invent a path; use the official Discord or Steam Discussions and include your Steam install path, build date, and whether the migration prompt appeared.
Safe Cleanup Steps
- Close Not Quite Dead.
- In Steam, make sure the game is not still running.
- Press
Win + R. - Enter
%LOCALAPPDATA%. - Look for
NotQuiteDeadorNot Quite Dead. - If you find one, move it to a temporary backup location instead of permanently deleting it.
- Launch the game again.
- If the black screen is gone, the old local data was likely the cause.
- If the black screen remains, restore the backup if needed and report the issue with your build date.
Do not delete unrelated Unreal Engine, Steam, or Windows folders. Do not delete cloud data unless the developer gives a specific instruction for your case.
What To Include In A Bug Report
Include:
- Whether you played the previous Not Quite Dead Playtest.
- Whether the migration prompt appeared.
- Whether you selected yes or no.
- Whether the black screen happens before the main menu or while loading a save.
- Whether moving the local data folder changed anything.
- Your Windows version and GPU.
- The Steam build/update date visible in your client.
Related Problems
If your issue is not a black screen, start with the known issues hub. Low stamina can explain some melee/left-click cases, and controller or WASD symptoms should be tested separately before touching saves.
Source Notes
Checked on 2026-08-28. Sources used: the official Steam black-screen/save-reset post and the August 25 Steam/SteamDB release-candidate update describing the legacy save migration system. This page should be rechecked after any launch hotfix that mentions saves, loading, black screen, or migration.
Choose your next move
Related Guides
Once this question is solved, continue to the next decision without returning to search.
Known Issues Quick Fixes | Not Quite Dead
A 30-second troubleshooting hub for Not Quite Dead black screen, old playtest saves, zombie pressure, controller support, WASD movement, exit behavior, vehicle handling, and multiplayer joining.
Not Quite Dead Black Screen Fix - Delete Old Playtest Save
How to fix a Not Quite Dead black screen caused by old playtest save data, including the LocalAppData folder, Win+R steps, reset warning, and what to try if the save cleanup does not apply.
