Zeoinx Posted September 25, 2019 Author Share Posted September 25, 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? yes, its now the same error, but in the default directory. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 25, 2019 Share Posted September 25, 2019 OK, after searching for the error you['re getting it sounds like a Permissions Issue, and a possible problem with the install package.All of the articles mention "NPM" whatever that is. You should probably go to github and report that as a bug just in case, although I haven't seen anybody else have this problem.Are you using an Admin account, and did you install Vortex as an Admin?You're supposed to run the Vortex Install package as an Admin, and then after Vortex is installed, only run it NOT as an Admin Link to comment Share on other sites More sharing options...
Tannin42 Posted September 25, 2019 Share Posted September 25, 2019 The first answer I gave on this thread is the only answer you need. This is the third time I'm giving the same user this same answer:EPERM is a permission errorit means that the OS (windows) doesn't allow Vortex to create a directory inside AppData/RoamingAny default configured Windows and any sanely configured windows has that directory writable to its owners, yours doesn't Why? The only explanation is that you changed the permissions, possibly unwittinglyThe solution? You have to use Windows to change the file permissions on AppData/Roaming so that the user Zeoinx can write to it and then make sure you actually run Vortex as that user. None of this is a Vortex issue. None of this can be fixed by Vortex. None of this needs to be reported to us. Link to comment Share on other sites More sharing options...
Zeoinx Posted September 26, 2019 Author Share Posted September 26, 2019 OK, after searching for the error you['re getting it sounds like a Permissions Issue, and a possible problem with the install package.All of the articles mention "NPM" whatever that is. You should probably go to github and report that as a bug just in case, although I haven't seen anybody else have this problem. Are you using an Admin account, and did you install Vortex as an Admin? You're supposed to run the Vortex Install package as an Admin, and then after Vortex is installed, only run it NOT as an Admin Yes, I am on an admin account, I have no idea how to change permissions, so I have no idea how this would have happened to begin with. If someone would walk me though on how to give permissions back to Vortex, I would love to do it, but considering this is the ONLY program to ever happen to, and yet everything else i use makes folders in that directory all the damn time, this makes no sense to me how THIS one program doesnt have permission and yet its not a votex problem. Just give me a walkthrough on how to attempt to fix this please Btw, I might as well point out, I can manually make a folder myself in the directory in question, so i am also confused why Vortex cant. Link to comment Share on other sites More sharing options...
Tannin42 Posted September 26, 2019 Share Posted September 26, 2019 https://lmgtfy.com/?q=windows+file+permission Link to comment Share on other sites More sharing options...
Zeoinx Posted September 29, 2019 Author Share Posted September 29, 2019 The first answer I gave on this thread is the only answer you need. This is the third time I'm giving the same user this same answer:EPERM is a permission errorit means that the OS (windows) doesn't allow Vortex to create a directory inside AppData/RoamingAny default configured Windows and any sanely configured windows has that directory writable to its owners, yours doesn't Why? The only explanation is that you changed the permissions, possibly unwittinglyThe solution? You have to use Windows to change the file permissions on AppData/Roaming so that the user Zeoinx can write to it and then make sure you actually run Vortex as that user. None of this is a Vortex issue. None of this can be fixed by Vortex. None of this needs to be reported to us.Your ego is beyond belief, especially when I have stated multiple times I have not changed a god damn thing. how you became a staff member is beyond me, but enjoy your power fantasy online. If this is how you treat your normal job, I feel sorry for your coworkers. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted September 29, 2019 Share Posted September 29, 2019 The first answer I gave on this thread is the only answer you need. This is the third time I'm giving the same user this same answer:EPERM is a permission errorit means that the OS (windows) doesn't allow Vortex to create a directory inside AppData/RoamingAny default configured Windows and any sanely configured windows has that directory writable to its owners, yours doesn't Why? The only explanation is that you changed the permissions, possibly unwittinglyThe solution? You have to use Windows to change the file permissions on AppData/Roaming so that the user Zeoinx can write to it and then make sure you actually run Vortex as that user. None of this is a Vortex issue. None of this can be fixed by Vortex. None of this needs to be reported to us.Your ego is beyond belief, especially when I have stated multiple times I have not changed a god damn thing. how you became a staff member is beyond me, but enjoy your power fantasy online. If this is how you treat your normal job, I feel sorry for your coworkers. The staff member in question is Tannin42, the person who developed Vortex, MO1, and MO2. He;s a professional programmer who knows what he's talking about. Link to comment Share on other sites More sharing options...
HadToRegister Posted September 29, 2019 Share Posted September 29, 2019 This isn't a Vortex problem, it's a system specific problem, otherwise there would be multiple threads about this.You have something set wrong on your system.Tanni42 became a staff member once he was hired to write Vortex, he has told you what you need to do, but you refuse to do so.The very first result of a google search How to Take Ownership of Files and Folders in WindowsDid you run the Vortex installer as an admin?You shouldAfter that, you should NOT run Vortex as an adminDo you have Vortex set in SHARED or PER-USER mode? SETTINGS--------->VORTEX--------->Multi-User Mode Link to comment Share on other sites More sharing options...
Zeoinx Posted September 30, 2019 Author Share Posted September 30, 2019 This isn't a Vortex problem, it's a system specific problem, otherwise there would be multiple threads about this. You have something set wrong on your system. Tanni42 became a staff member once he was hired to write Vortex, he has told you what you need to do, but you refuse to do so. The very first result of a google search How to Take Ownership of Files and Folders in WindowsDid you run the Vortex installer as an admin?You shouldAfter that, you should NOT run Vortex as an admin Do you have Vortex set in SHARED or PER-USER mode? SETTINGS--------->VORTEX--------->Multi-User Mode I checked all the "security tabs" for the folders in question, I gave myself FULL PERMISSION on all of them, i am still getting the error. How do I check the Vortex set "shared or per-user" mode if i cant OPEN vortex? Is this another tab somewhere i need to find? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.