When the latter is on a separate partition, that one can be left as-is when performing a Reflect restore. I know that sounds like a blunt instrument solution, but I personally always store my user data on a separate partition simply because it gives me a way to restore my OS to an earlier point in time without having to roll back my personal data to that earlier point in time as well. As a last resort, you could create a separate partition on your disk to store the data and easily exclude that partition from your backups. Other than that, if you haven't already restarted, I'd suggest doing that in case the VSS engine needs to restart to apply those changes. So if you haven't already, verify that the item is in the correct folder and that you don't have a typo of some kind. I've never had a use case for this, but I've pulled my hair out dealing with registry modifications not having an effect and then seeing that I had made a tiny typo when setting it up. Unfortunately, the files under myDymoMount are still being backed up! Is there any way to prevent mounted file systems from being backed up by Macrium Reflect (or to get the above Registry modification to actually block the backup of those files)?
REG_SZ_MULTI: C:\Users\wbrel\Documents\myDymoMount\*.* /s Under FilesNotToSnapshotMacriumImage I added: I've tried the Registry modification that has been widely suggested as a way of excluding files from Image backups. This file system contains UNENCRYPTED versions of my files which I would like to exclude from an Image backup. Those files are accessed locally via a mounted virtual file system which in my case appears as C:\Users\wbrel\Documents\myDymoMount. I'm using the Cryptomator program to securely store files in Google Drive.