Cloud Save Conflict

Disable Cloud saves for DAI....see if it starts.  If it does, make a backup of your saves folder in another location and wait a few days...backing up as you go.  Then if you really need Cloud saves for playing on different systems or some such, then re-enable it after a few day to see if it is a cloud server issue.  Personally, I have all cloud saves turned off, as I only play on one computer and I occasionally make a copy of my saves folder just in case.  MY personal experience has been the cloud save function causing more issues than it saves.

Sorry for the late-ish reply- I tried this but it still won't launch so I think it's safe to assume it wasn't the cloud save causing the problem. It still just won't open at all. I tried to delete Origin and redownload it, but it didn't change anything. All of my other games work fine, but not Inquisition. I also tried to repair the game to see if that would change anything, but nope. Thank you for the suggestion though, much appreciated.

Hi @Youkai-Amy

We had some general issues with cloud saves on Origin recently, but they were fixed in the latest client patch. Could you make sure that you're using the latest version of Origin (10.5.24.5022 - 0) and check out if the cloud save conflict still occurs in DA Inquisition? 🤔

Thanks!

/Ataashi

So if cloud saves are off, and it doesn't ask you to choose...then it is a problem with the game not starting.

This can be many different issues.  So if this is still the case after the latest Origin update, then please post a DxDiag file up here, and also do some basic checking. 

1)  Disable all Anti-virus programs(usually can be done temporarily) and see if it fixes issue.

2)  Disable Firewall programs.

3)  Make sure you don't have Razor(mouse/keyboard) programs installed....some people report it is just the online reporting section of the program causing issues.

4)  Try a clean boot of the computer and only run minimum programs, plus Origin and DAI and see if it works.

5)  Make sure you don't have teamspeak running...I think teamspeak 13 started this issue for it.

keep us up to date....