Known Issues

[Tannin42]

Problem: "Database is not open" exception on switching game in 0.14.0

 

Solution: It's safe to click ignore here but you may have to do this several times. Easier solution is probably to quit and restart Vortex

 

This happens due to a timing problem when vortex tries to update an internal cache

[Tannin42]

Problem: "Failed to create backups of the ini files for this game." and the path in the error message is a onedrive path.

Solution: Disable "Files On Demand" in the OneDrive settings.

Explanation: Microsoft introduced this feature in the last major update and they seem to use some dark voodoo that actually breaks a few tools.

Node.js, a framework Vortex is built upon can not currently deal with this, causing this error message (and a few others).

[Tannin42]

Problem: "Deployment failed" notification, log file contains lot's of messages "failed to link error=EISDIR: illegal operation on a directory, link"

 

Solution: The problem is probably caused by the filesystem on which the game&mods are installed being exFAT. Unfortunately Vortex currently works on NTFS filesystems, so the only solution right now is to move the game to a NTFS partition.

[Tannin42]

Problem: Vortex 0.15.0 reports cyclic even without any custom rules. This usually involves a compatibility patch of some kind where one of the plugins that are made

compatible is in a non-default group.

 

Workaround: Add the compatibility patch to the same group as the plugin (the one that isn't default)

 

This is a known problem and will be fixed properly in the future, the above is just a workaround.

[Tannin42]

Problem: ENOENT: no such file or directory, open 'C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Local State'

 

Workaround: It's safe to click ignore on this error message. An alternative is to create a file with the name mentioned in the error message (Local State should be a file without extension, not a directory!) with the content

{}

[Tannin42]

Problem: On Startup you get an exception saying "Command failed: powershell.exe -NoProfile -NonInteractive ..."

 

Explanation: This happens when a new version of vortex is available and the automatic update fails to validate the new installer. The updater framework uses an external powershell script to test the signature of the archive. For some reason this script fails, could be because powershell is disabled on your system.

 

Workaround: It's safe to ignore this error but you need to manually update vortex. If this continues to happen,

 

Solution: Vortex 0.15.x should produce nicer error messages but the automatic update will still fail if this happens. It might be all you have to do is enable powershell in "Programs & Features" in windows.

[Tannin42]

Problem: When reporting an error you receive another error message: "HTTP (401) - Unauthorized"

 

Explanation: This happens if you're either not logged in inside Vortex or the error happened at the time before Vortex has confirmed your identity. Due to a bug, errors can't be reported without login atm.

 

Workaround: Please click ignore on this error message, don't report it any more