Windows 11 folder keeps reverting back to read only

Hello! My name is Mostafa; I will assist you today.

I’m sorry that you are experiencing this issue. If you've already tried various troubleshooting steps but the folder keeps reverting back to read-only, there are a few more things you can try:

1. In addition to changing the controlled folder access to off, make sure you also disable it specifically for the folder causing the issue (C:\Users\USER\Appdata\Roaming\Vortex\downloads). To do this:

a. Open Windows Security by searching for it in the Start menu.

b. Click on "Virus & threat protection" in the left-hand menu.

c. Under "Ransomware protection," click on "Manage ransomware protection."

d. Turn off the toggle switch for "Controlled folder access."

e. Click "Yes" if prompted by User Account Control (UAC).

2. Run the Command Prompt as an administrator and use the attrib command:

a. Press Win + X and select "Command Prompt (Admin)" or "Windows PowerShell (Admin)."

b. In the command prompt window, navigate to the Vortex downloads folder using the cd command. For example:

cd C:\Users\USER\Appdata\Roaming\Vortex\downloads

d. Once inside the folder, run the following command to remove the read-only attribute:

attrib -r *.* /s

Please check the below link to try some solutions

https://www.bollyinside.com/articles/how-to-fix...

Please let me know if the above steps did not help. Thank you.

__________________________________________________

Disclaimer - There is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before downloading and installing it.

Thank you for getting back to me Mostafa Sadeghi.

I tried the command prompt but I am unsure how to word it? This is what I tried:

C:\Windows\System32>C:\Users\Mocah\Appdata\Roaming\Vortex\downloads-r*.*/s

The filename, directory name, or volume label syntax is incorrect.

C:\Windows\System32>C:\Users\Mocah\Appdata\Roaming\Vortex\downloads-r*.*/s

The filename, directory name, or volume label syntax is incorrect.

C:\Windows\System32>-r*.*/s C:\Users\Mocah\Appdata\Roaming\Vortex\downloads

'-r*.*' is not recognized as an internal or external command,

operable program or batch file.

Apologies for the confusion. The correct command to remove the read-only attribute from files and subfolders within the Vortex downloads folder is as follows:

attrib -r "C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*" /s

Make sure to replace "Mocah" with your actual username in the command.

Here's a breakdown of the command:

1. attrib: This is the command used to modify file attributes.
2. -r: This option removes the read-only attribute.
3. "C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*": This is the path to the folder you want to modify. The * at the end is a wildcard character representing all files and subfolders within the downloads folder.

4m./ /s: This option ensures that the command operates on all files and subfolders within the specified path.

Run this command in an elevated Command Prompt or PowerShell window, and it should remove the read-only attribute from the files and subfolders within the Vortex downloads folder.

None of those commands work.

C:\Windows\System32>"C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*":m./ /s:

'"C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*":m.' is not recognized as an internal or external command,

operable program or batch file.

C:\Windows\System32>C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*":

'C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*":' is not recognized as an internal or external command,

operable program or batch file.

C:\Windows\System32>C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*" /s

The filename, directory name, or volume label syntax is incorrect.

C:\Windows\System32>attrib -r "C:\Users\Mocah\AppData\Roaming\Vortex\downloads\*" /s

Thank you for taking the time to respond to this thread. If the steps provided didn't work, there's no need to worry. As this is an open forum, there's a chance that someone else in the community might have an idea or solution for this issue. I will keep this thread open and continue to explore possible solutions. Your contribution is greatly appreciated.