Version 1.2.9 failure to launch
Posted 26 April 2020 - 11:24 PM
Posted 27 April 2020 - 02:31 PM
Please check if there is a dialog open, it might have opened behind another window.
If you're certain there is nothing, please find the directory "C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins", select the directories "changelog-dashlet" and "common-interpreters" and move them somewhere else (or delete them), then try starting Vortex again.
Let us know if that changes anything, if it still doesn't start, please send in the vortex.log again (please send the entire log file, not the "diagnostic files")
Posted 27 April 2020 - 10:21 PM
Posted 28 April 2020 - 08:05 AM
Sorry, forgot to mention about the corruption message, but yeah, ignore it.
Unfortunately this doesn't give us any new information. Vortex gets stopped while loading the extensions, in your first log it showed it successfully loaded "changelog-dashlet" and "common-interpreters" should have been the next to be loaded.
There is nothing else going on inside Vortex at the time, there is no reason it would stop at that point. Something external interrupting Vortex or Vortex trying to show a system dialog and not getting a response are the only two things that make sense.
You could look into the windows "Event Viewer" and see if windows logs anything when Vortex fails to start (should be under Windows Logs -> Applications if anything).
The other thing you could try is to move away all the directories bundledPlugins, see if it starts again, if gradually move them back until you can identify which one caused the problem. Also check in "C:\Users\<username>\AppData\Roaming\Vortex\plugins" if you have any extensions you have installed on top of what's bundled and (re)move them as well.
If none of that helps and you made sure there is no dialog opened by Vortex I'm honestly at my wits end. The log shows pretty exactly where it stops and there is no reason for it to stop there.
Posted 28 April 2020 - 09:54 PM
I've done enough checking for these types of errors to know that it can be very difficult to find the source. The only error code in the event viewer is 1000. This faults the vortex executable, but that isn't much help to troubleshoot because it doesn't go deep enough to give an idea of where in the code. The dll referenced in this type of error is not always the fault either. That's just what it was referencing when it crashed. The nt.dll is updated fairly often with monthly updates though, so I'll see what the next windows update does. If that doesn't do it I'll likely do a clean install of Vortex and reload mods again at some point.
I appreciate you looking!