Torrent Rollback Rx Pro 11.2 [x32|x64] [TeamOS]

[humax5]

Thank you

 

[bsdaddict]

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.

 

[mrbittles]

Any ay to trim ssd anyway if using rollback or eazyfix?

 

[bsdaddict]

Any ay to trim ssd anyway if using rollback or eazyfix?

I don't know about eazyfix, but for rollback RX afaik the answer is no. If eazyfix operates in a similar manner I'd guess it doesn't, but you should try to confirm that for yourself.

I gave the SSD section of the FAQ (which I can't access anymore from the link on reddit, for some reason, so found the original on the wilderssecurity forum) another read to double check, but no workarounds are mentioned. To the contrary, it recommends not using RRX to protect an SSD, period. If anyone's interested, here's the FAQ entry on SSD's:

2. Solid State Disks (SSDs): The operating system TRIM command is designed to enable the operating system to notify the SSD which pages no longer contain valid data due to deletions either by the user or operating system itself. During a delete operation, the OS will mark the sectors as free for use by new data and send a TRIM command to the SSD to mark them as not containing valid data. After that the SSD knows not to preserve the contents of the block when writing a page, resulting in significantly less write amplification (a condition known to decrease both the speed and finite life of the SSD) causing fewer writes to the flash memory (an overall LIFE limitation), higher write speed, and increased drive life.
Horizon DataSys, ever since the introduction of full SSD and TRIM support in RollBack Rx™ v9.1 on July 18, 2011, has been fielding questions associated with that stated capability. Many users have tested and found that the important TRIM function, required to properly manage a SSD under the Windows operating system, does not appear to be operational between the Rollback interface and the physical SSD.
Due to the above perceived anomaly concerning Rollback’s ability to properly TRIM a SSD, I decided to script a simple test to determine if the TRIM command was indeed being issued by Rollback during its storage space management. The result of that process has shown that RollBack Rx™ DOES NOT ALLOW the required TRIM commands to be issued directly to the SSD. This is definitely detrimental to both the expected speed of the device as well as its eventual total life span. My recommendation at this time would be to avoid the use of RollBack Rx™ as a protection mechanism for any part of a Solid State Disk until such time as Horizon DataSys engineers the proper method for management of Solid State Disks. In the past, Horizon DataSys has proven to have been incapable of the discovery process needed to deal with this serious SSD management anomaly. As a result, they have always stated that RollBack Rx™ was properly engineered to provide that important management function. This statement has been proven to be in error.

 

[JohnJo]

thanks very mych! this app look like a must have!

 

[helloworld1314]

Dear user @Steelmonkey,
it still works over here.

Not true Medicines.....please fix it ..thanks

 

[DjNaToTheS]

Dear user @helloworld1314,
Please follow the how to activate process.

Good luck to you.

 

[helloworld1314]

Dear user @helloworld1314,
Please follow the how to activate process.

Good luck to you.

thanks ... now i replace the file before restart..... it is ok....but when i change the date too long ... the app can not function will fail....


thanks
DjNaToTheS
again.



the .dll file ....very good .

 

[jason3354]

Can't seem to activate it ... I get the error license expired. Yes!!! The computer was restarted after the install, and the Medicines file was put in the Program files folder.

 

[DjNaToTheS]

Can't seem to activate it ... I get the error license expired. Yes!!! The computer was restarted after the install, and the Medicines file was put in the Program files folder.

Dear user, please make sure you follow the how to activate process.

 

[Uncle Mac]

Dear user, please make sure you follow the how to activate process.

Question. What do you think they are missing or doing wrong

 

[DjNaToTheS]

@TheMacGyver, I think he didn't click "demo" while installing.

 

[Uncle Mac]

i tested it, it works perfectly, no problem

​

 

[jason3354]

Replaced the Medicines file with the original file in ProgramFiles.. Still get the same message. Check attachment.

What file format is allowed for screenshot.

 

[Uncle Mac]

@jason3354 ..click on demo during installation, you have a problem

 

[Uncle Mac]

What file format is allowed for screenshot.

Lookimg Hosting>>> Full bbcodes pasted

 

[jason3354]

Replaced the Medicines file with the original file in ProgramFiles.. Still get the same message. Check attachment.

What file format is allowed for screenshot.

You must be registered for see links

 

[Uncle Mac]

@jason3354 copy pached file and paste in C:\Program Files\Shield and restart pc

 

[jason3354]

Yes... Now it works.. I was copying to the wrong folder.
But now I cant make a new snapshot.
I'm getting the error " Taking snapshot failed."
I've even rebooted the machine.

Here is a screenshot.

You must be registered for see links

Sorry... Any idea why snapshots are failing?

 

[drbuda]

Great share
downloading and seeding