I certainly understand not updating every time, although quickly reading over the release notes since 4063, which was released over a year ago now, there have been multiple bug fixes that could potentially be relevant to you, including some that affect restore/recovery scenarios. After all, the fact that backups are working perfectly does not always mean a restore will. So if you're going to stay behind on releases, I'd recommend at least keeping an eye on the release notes. But I just noticed a big red flag in your earlier post. You said you're backing up your C drive and Reflect is getting stuck on "Determining files to copy". I must have automatically substituted "Looking for changes" when I read that originally, because "Determining files to copy" only occurs with F&F backups rather than image backups. But if you're performing F&F backups of your entire C drive, you absolutely do not want to be doing that, so if that IS what you're doing, then you have a much larger problem here. If you expect to use that backup for system recovery purposes, it will not work properly in that context because restoring an F&F backup to certain areas of the C drive will break some file system techniques that Windows applies in various places, such as hard linking. And even if you don't care about full system recovery, an image backup will be significantly faster than an F&F backup when they're backing up the same data set, as would be the case if you're backing up the entire partition. In my tests on a file server's Data partition, an image backup ran 2.5x faster than an F&F backup. Restore performance would likely be similar. If you're running an F&F backup AND an image backup because you believe an F&F backup is necessary in order to recover individual files and folders as opposed to restoring the entire system, that is not the case. Image backups can be mounted to allow recovering individual files and folders, so having an F&F backup in addition is just wasting time and space. It's also worth pointing out that if you browse an F&F backup, files larger than 4GB cannot be restored properly that way due to the FAT32 emulation that Reflect uses in order to mount an F&F backup as a virtual disk; you have to use the Restore wizard instead for those files. Image backups do not have this limitation. The only case I can think of where it would make sense to perform an F&F backup of an entire partition would be if you had a file server where you had defined a lot of custom NTFS permissions throughout a complex folder hierarchy and you wanted a wizard-based method to restore individual files and folders with those custom permissions. Image backups do not directly allow that; you'd need to browse the backup and use command-line tools to restore data with those permissions. But apart from that very specific use case, if you want the whole partition, then use an image backup. And just to avoid potentially making a second mistake, when you set up an image backup job, make sure you don't capture JUST the C partition. On most systems, that isn't enough to get a backup that is usable for system restore purposes. If you're not sure, open Reflect and in the Backup Tasks area in the upper-left, click "Create an image of the partitions necessary to back up and restore Windows". The partitions that Reflect pre-selects in the wizard that will appear should be considered your "minimum viable backup" for system recovery purposes. You can add to that selection, but do not subtract from it.