I started the game before the DLC was released and everything was fine then. After the game was updated to 1.7 with the Fatesworn DLC my old save files were not found with me only having the option to start with New game

Same issue here... save files not found, then game crashed with some error about not being able to read some DLC file. Verifying files now then will try a reinstall... went ahead and backed up save files to be safe.

Where did my save game go GOG? All i can do is start a new game.

I seem to have found a solution that works, at least for me...

1 - back up save files
(there are two folders in C:\Users\(username)\AppData\LocalLow, one is called THQOnline and one is called THQNordic... in my case my old save files were accurate in the "THQOnline" subfolder but there were nothing but a couple new entries dated today in "THQNordic" but I'd already run the game and gotten this error, so others who haven't run the game with the DLC yet may be able to just back up their save files from the "THQNordic" location)

2 - open Galaxy and TURN OFF CLOUD SAVING for the game

3 - close Galaxy

4 - open the above mentioned "THQNordic" local save subfolder and delete everything, then copy / paste your saves you backed up previously

5 - Run the game (I personally did this without opening Galaxy again) and see if you now have the options "Continue" and "Load Game"


***I don't know if cloud saves can be turned back on at this point or not... I'll experiment and see, just wanted to share a potential solution until this is (hopefully) fixed in a patch

BRAVO!

Thank you, the notification of a reply reminded me I hadn't updated this post! :-D

*I loaded my old save and played just long enough to pick up a new quest and make a new save. I then closed the game, opened Galaxy and re-enabled cloud saves. Running the game then seemed to still work fine and recognized my new save (with Galaxy still open.)

I think personally I will just leave cloud saving disabled as this makes me trust it less, but I figured it was worth knowing that disabling it long enough to manually replace your save files and run your game / save seem to be sufficient, then cloud saving can be re-enabled and things seem fine... I'd just highly recommend keeping a backup of your saves if you have both cloud saves and automatic updates enabled, just in case there are any more hiccups like this.

Sorry, this is a load of BS. And I know you mean well but anytime I use a player fix it breaks something else. I think I just want my money back. I had a max-level character and he is gone over installing a xpack. That's just stupid.

I don't disagree in the slightest. At the very least, it may be worth checking to see if your save files perhaps survived in at least one of those folders, if you hadn't already backed them up... that way, even if you get a refund on the DLC, you'd at least get to keep your progress thus far while avoiding having to resort to a player fix or deal with less-than-functional expansions. :)

It might be worth the effort to verify game files. Ater receiving 2 updates to the game the 1st being 0MB and the 2nd at .1MB I verified the game files then it downloaded 125MB and the game started correctly and all saves were intact.

I had this issue the problem was the patch itself if you are going by the offline installed version. I was on v1.6 so I downloaded the patch for 1.6->1.7 then 1.7->1.7a and then the fatesworm DLC which is 1.7a.

1.6->1.7 patched fine but I couldn't patch 1.7->1.7a so I thought I could just install the DLC which is 1.7a but then there were no save games. I ended up just redownloading the 1.7a full offline installer then installed the DLC and everything is working again.

FYI 1.7->1.7a patch doesn't patch there seems to have been a minor patch between the 1.6-1.7 to 1.7-1.7a and if you are using the offline installer of 1.6, there is no way to patch up to 1.7a. You have to redownload the whole offline 1.7a installer to get it patched properly to play the DLC, though the 1.7a DLC will happily install on your 1.6->1.7 offline patched install.

OK, so all of a sudden it's working fine now. From what I hear from CM that post a lot on steam this was a GOG issue that they knew about and will resolve. So my max character is back.