Pakchunk error

[Yeedefix]

So I keep getting these errors 'The Pak File .../.../...Mordhau/Content/Paks/pakchunk[##]-WindowsClient.pak'. Does anyone know how to fix this?

[Light]

i have the same problem

[DrunkDwarf]

Find and delete the specific pakchunk file that it mentions, the number is important.

You can find the install directory by going into the properties of the game in steam, then clicking the "Local files" section, then the "Browse" button. That pakchunk folder will be in the Mordhau\Content\Paks folder. Find the pakchunk file of the same number it complains about, and delete it.

Once that specific file is deleted, you want to go back into the properties of the game on Steam, then go to "Local Files" again, then press the "Verify integrity of game files..." button. It will reacquire the specific file it's complaining about.

[Kony]

Originally posted by DrunkDwarf:

Find and delete the specific pakchunk file that it mentions, the number is important.

You can find the install directory by going into the properties of the game in steam, then clicking the "Local files" section, then the "Browse" button. That pakchunk folder will be in the Mordhau\Content\Paks folder. Find the pakchunk file of the same number it complains about, and delete it.

Once that specific file is deleted, you want to go back into the properties of the game on Steam, then go to "Local Files" again, then press the "Verify integrity of game files..." button. It will reacquire the specific file it's complaining about.

ive done this about a million times and it always keeps pak failing, usually 4 or 0 ive deleted and verified so many times, done every fix on the internet and its still broken.

[DrunkDwarf]

From what I've heard of this error, if files are repeatedly becoming corrupted, there may be an issue with your memory or disk drive.

[Catatonic Twitch Streamer]

This happens to me too. Redownloaded a lot of files, but even they were allegedly corrupt.

I was already doubting it to be my harddrive or ram for other games run fine and hadn't happend I had played this game months ago.

Turns out this only happens in Frontline mode, never in Invasion mode.

Just don't play Frontline.