Hi Joe, on three occasions parts of Rollback Rx were mistaken for an MBR rootkit on my old XP 32 bit pc. On two of those occasions I was informed that the issue was resolved, it was not I have reinstalled Rollback Rx on my new Win7 64 bit pc, I have temporarily removed Prevx. Can you guarantee that this issue where Prevx deletes parts of Rollback Rx (effectively destroying the snapshots) has been resolved
The problem is Rollback Rx uses rootkit-like technologies with the MBR. Prevx has been right in picking these up. There should be dialog with the manufacturers of Rollback Rx to make sure their product is compatible with such a sophisticated rootkit scanner as Prevx.
I am fully aware of that, and I agree their should be some dialogue between both. That however is not the issue, my concern is will my snapshots be deleted, Prevx has previously on two occasions wrongly informed me that it was no longer an issue. I really hope they have resolved this problem.
Just add Rollback Rx Folder to the detection overrides section of Prevx and that should suffice but Joe will have to confirm if that will work!! Or the file that is detected by Prevx and add that also! TH
I have done that, the second time it was detected upon installation. I to thought that would do the trick so did Prevx help. But that proved not to be the case During a scan it detected add-ware, then when I clicked remove, on the subsequent scan it detected the MBR... Snapshots destroyed, as Prevx doesn't have a YES or NO option as to the removal of an MBR It's just: "It will be removed on reboot"...period!
Just to clarify - when was the last time you experienced this issue? The newer v3.0.5.x builds all have the correction in place to identify a Rollback Rx MBR. Let me know!
I haven't been using Prevx for some months, because of this issue. I installed it on my win7 x64, but un-installed it when I realised Rollback Rx was compatible with my new PC. I just wanted to be sure it wouldn't destroy any snapshots Thanks for your reply, I'll give Prevx/Rollback Rx combo another try.
Let's keep the hyperbole to a minimum. I really don't believe that Rollback Rx can be considered as rogue software by any reasonable (or unreasonable for that matter) definition of the word. Blue
Potential users of Rollback Rx (or any software solution for that matter) do need to understand the basic functional attributes of the product and what that means to the greater operating paradigm with which they use their machines. Rollback Rx - and like products (AyRecovery/EAZ-Fix/Comodo Time Machine) - does place some important constraints around what a user can do outside of the environment created by the product. It's simply a detail that needs to be understood to productively use the product (and there are plenty of satisfied users available). Blue