"Protected location" message in RAM FS when selecting a source folder

While using the RAM File System software on Windows 10, I attempted to select a Source Folder located within "C:\Program Files". However, when I select any subfolder within that directory, for example "C:\Program Files\thinkorswim", the message "Protected location" appears beneath the folder path field, and I am unable to continue with the creation of a new volume.

Could you please provide more information about what this message means and why it appears? Specifically, is it related to Windows folder permissions, an intentional safety restriction within the software, or some other limitation?

Any additional details or guidance on how to proceed would be greatly appreciated.

Thank you,
Michael

Good news: nothing is wrong with your system. That message is a deliberate safety check in RAM File System, not a permissions error.

When you create a volume from a folder, RAM FS moves the original aside and puts a link in its place pointing at the RAM volume. Because a RAM volume is volatile, that link can briefly lead nowhere after an unexpected restart. In a data folder it's nothing more than a minor nuisance, but in a system folder like "C:\Program Files" it could potentially leave an application (or in the worst case Windows itself) unable to start. That's the reason for the check: these locations are excluded precisely so the software can't be used in a way that renders a system unstable or unusable. For the same reason, we currently don't offer a way to override it.

Worth knowing too: even without such check, creating a volume from a folder inside "C:\Program Files" would require administrator rights, since Windows itself protects that folder from being modified.

The simple fix is to reinstall your thinkorswim somewhere of your own choosing outside Program Files, for example "C:\thinkorswim" would work nicely. The installer lets you pick the location, and RAM FS will accept that path without complaint. Everything outside the protected system folders is allowed.

Thank you for the insight, it really helped to clear things up. I'll make the necessary path adjustments.

Best regards,
Michael