Group: Forum Members
That's correct. I believe -- but am not certain -- that Image Guardian relies on some functionality built into Windows that itself only works on NTFS volumes, in which case that limitation would stem from a dependency on a non-Macrium component. But even if that weren't the case, given that exFAT has been around since Vista and as you say is sometimes used as a default file system these days because it's the only modern file system that is read/write on Windows, Linux, and macOS without any third-party software required, my guess is that if getting Image Guardian working on exFAT wouldn't involve significant additional challenges over getting it working on NTFS, then it would have been done already.
But I'm not sure how you would propose to notify users. I personally think it would be annoying to be told, "These volumes are not protected by Image Guardian" all the time. Reflect already defaults to enabling Image Guardian on any destinations where it's possible, and the "Create a backup" tab that is shown when Reflect is first launched shows an Image Guardian badge for any volume that is protected -- and therefore its absence on exFAT volumes (and anywhere else) would indicate lack of protection. I personally think it makes much more sense to consider ransomware a threat that is NOT protected against until you have positive confirmation to the contrary, not assume that you're protected unless specifically warned otherwise.
As for your last sentence that, "It would good if the program were modified so that it does handle disks that are NTFS," Image Guardian already does handle NTFS disks. Was there a "not" missing in that sentence?