Jump to content

coltontooman

Recommended Posts

hi, i am trying to give custom directories permission for vortex the mods are on the same drive as skyrim when configuring the download and staging area directories i un-tick the read only mark for root and all sub folders, (im putting sub folders to organize between fallout 4 and skyrim mods) and after i change the file permission i open vortex again only to see that it has undone the permissions i set and gone back to defaults. does anyone have any insight ?( i wish i could correct the title)

Edited by coltontooman
Link to comment
Share on other sites

Welcome to the wonderful world of Windows User Account Control. This is a "feature" of the newer Windows OS that prevents any changes being made, by anyone, to any file on the computer.

Windows has taken control of all the files on your hard drive and set them to read only. My experience was that I disconnected from the internet, opened the Control Panel and disabled the User Account Control. I then removed the "Read Only" check for the entire hard drive. When it finished running, I checked my files and they were then able to be changed.

However, since then, they were mysteriously set to "Read Only" again.

Link to comment
Share on other sites

Ah, Microsoft... "Protecting users from themselves, preferably without their consent".

Did you try to use "TakeOwnership"? I use it all the time, when Windows suddenly decides for me, that I can't delete or move this or that.
It's a simple hack. Actually, it's not even a hack, it simply automates what can be done within Windows, but what normally is a tedious and long process.
Google it, and if you decide to use it, after downloading it should be a simple registry entry. After adding it to registry, you should have access to "TakeOwnership" command under right-mouse context menu. You just right-click a file or folder, then choose "TakeOwnership". This executes a script, which will give you FULL permissions to a file or folder, meaning that from now on, you can change all attributes for these files, move them, delete et c. Can't guarantee it will work, but you may as well give it a try. If you are using AV software with some strict rules like me, remember to whitelist "TO", so it can do its work properly.

EXERCISE CAUTION though. Using "TakeOwnership" on third-party files and custom created folders is fine, but Windows system files and folders, as well as whole drives are not meant to be fiddled with like this. In other words, never ever try to use "TakeOwnership" on whole drives or system files and folders, as this may, and probably will totally screw your system.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...