Cannot speak for the lost saves on the PC version, but my hatred for how messed up this situation was prompted me to figure out how to fix it on 360.
01. Back up whatever saves you have that do work in case of (another) disaster.
02. Delete title update #5. Ignore the prompt to install it again when starting the game and let XBL go offline.
03. See if your most recent "broken" autosave on your main storage device (likely your default HDD) will load. You will get the "DLC not present blah blah" error message but click ok.
04. Play around in the game so your autosave is overwritten three to five times.
05. Exit out of the game to the dashboard, launch again, accept the title update.
06. Load/continue your autosave, overwrite it a few more times, and then create a hard save.
This worked for me. I think it took less effort to get a command line version of UNIX running on Dreamcast back in the day, but I guess this is modern entertainment.
As for the PC version, I'm guessing if you are straight through steam you might be fucked. Maybe if you can re-install a retail copy and pull out an ethernet cable so steam doesn't autopatch it you might be able to try what I did. To me, it seems like patch/TU #5 needs to be patched. This did not happen with TU4 at all when I started playing the game on Tuesday.
Alpha-Bromega said:
anecdotal. that's too bad and i'm truly very sorry that was your experience with the game.
I don't think there is anything anecdotal about problems with Obsidian games. KOTOR2 on the PC was a nightmare when I played it not too long after it came out. I'm going to see this through because it is fallout, but yeah, Alpha Protocol can stay in shrink wrap. Hire some QA testers, fuckers!