Since you want :
- Documents to stay protected, and
- Games to be able to create sub-folders and files in Documents,
- Without creating exceptions for the game programs.
This means that the games must be diverted into using other folders.
As most games don't expose such an option, here is a general
method that does not need any changes in the game.
I suggest using the free
to isolate the game in a sandbox (it's possible to have multiple
This way, while the game thinks it's using the Documents folder,
its disk requests are actually being redirected to a sub-folder
C:\Sandbox, so not using any protected folder.
This will also simplify uninstalling a game, since emptying
the sandbox is enough to wipe out a game with every file
and registry change that it ever did.
Installing a game in a sandbox is done by right-click of the
installer and using the context-menu option of "Run Sandboxed"
to choose the sandbox in which to execute it.
The game won't be able to create icons on the real desktop, so
running the game from the sandbox can be done in several ways:
- Create a real desktop icon via Sandboxie menu
Configure > Windows Shell Integration
- Right-click any file and open it using the context-menu option
of "Run Sandboxed"
- Designing a folder as "always sandboxed" so any program or file
opened from it are automatically sandboxed.
Sandboxie has many options to customize the behavior of its
I also use Sandboxie for testing new software or one that I don't
trust, since it protects my running system and also much simplifies
(Previous answer. See comments below as to why it's not very useful.)
There is an undocumented Windows feature for removing a folder from
Run PowerShell as Administrator
Enter the following command:
Remove-MpPreference -ControlledFolderAccessProtectedFolders "C:\Users\USERNAME\Documents"
does not document the parameter
ControlledFolderAccessProtectedFolders, but it still seems to be
On my computer Protected Folders is turned off, but this
parameter seems to be still accepted by the command.
Try it and see. If it works, you might consider removing
protection from sub-folders of
Documents, rather than the entire