vortexposer

Can confirm that that happened on mine too. Although I wasn't evading update but just wanted to review changelogs prior to, though nothing terrible happened as a result (beside the point). Had thought it was maybe bc I had Changelog Dashlet extension disabled bc I enjoy living dangerously minimal but wasn't going to reset to default to test that theory. I usually ignore and keep with stable but are there any betas for these versions anymore? Or is just being dropped right into main branch?

That'll teach ya to not let onedrive manage modded folders.

Save redirection is written by Ini Tweak to its prefs ini (including default profile), by adding profile ID onto its vanilla saves path. Fallout 4 used custom ini for some reason but for all the other BGS games, it swaps it out directly from the prefs ini.

Before adding a collection; check Manage Groups tool and keep it tidy/clear of anything that's not intentionally made by you and when removing a collection - manually delete junk groups left behind or reset to clear all.

Go to Vortex Plugins tab, Group Manager tool and right click anywhere onscreen. Then choose reset to clear defunct custom user groups.

So it didn't automatically open a browser page?

Your assumption is correct and that is how it is meant to work. Only a collection should ever override this toggle.

.base and .baked are only used by Vortex and are never meant to be edited manually by user or directly by any tool so what were you doing when that error was reported?

Tools that generate files can be redirected to their own custom output directory (user-made folder) in Vortex staging.

Go to Vortex Extensions tab, select show bundled at the top and confirm it's enabled.

Not sure what you mean but the incorrect setting was likely added by an inappropriately assigned collection tool.

Change its path on Dashboard tab/tools.

The ".1" appended to an archive name is what happens when it already exists in the same directory but you chose to add another copy, same as in windows downloads folder when it adds "(1)/(2)" after downloading same archive multiple times. Vortex should recognize this by giving a version drop-down variant with two sharing the same version. Manually delete its extra copy/re-adding base copy with no ".1" or once selected in Vortex, check its archive name field (for extra .1) and then delete version duplicate directly in Vortex UI drop-down menu.

Check if its enabled in Vortex Extensions tab (toggle hidden to view bundled extensions).

Admin issues deleting an archive like this requires Vortex to be closed first to end the process its hung up on.

Can you post picture of the error warning?

Its odd but technically required for hard links. Symbolic links not working is likely permission issues, as the nexus wiki says.

Modding The Witcher 3 with Vortex - Nexus Mods Wiki

Vortex 1.9.4 is the beta version. 1.8.5 is the up to date stable so you could probably ignore the mismatch as it just means your last install was using latest beta. Use the Vortex Uninstall.exe next time when uninstalling to clear that data and stick to stable to avoid other potential problems the beta may have (its for testing updates that users have to opt into if they're willing to deal with intermittent bugs). Should also not try managing a game using another manager with its own mods..

Filtering helps. One of the first steps I take when setting up Vortex is to go through extensions tab and disable everything not relevant to my personal-use. Not bc I care about the space they take up (nominal) but bc I don't want to "see" them. https://i.imgur.com/Us586QY.png

Wait. Hold up.. check your Extensions tab for SSE.

Uh, do you have open folder set to single click in windows explorer options? Tested with that setting and it does bypass highlight selection for the folder.

Select the game folder.

Go to Tools on Vortex Dashboard tab; select side dot to pop edit option, confirm in target path that it is pointing to your game folders skse64_loader.exe and not Mod's Staging folder. Typically, when skse throws this error it means it was launched outside of the game folder - so it can't find the game's executable.

Check that the SKSE Dashboard tool is targeting the deployed game folder copy.