Call of Duty: Warzone Pacific is facing an extremely annoying DEV ERROR 6039 on their PS4s and other consoles. While the problem may seem ominous at first, it has a few easy but albeit time-consuming and tedious fixes. As of yet, the developers have not provided us with an actual fix to the problem. So, all these fixes are provided by community members.
The error seems to be most prevalent to those who are using HDDs or ones who have had issues in updating their game due to low disk space or an unstable internet connection. You can find the fixes to DEV ERROR 6039 down below.
What is DEV ERROR 6039 in Warzone: Pacific?
The issue seems to be a recurring theme on the PS4, PS5, Xbox Series X | S, and the PC. However, it seems to be the most prevalent on the PS4. As of yet, it seems like this error occurs due to hard disk/storage errors.
According to the developers, this error seems to have popped up in Warzone: Pacific. However, the issue has persisted throughout all versions of Warzone and commonly occurs when a new major update pops up.
With that said, here are the most common fixes for Warzone DEV ERROR 6039 (common_mp.fc):
- Clear up Hard Disk space from unused games
- Power cycle your PS4:
- Completely turn off your console by holding the power button down
- Once the light stops flashing, plug the power cable ouut and leave your console there for 20-30 minutes
- After doing so, attemmpt to launch the console in Safe Mode
Related: Best Plane Controls and Tips in Caldera | Warzone Pacific
Reinstalling Call of Duty: Warzone Pacific
If the above two fixes don’t work for you, you’ll have to resort to the most time-consuming but effective one which is to delete your game and to re-install it. Here’s how you can do so:
- Head to your console’s library
- Select Modern Warfare 2019 / Warzone: Pacific and delete it
- Now, download the game again and you should be good to go
Note: If you are on PC, we recommend verifying the integrity of your game files before you go ahead and reinstall. Chances are that the error might correct itself by following this route.
Did the fix we mention work out for you? Let us know in the comments section down below!
