Save Failed.

Bug Report
Hello,

Trying to play through nova's campaign and whenever I try to save the game and/or the game attempts to automatically save after a checkpoint, I get a "Save Failed." message.

I was searching through the internet and apparently there used to be a sticky thread about this but it is now gone(404). Information on the issue is scarce and nothing conclusive. I am logged in as Admin and the Documents/Starcraft 2 directory has the correct permissions... Help?
Hello Spawn,

Sorry for the late reply on this.

Try this workaround:
1. At the Campaign select screen click on more to the load save game menu.
2. Open the "Show in Folder" button.
3. Delete the entire "Saves" folder, in the account folder area the "Show in Folder" button brought up.
4. Start a campaign game.
5. See if auto saves and manual saves work again.

Hope that works to resolve this issue!
Thanks,
-Kelphe
Same problem, above solution does not work.

I just downloaded LoV and in the second mission the problem showed first (unable to save games, and unable to load save games). Not sure it matters, but in the load menu, autosaves show up but have a little red exclamation mark next to them.

As per the the above, I deleted the folder but now simply have to replay the first missions. Is there a solution? or a cheat so i don't have to play them again?
Same problem. This happens since the game got one of the useless updates a few weeks ago.
Had this problem while trying to finish the Into the Void missions. Luckily I was able to power through them so I didn't have to save, but otherwise this would've been a huge problem. Someone should definitely look into this.
I get the same problem when playing prologue of Legacy Of The Void on Brutal on Windows 10. Saving worked normally until the end of the 2nd mission. Now the save file is created, but the error message says about failed save and saves cannot be loaded. This mode is kinda Mega Brutal :)
Is this still going on? Can't progress my campaign well at all this way.

Deleted the save folder, and while battlenet remembers where I was, I can't save any more progress.
Not sure about 4.0, but 3.19 certainly still had this problem. It seem to happen with all campaigns without the story "ship" mode between the missions (e.g. the first 3 missions of Legacy, before getting to Spear of Adun). Usually restarting the game and starting the mission from beginning resolves the problem (you can save through the existing mission), but as soon as you advance to next one, the problem resurfaces.

EDIT:

Maybe it's related to this known issue?

Saving the campaign during the ""For Aiur!"" mission then loading that save causes the player to be unable to save during the next mission.


Only that it seem to apply to all missions that doesn't have the "Story mode" in between.
It appears as if sc2 stops getting write access to save folder. Read deanx reply

https://eu.battle.net/forums/en/sc2/topic/15161831158?page=1
I have given write access and it doesn't work.

I have tried all that crap.

Every other update makes it impossible to play. Why did I pay for this crap?
I keep having this error. Any news on this?

I even added sharing with read/write for everyone and seems to have worked for a while. Then it stopped working.
I've been having the same problem for the last few days.

When saving, above the header that says "Date", click on the "new folder" button, and make your saves in a new folder.

I'm still not able to access my old saves, but at least I can make new ones that I'm able to load from.
I'm not sure if the following will help. I noticed this particular bug during SC2 campaign play. Then when playing SC: Mass Recall it popped up again. I know a mod may change the behaviour of the game and the following may not be useful, but just on the off-chance...

Mass Recall puts its saves in the Saves\Multiplayer directory. I had a poke around and loaded a few into a hex editor (XVI32).

Both working and broken saves start with the 12 hex bytes: 4D 50 51 1B 00 02 00 00 00 04 00 00 ('MPQ' ASCII followed by various other stuff). After that, the broken saves just contain nulls until offset 0x400, where the 'MPQ' string appears again plus other stuff.
But the working saves contain the byte 0x71 at offset 0x0C, followed by other stuff, up to the last two-byte entry starting at 0x7E which is 10 06. Thereafter nulls, until 0x400.
If viewing in Notepad the most obvious thing will be the string '(StarCraft II save' starting at offset 0x14 in the working saves.

Not sure if anyone can corroborate this with standard SC2 campaign saves? Basically just look for the 'StarCraft II save' string near the start of the file in Notepad. If I'm right, broken saves will always lack it and working ones always have it (plus other stuff not legible in a text editor).
Hey Blizzard just to let you know that for whatever reason your latest update for STARCRAFT 2 has one hell of a bug in it that is causing auto-saves to fail. Even manual saves fail. I went to save a mission on Char and it said SAVE FAILED. Literally tried to save it again and it then said SAVE SUCCESSFUL. Seems you might want to get onto this as it is one hell of a bad bug to have.
Just purchased LotV and dealing with same issue...any updates?
Hey DieZieg,

Nothing yet. So far, we only know that the developers are working on a fix.

It does seem to precipitate from certain conditions, so if you avoid them, it shouldn't happen.
03/22/2011 11:04 AMPosted by Huginncord
If you load a saved game, then beat it and replay the mission, you are no longer able to save.
05/11/2018 06:09 AMPosted by Leviathan
Hey DieZieg,

Nothing yet. So far, we only know that the developers are working on a fix.

It does seem to precipitate from certain conditions, so if you avoid them, it shouldn't happen.
03/22/2011 11:04 AMPosted by Huginncord
If you load a saved game, then beat it and replay the mission, you are no longer able to save.


It is now 2018 and this bug is still not fixed lol.. "working on it my !@#"

And so as long as you avoid playing the campaign you have no issues at all lol.... thats the fix? to not play it..

Seriously this bug is really freaking pissing me off.

Join the Conversation

Return to Forum