capella6707 Posted October 4, 2018 Share Posted October 4, 2018 I just updated Vortex (I don't know what version from/to, but I had it opened on 10/2 with the latest stable version, and today on 10/4 it said there's an update available). Now, when I try to start Vortex I get a message saying "Application state is invalid. I can try to repair it but you may lose data" with the options to Quit, Ignore and Repair. Needless to say the "Repair" warning scared me off that without knowing exactly what data I could lose. I've put a lot of work into a stable modded install of Skyrim SE and I don't want to do anything to compromise that. So, should I just download and reinstall it, or Repair it? Link to comment Share on other sites More sharing options...
rmm200 Posted October 4, 2018 Share Posted October 4, 2018 Check the change log for the new Vortex release. It looks to me like it is sort of expected.I used Repair, it did it's thing, and I lost nothing.If you try it and your computer catches fire - don't blame me. Link to comment Share on other sites More sharing options...
Zanderat Posted October 4, 2018 Share Posted October 4, 2018 I chose repair also. No issues. Link to comment Share on other sites More sharing options...
AgentTallin Posted October 5, 2018 Share Posted October 5, 2018 I chose repair also, no issues. :smile: Link to comment Share on other sites More sharing options...
Tannin42 Posted October 5, 2018 Share Posted October 5, 2018 Yeah, that was expected, it may actually happen in the future too. We have a bunch of sanity checks that clean up broken or simply "orphaned" parts of the application state. This is to prevent it from deteriorating over time and then cause us problems later.Each potential problem requires its own tests and so as we add new ones you might get this message. When you get this after updating Vortex it usually doesn't mean something broke since the last time you ran Vortex but that we added further checks. I will try my best to always make mention of that in the changelog.I will also add an option to create a backup of the state before running the repair so if something actually does get lost you can roll back. Link to comment Share on other sites More sharing options...
capella6707 Posted October 5, 2018 Author Share Posted October 5, 2018 Yeah, that was expected, it may actually happen in the future too. We have a bunch of sanity checks that clean up broken or simply "orphaned" parts of the application state. This is to prevent it from deteriorating over time and then cause us problems later.Each potential problem requires its own tests and so as we add new ones you might get this message. When you get this after updating Vortex it usually doesn't mean something broke since the last time you ran Vortex but that we added further checks. I will try my best to always make mention of that in the changelog.I will also add an option to create a backup of the state before running the repair so if something actually does get lost you can roll back. Thanks for the explanation, Tannin! An option to backup the state is a great idea, I think. Link to comment Share on other sites More sharing options...
JimmyRJump Posted January 5, 2020 Share Posted January 5, 2020 More than a year later and it just happened to me with version 1.1.5 and not after an update. First I chose 'ignore' and Vortex started but the 'Downloads' tab was completely red and it's features couldn't be shown. Closed and reopened Vortex and got the same error and chose 'repair' and Vortex worked normal without loss of data, at first glance. This shouldn't be happening several years into the 'development'. And a back-up of a borked app is useless since restoring the back-up will leave you with the same problem as before. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.