Closed BinToss closed 10 months ago
Hi there!
First of all, thank you for your report.
You may have been notified that Vortex is being phased out in favor of the Nexus.App mod manager - Your report is such a niche case which would barely affect 1% of our users, and even then I'd expect them to know how to resolve the use case you described given that they knowingly broke their environment in the first place!
Your bug report will be forwarded to the Nexus.App developers for the sake of visibility, but as far as Vortex is concerned this will not be looked at.
Sounds like the Junction is possibly to another drive? Consider using a Volume MountPoint instead.
Ideally, you would have wanted to set this up from the start, otherwise you gotta make sure you get an actual 1:1 copy which is not trivial (permissions, alt-data stream, & your hardlinks might get automatically re-adjusted or the data they point to might instead get copied). For example, if you were freshly installing windows:
C:\Users\
and create a new folder with the name for the actual account you wantChange Drive Letter and Paths...
. Mount in the following empty NTFS folder
and select the folder you created earlier.
Sounds like the Junction is possibly to another drive? Consider using a Volume MountPoint instead.
Ideally, you would have wanted to set this up from the start, otherwise you gotta make sure you get an actual 1:1 copy which is not trivial (permissions, alt-data stream, & your hardlinks might get automatically re-adjusted or the data they point to might instead get copied). For example, if you were freshly installing windows:
- Create an Admin user account which will only be used to setup the actual account you want.
- Go to
C:\Users\
and create a new folder with the name for the actual account you want- Go into Disk Management, rightclick the volume you want to be your profile, and select
Change Drive Letter and Paths...
.- In the popup, instead of assigning a drive letter, select
Mount in the following empty NTFS folder
and select the folder you created earlier.- Now actually create the account/user profile, set it to primary or whatever, and login and use that
I may have confused you with the note about an attempt from a few years ago involving a "C:/ProgramData/Vortex"➡️"D:/Vortex/" symbolic link.
I updated the issue description with same-drive, same-volume reproduction steps. One set of steps creates a symbolic link. The other set, a junction. I haven't tried linking to another volume, but I know only Symbolic links can be used for that. Junction and Hard links are same-volume only.
Ideally, Windows would let me choose the name I want instead of quietly creating one using the first n alphanumerics of my email address. There is a "proper" procedure for changing the username–which I followed–but it doesn't update Task Scheduler tasks, some Registry keys/values, or strings or binary data stored in files. ACLs (filesystem permissions) seem to have updated properly.
Describe the bug After performing a not-recommended rename of my Window user account and leaving a junction link with the new name in
C:\Users\
(and updating ACLs and Registry key/values), plugins loading from the$env:USERPROFILE/AppData/Roaming/Vortex/plugins/
will fail to load NodeJS/Electron dependencies as was seen in https://github.com/Nexus-Mods/Vortex/issues/8065#issuecomment-738714657.Booting to WinRE and swapping the junction link's and real directory's names allowed Vortex aftermarket plugins to load. Downloads still succeed because I have the download directory set to a different drive volume.
If the Vortex data directory itself is relocated with a symbolic link, the Vortex app will attempt to create a directory with the same name.
If it's relocated with a Junction link, Vortex continues with warnings and fails to initialize downloaded plugins, but experiences no critical errors.
To Reproduce Steps to reproduce the behavior: Symbolic Link
Junction Link
On previous PCs, I'd tried to use symbolic/junction links to relocate Vortex's data directory to a different drive volume. It failed back then and I didn't look into it further.
Expected behavior Any file/directory path reparse points such as symbolic links or junctions. These paths must resolved to "real" paths before R/W are possible on paths they point to. See https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getfullpathnamew and https://learn.microsoft.com/en-us/windows/win32/fileio/reparse-points-and-file-operations for Win32 API usage Symbolic links are available on almost any OS kernel and file system. Junctions are an NTFS feature and not restricted to Windows OSs.
Platform (please complete the following information):