New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot deploy mods via symlink #6234
Comments
The error message indicates that the task that was created by the Workaround can't be found, why I can't say based on the information provided. |
There is no new task created, even though I have switched off the workaround, restart Vortex, and enabled the workaround... Could it be something on my Win10 blocking the creation of such tasks? |
Must be, but I'm not aware of any setting in Windows that would prevent the creation of tasks. |
Still, what should the task do? I will need to tell Windows to do something like running an exe; I'll default to the Vortex exe for now. |
Tbh. If Vortex can't create the task it's unlikely it will be able to run it anyway, so I'm afraid you will just have to live with the workaround not being available to you. My recommendation would be to disable "Deploy Mods when enabled" and then install and enable your mods in bulks before you deploy manually, that way you don't have to confirm the UAC dialog as often. Or you could move your staging folder to be on the same drive/partition as the game and then use hardlink deployment which works without elevation. Or, if you consider yourself an advanced windows user: go to windows settings -> Update&Security -> For developers and there select "Developer mode". |
It is mysterious, but suddenly the issue went away. Previously, the only deployment method I got was "Symlink deployment (requires elevation)", and now I still get only one deployment method, but the name becomes "Symlink deployment". As a matter of documentation, I tried enabling Development Mode on Windows 10, and disabled it. I also set up a global task which would run Vortex.exe at highest permission possible every time I log in. Having done those things (and thinking that those things did not work, since I immediately tried to deploy mods after setting those two things, and could not deploy mods), I restarted Windows, and the issue went away. Not sure what might have made the issue went away. Edit: I also re-installed a fresh copy of Vortex by also cleaning the relevant AppData folders manually. I also cleaned up the previous deployment and staging folders manually before I set them again to the other drive away from the main drive. Essentially I had a "clean" environment to set things up again with Vortex. Not sure if the clean environment helped. |
It is strange. After closing Vortex and opening it back up in the same session of Win10, now it says "Deployment method no longer supported: Requires admin rights on windows." |
Not sure if important piece of info, but I am using both Steam and Vortex to obtain mods for X4 Foundations. I noticed that once Steam made their updates, the deployment from Vortex will fail. Not sure if the Steam-Vortex integration extension for Vortex will help. |
@Vectorial1024 Sorry for the very late reply, unfortunately your posts don't actually shed any light on the initial problem. The issue you were posting about initially affected the "requires elevation" variant however, which is used if the first one isn't available. |
Closing due to lack of feedback/assumed to be resolved. |
Describe the bug
Cannot deploy mods via symlink. I am trying to install mods for X4: Foundations.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Mods are deployed with no errors, and I can find the mod folders in the game /extensions folder.
Screenshots
There are some descriptions of the screenshots at imgur.
https://imgur.com/a/1FAoE76
The error log from above in text form:
Platform (please complete the following information):
Additional context
I also enabled the Workaround -> Symlinks -> "Allow Symlinks without elevation" settings, and according to the dialog, Vortex should have set up an elevated task in Windows for deploying mods.
The text was updated successfully, but these errors were encountered: