Reprise: Cannot deploy mods via symlink

[Vectorial1024]

Describe the bug
Hi there, a long time ago (wow it was 1 year ago) I posted about Vortex unable to deploy mods through symlink (#6234). Back then, I somehow made it work but was unaware how it worked, and the issue was closed inconclusively.

This time, I changed my attention to installing mods for X Rebirth, and realized the same bug exists for that game. And, at the same time, I am fortunate enough to find out someone on Nexus Forums documenting a weird fix to this exact problem but for Morrowind, posted in Dec 2020. Link: https://forums.nexusmods.com/index.php?/topic/9402773-weird-fix-to-vortex-mod-deployment-side-topic-to-vortex-will-notcan-not-deploy-mods/

To Reproduce
I believe it could be reproduced/illustrated with these steps:

1. Install a fresh copy of Vortex; also need to somehow make sure we are using the default settings
2. Mod-manager-download some mods
3. Try to deploy mods
4. "Symlink creation failed" <- this is the apparent error reported in Cannot deploy mods via symlink #6234
5. "If symlink failed then try to change to hardlink" <- common suggestions for the apparent error
6. Go to Settings -> Mods
7. Realize unable to change from Symlink Deployment to anything else, there is only Symlink
8. Confusion <- Perhaps ppl are stuck here
9. Go to Settings -> Mods
10. Change the Mod Staging folder (I believe any location would do, but I changed it such that this folder and the game files folder are on the same drive)
11. I think also need to change Download Folder in Settings -> Download (...?) (also changed to be in the same drive with others)
12. Go back to Settings -> Mods
13. Now I can select Hardlink Deployment (Move Deployment (Experimental) also becomes available)
14. Change to Hardlink Deployment -> Apply changes
15. Go back to the mod list
16. Deploy mods again
17. It works! Mods are deployed, no problems.

Expected behavior
At step 7 above, I should be able to pick other options right at the get go (e.g. change to Hardlink immediately) so that there is no confusion at step 8 and no subsequent "weird fix". (Edit: I later discovered that Hardlink requires the staging folder to be on the same drive as the game folder; perhaps the documentation could mention this?)

Or, what exactly is going on under the hood that I am unable to see that caused Vortex to fail "default-settings" deployment in the first place.

Screenshots
N/A

Platform (please complete the following information):

• OS: Win10
• Vortex Version 1.4.12

Additional context
Link to original post: https://forums.nexusmods.com/index.php?/topic/9402773-weird-fix-to-vortex-mod-deployment-side-topic-to-vortex-will-notcan-not-deploy-mods/

And so it seems it does not only affect X4 Foundations. X Rebirth, but also affect Morrowind, or perhaps other games as well?

[IDCs]

Hi @Vectorial1024, thank you for your report. The #6234 report is tied to the old "symlinks without elevation" mechanism; (I'm going to assume this report is tied to that mechanism as well) the issue you encountered isn't game specific - it's an issue with your environment where for some reason your security settings/policies or AntiVirus is actively blocking Vortex from either creating the task responsible of running the symlink script OR removing the script as soon as Vortex creates it (or both).

Unfortunately environment settings/applications that are actively blocking Vortex from running its logic are not fixable on our end. I'm afraid you will either have to stop using the old workaround and elevate whenever required to do so, or try using the new experimental mechanism and let us know if that fixes things. Alternatively you can just keep using hardlinks as you appear to be doing currently.

I'm going to close this issue as we can't fix environment related issues. Please do let us know if the experimental workaround works though.