Zeoinx Posted September 19, 2019 Share Posted September 19, 2019 So if Anyone has a clue what the hell is going on, I tried Reinstalling Vortex when it refused to open (Tried everything, running as admin, restarted PC, and then reinstalled Vortex and when i reinstalled, this started happening.) About ready to pull hair out. Link to comment Share on other sites More sharing options...
Tannin42 Posted September 19, 2019 Share Posted September 19, 2019 You changed where windows stores the appdata\roaming directory and it's not writable. Vortex doesn't "invent" permission errors, the fact you got this message means that windows actively prevented Vortex's attempt at writing there. This isn't a Vortex problem, it's a windows setup problem, appdata is supposed to be writable to the user owning it. Link to comment Share on other sites More sharing options...
Zeoinx Posted September 19, 2019 Author Share Posted September 19, 2019 You changed where windows stores the appdata\roaming directory and it's not writable.Vortex doesn't "invent" permission errors, the fact you got this message means that windows actively prevented Vortex's attempt at writing there. This isn't a Vortex problem, it's a windows setup problem, appdata is supposed to be writable to the user owning it.Its writeable, I opened Vortex many times SINCE changing it, along with all my other programs. Edit : It WAS writable, and I tried to turn off "Read Only" but for some reason, it keeps reenableing "readonly" access, dispite my "Applying" settings to change it. WTF is going on. Link to comment Share on other sites More sharing options...
Tannin42 Posted September 19, 2019 Share Posted September 19, 2019 What's going on is that you're not running Windows 95.The read-only flag is a remnant of dos times, ever since Windows NT file permissions are not implemented with a simple flag but with ACLs which you can manage on the security tab of the file properties.At least on NTFS drives. Link to comment Share on other sites More sharing options...
Zeoinx Posted September 23, 2019 Author Share Posted September 23, 2019 So i just upgraded my PC with a new SSD for my main HD, brand new install of windows, and guess what, this f*#@en error persists. What do I need to do to let this program run. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 23, 2019 Share Posted September 23, 2019 So i just upgraded my PC with a new SSD for my main HD, brand new install of windows, and guess what, this f*#@en error persists. What do I need to do to let this program run. Why is the path for appdata E:\ ? Are you using symbolic links to have your appdata on E:\ instead of C:\ ? Link to comment Share on other sites More sharing options...
Zeoinx Posted September 24, 2019 Author Share Posted September 24, 2019 So i just upgraded my PC with a new SSD for my main HD, brand new install of windows, and guess what, this f*#@en error persists. What do I need to do to let this program run. Why is the path for appdata E:\ ? Are you using symbolic links to have your appdata on E:\ instead of C:\ ? I prob should mention, the clean update is now C: drive, before the clean reinstall, i had moved my app data to the other drive for more room as my former C drive was actually very tiny. This is a brand new HD. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 24, 2019 Share Posted September 24, 2019 So i just upgraded my PC with a new SSD for my main HD, brand new install of windows, and guess what, this f*#@en error persists. What do I need to do to let this program run. Why is the path for appdata E:\ ? Are you using symbolic links to have your appdata on E:\ instead of C:\ ? I prob should mention, the clean update is now C: drive, before the clean reinstall, i had moved my app data to the other drive for more room as my former C drive was actually very tiny. This is a brand new HD. So, after you reinstalled windows etc, did you do a clean install of EVERYTHING, or did you restore a backup of things like Vortex etc? I HOPE you didn't copy your old appdata folder from E to your newly installed C drive. Link to comment Share on other sites More sharing options...
Zeoinx Posted September 24, 2019 Author Share Posted September 24, 2019 So i just upgraded my PC with a new SSD for my main HD, brand new install of windows, and guess what, this f*#@en error persists. What do I need to do to let this program run. Why is the path for appdata E:\ ? Are you using symbolic links to have your appdata on E:\ instead of C:\ ? I prob should mention, the clean update is now C: drive, before the clean reinstall, i had moved my app data to the other drive for more room as my former C drive was actually very tiny. This is a brand new HD. So, after you reinstalled windows etc, did you do a clean install of EVERYTHING, or did you restore a backup of things like Vortex etc? I HOPE you didn't copy your old appdata folder from E to your newly installed C drive. This was a clean install, I put in a entirely new harddrive, which was the main reason for the clean install to begin with. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 24, 2019 Share Posted September 24, 2019 This was a clean install, I put in a entirely new harddrive, which was the main reason for the clean install to begin with. So, are you saying you're still getting the error from your original post?about not being able to mkdir on E:\appdata? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.