Since I saw some people reporting issues on this software, it's better to state some facts about how it works and the possible issues one will face, especially when using this software with SSDs due to its nature of how it interacts with windows and hardware, especially under Windows 10. Before we go further I want to thank DJ for his work and this has nothing to do with him but rather with how the program interacts with windows.
As
@bsdaddict said, Rollback intercepts and prevents the TRIM command from ever been issued on the SSD. This command allows the SSD to "know" when Windows no longer needs a previously used disk block so that it may, internally, release and relocate the hardware NAND block storage.
Since Rollback hides it’s snapshot DATA from Windows, it must block Windows from letting the SSD know that a block is no longer in need and so without active TRIM information from the OS, SSDs must carry around unnecessary information almost forever which allows for very inefficient block management by the SSD. This can eventually lead to very slow WRITE speeds as time goes by and excessive WRITE AMPLIFICATION which shortens the expected lifespan of an SSD (google the terms for more info). Just to make it clear, that doesn't mean you will have issues on day one. It all depends on the frequency and amount of writing that you do on your SSD as well as the frequency of snapshots.
Now to make things worse, when a snapshot is taken, all it does is leave the original DATA in place on the disk, protect it, and start a new snapshot. This is known as REDIRECT-ON-WRITE technology rather than COPY-ON-WRITE technology used with normal disk imaging programs. In order for Rollback to do this, it needs to hide its snapshot data from the Windows OS itself… a
very dangerous process at best.
If Windows doesn’t know about Rollback’s snapshot DATA, it just might destroy it when doing certain actions like re-partitioning during OS upgrades, certain uses of the Windows OS Recovery System, any use of external OSes (live CD) for the purposes of FileStructure cleanup, disk defragmentation, etc and is some cases even dual/multiboot. That’s the main reason Rollback takes over your System’s MBR (Master BOOT Record) so that it may operate UNDER (hidden from) the Windows Operating System.
That being said it's not a bad program and in most cases, it will do what it promises if that's what people are after. I just feel that users should know of its issues before the install it especially on SSDs and also the possible risks. I would also suggest to google and read about the importance of the TRIM command on SSDs.
I hope it helped.