Soo, I downloaded this a couple weeks ago and finally got around to installing it today. I'm installing WSL2 on my win10 box, and for that I've got to get on the insider program slow ring. So before doing that I figured it was a good time to add another layer of protection to my system. I ran into problem and while researching how to resolve it I came across some details regarding various incompatibilities that I wish I had known earlier... I should add that a complicating factor for my experience is that I'm dual-booting. That's probably the reason I ran into the problem I did, but after discovering those details I mentioned I didn't even bother trying to fix it anymore and just uninstalled Rollback RX. I felt it was important enough to bring to everyone's attention here, since these details ARE NOT MENTIONED on the RBRX site (or if they are they're hidden pretty well) or by the installer.
I was reading some posts on the HorizonDataSys subreddit (because apparently that's replaced their forum now..) and noticed an unofficial FAQ written by TheRollbackFrog from Wilders Security Forums. Can't link it but it's 5 months old as of today and titled "Rollback RX™ - The “unOfishul” FAQ". That should be enough for anyone who wants to to find it. And in my opinion, if you're using RBRX you should read it, because there's some potential gotcha's lurking... The FAQ's like 3 pages long and I don't know if I can post it all here, so I'll just give a quick summary of the dealbreakers I discovered and urge you all to read the FAQ yourselves. (if an admin/mod says it's OK to post that much here I'll be happy to do so and save y'all some clicks...)
So, the dealbreakers for me... 1) RollBack Rx does not allow TRIM commands to be issued directly to an SSD, which impacts the speed and total life span of an SSD. 2) Any access of a Rollback protected partition from other than the OS that is installed on it (which I do in my dual-boot environment) is considered dangerous. Snapshots, the Rollback system, data files and/or the residing OS may be damaged. 3) Windows Updates are tricky and have caused problems in the past. It's recommended now to disable Rollback RX before any updates. (which kinda defeats the purpose for me, since a quick way of undoing updates was my primary goal for installing RBRX...) 4)
RBRX doesn't play nice with disk imaging applications. Macrium Reflect is my main backup and I'm not willing to compromise that in any way.
Those were the main problems. The SSD issue was enough on its own for me to ditch RBRX. I'm fairly satisfied with the Macrium Reflect + Shadow Defender combo I've been using. RBRX sounded like it might improve upon Shadow Defender for me, but considering this new info I'll just stick with it for now.