I think I'll shelve this until I can learn how to get everything to play nice with each other Yes, it could be an AV issue, because just like Windows, AV programs will over-zealously guard the Program Files folders A thought came to me is this a McAfee issue? That is just a guess though on my part and not an educated one. I am not very computer literate but at least I can try to follow instructions. I should note this is my 3rd attempt at getting it working, on a previous attempt I ended up seeing all of the folders listed inside the "Programs (x86)) file, I cannot give you a screen shot because the program needs me to give it permission to Access the staging folder which so far I cannot This is a brand new computer, at least for me. I am including this information in case its part of the problem, The Vortex folder is in Program Files and Not in Program Files(x86). I am having a similar issue but with the "Vortex Staging Folder". You can see step by step what I do, the errors, the permisssions, the read only status etc Here are screenshots in a 3rd party gallery.
By the way, i have the same permissions and read only settings for all the other mods I have installed. I HAVE ALSO GONE INTO PROPERTiES AND GAVE MY ACCOUNT USER ALL PERMISSION TO MODIFY THE FILE, AND UNCHECKED READ ONLY AND ALL THAT. Please try to install these mods using Vortex yourself? Here are two mods that cause this problem. Asking Vortex to try and fix the problem for me does nothing. It takes a long time and its easy to misspell a folder name or make a mistake transferring a file Then I simply copied the mod files into my new folder, archived it, then installed the 'new' mod I had to recreate the entire folder structure of the mod, by making a bunch of NEW FOLDERS on my own, and renaming them. ONE SOLUTION: Now I did figure out a way to fix it. I have installed about 50 mods and so far 2 of the mods give me this problem.
If your account has admin rights Vortex can try to unlock the file for you