Windows 11 folder keeps reverting back to read only

The problem that myself, and potentially some others here are having, is specifically the fact that that block being filled means there is a read-only file somewhere within the target folder,

That is not correct. If you look carefully, you will see that the box is always a solid block even if there are zero files marked read-only within the folder.

It is, in fact, not an indicator at all. Microsoft should never have used a checkbox for a command. And that's all it is, a command. When you click it clear, you're telling Windows that you want to unset read-only from any files that may be read-only within the folder and its subfolders. When you check the box, you're telling Windows you want to set all files within the folder and its subfolders to read-only. Whether you set or unset, it only affects files. The read-only state of the folder, and any of its subfolders, is not affected. Only files are affected.

So, the item labeled "Read-only (Only applies to files in the folder)" does not indicate anything. However, to your point, it may be used to provide relief (possibly temporary) from a problem (TBD) that is setting one or more files within your folder to read-only. The problem with this bad interface design is that it is misleading people into believing that Windows "keeps resetting my folder to read-only". And that certainly distracts from finding the root cause of whatever problem they're having.

No doubt something is setting one or more files to read-only for some users and I will go back and edit my replies to be considerate of the fact that the use of this command to remove the read-only attribute from files could be helpful, but more investigation is needed to identify which files are being set read-only, when that occurs, and what processes are involved.

Gunner hanna, thank you for the thorough explanation of the problem. But what is the solution?

I'd like to respectfully draw attention to what I think the issue might be with your communication, here.
First - that block is not meaningless, and may actually indicate exactly the issue some people are having, which is actually what is explicitly mentioned immediately after the statement that the block is 'essentially meaningless'.
The problem that myself, and potentially some others here are having, is specifically the fact that that block being filled means there is a read-only file somewhere within the target folder, though they may not know which file is read-only, and that read-only file may be hidden, but that contained read-only status may infact be the problem, as is potentially the case with the original Vortex user's problem.

I specifically draw attention to the fact that the target read-only file may be hidden because as the cmd prompts you directed them to use revealed to me, unticking this box will not remove the read-only attribute from hidden files. The cmd dialogue, however, specifically told me which files were hidden and still marked read-only so I could manually remove that attribute myself.

Please do not dismiss people who are correctly recognizing their issue just because they cannot access the deeper information to reveal why that is the issue.

it happens when I attempt to save to my computer so I can work on in remote locations. So every time i attempt to save to computer.

What happens? Details are very important. What error message is displayed?

it happens when I attempt to save to my computer so I can work on in remote locations. So every time i attempt to save to computer.