Folder Guard controls access to files and folders on a configured Windows installation. It can hide a folder, deny access, make content read-only or require a folder password. Filters and trusted-program rules add exceptions or stronger restrictions. Folder Guard intercepts access attempts; it does not encrypt file contents or rewrite the protected data.
This difference matters outside the configured system. Moving a removable drive to another computer or starting another operating system does not carry the same restrictions with it. A person who needs encrypted files must use encryption rather than treating a hidden folder as ciphertext.
Apply and active protection complete the rule
Creating a restriction in the configuration window does not enforce it immediately. The user must apply the change and keep protection active. Pausing protection suspends the expected restriction until it resumes, even though the rule still appears in the configuration.
Folder passwords belong to folders rather than individual files. The documented hierarchy also limits a password on a subfolder whose parent already has password protection, or on a parent that contains another protected folder. Designing the protected tree after adding passwords can require removing or rearranging an earlier rule.
Read-only access blocks changes saved back to the protected item. It still permits copying and printing. If the goal is to stop data leaving the folder, read-only does not meet that goal.
Filters can override the visible folder setting
A filter can match a filename or folder path. Another filter can match the program requesting access. The rule then assigns full access, read-only access or no access. Filters override ordinary folder restrictions. A broad filter can therefore make a password or folder rule appear broken even when Folder Guard follows the higher-priority condition.
The troubleshooting path disables filters and tests a clean folder with a minimal rule. This separates a folder problem from a filter, user or program exception. Adding more rules before that test can hide the actual cause behind another override.
Trusted programs receive a broad exception
Backup, antivirus and disk utilities may miss protected content because the same rule that blocks another user can block their processes. Folder Guard can trust a specific executable path and grant it full access. One application may use several executable files, so trusting one component may not cover its complete workflow.
A trusted path overrides restrictions and filters. A wildcard can make the exception wider than intended, and trusting Windows Explorer would expose protected content through Explorer. The trusted-program rule identifies the executable that receives the exception.
Cloud synchronization has the same conflict. Protecting a local OneDrive or Dropbox folder can prevent the sync client from reading changes. It does not protect the remote provider copy. A trusted-program rule can give the documented sync executable access while the folder restriction remains in place.
Closing one window may not relock every process
An automatic relock after a folder window closes may leave another window or process with existing access. The notification-icon action relocks the folder globally, and workstation locking can also trigger a relock under the documented setting.
Ending the user-interface process creates another misleading state: the access prompt or hotkey can disappear while kernel protection remains active. The missing interface does not prove that the protected files have become open.
System paths need a recovery plan
A rule applied to the Windows directory, an entire system drive or another broad path can make the desktop blank or stop Windows components. Folder Guard recommends preparing Emergency Recovery, keeping a backup and proving the rule first on a disposable folder such as C:\Test.
Windows Search or another application can also retain a filename after protection begins. Folder Guard controls later access to the item, but it does not erase every history or index record created earlier. A hidden folder and a forgotten filename are separate privacy goals.
