showler

No. The system Vortex uses to install mods is Windows Native so Windows sees things whether Vortex is running or not.

Not at the moment. It's been suggested.
 
Go here to upvote the suggestions: https://feedback.nexusmods.com/?query=bsa

The only way to do that is to have the files that are different in each version set up as a mod that can be deployed/purged by Vortex when you switch profiles.
 
Vortex is not designed to use multiple versions of a game so you need to trick it.

They are the instructions for Vortex on how to install mods for BG3. If you don't have BG3 or aren't modding it, then they won't do anything. Just ignore them.

Did you look at the comments in the announcement article? There are currently bugs causing the blur to stay on in the quick search and download history. Are you seeing it elsewhere as well?

Sorry, I misread.
 
If you're missing the Starfield extension you can get it here: https://www.nexusmods.com/site/mods/634

There's a feedback site here: https://feedback.nexusmods.com/
 
It's the best place to post such suggestions as they can be better tracked and upvoted to show priorities.

Just copy the files from the old directory into the folder where your new saves are being stored.

Already did.
 
Read the post: https://forums.nexusmods.com/index.php?/topic/13270524-starfield-extension-041-hotfix/

Use the "purge mods" option in Vortex.
 
Shut down Vortex.
 
Have the storefront (Steam, GoG, Game Pass) do the moving of the game.,
 
Restart Vortex, go to the games tab, choose the edit option on Skyrim, update the path information. Restart Vortex to be safe.
 
Go into settings and change your deployment folder to the new drive. Vortex will move the files.
 
Deploy mods again.
 
Vortex may automatically suggest some of the steps.

Vortex is designed to manage multiple games in multiple drives.
 
It might be a bit confusing that it only shows you one place to input the staging folder path, but a fair bit of the settings is context sensitive to the game you are managing and will only show information for that one game.

The list of Vortex supported games is here: https://www.nexusmods.com/about/vortex/
 
Aliens: Fireteam Elite does not appear to be on that list. You would have to create a Vortex game extension in order to make it work with Vortex.

There's a column available in the plugins tab to show which mod a plugin is associated with. Use that to check that the plugin is connected to the mod you disabled/removed. If it's blank, then Vortex didn't install that plugin at all and won't remove it.

Picky mentioned that if the games list is missing games then something might be preventing Vortex from communicating with GitHub.
 
Some of the other issues sound like not being logged into Nexus Mods in Vortex.

Read the common solutions thread.

You don't. You choose them individually.

On the "mods" tab, double-click a mod. That will open a side-panel. The option should be there.

You remove mods under the "mods" tab, not the "plugins" tab.

Look on the left, find the extensions tab, click it, look at top, find the "show bundled" button, click it to show all the extensions.
 
Then check if the Gamebryo or Skyrim extensions are showing that they are installed, enabled and functioning correctly.

It should be listed in the apps section of the windows settings with an option to remove it.

Well, your problem there is that Skse64_steam_loader.dll isn't an executable.
 
The shortcut should be pointing to Skse64_loader.exe.

Click on Extensions, click on the "show bundled" button, check the status of the "Collections" extension.

I think you need to create the folder first. Or it may have the generic Windows "make new folder" option while selecting the folder.
 
It just has to be empty or Vortex won't accept it.

Double click the ESP in the plugins tab, scroll down in window that opens till you find the groups dropdown. Change it to something like "Late Loaders" or "late fixes" or whatever. It will drop down (unless there is another rule that requires it to be higher). To reverse, simply remember whatever the default group was and change it back to that.

I believe Picky said that it is not currently possible to do that.
 
Not without creating separate Windows accounts to make separate Vortex configs (or some trickery with start-up options Tannin mentioned) at least.