Rollback RX v10.x (Home & Professional)

Yesnoo... you pay your money, you take your chances.

HDS official position is they are letting all Windows updates take place under Win10. If any of them become an issue, they will deal with it at that time. Of course with Automatic updates being uncontrolled for Windows 10 HOME, if one of them turns out "bad," they'll have a lot of work on their hands with attempted repairs.

Punt!

 

I will wait for now then.

 

Thank you for these points!

I use Kaspersky Internet Security 2016. AppGuard and HMP.A. What I'm worried about is with HMP.A because it does not have exclusion with other components apart from Exploit Mitigation component.
So, will HMP.A not interfere with Rollback RX?

 

I expect you will have to test this to find out. On the other hand you might try asking HDS tech support but I personally would not trust their reassurances (if thats what they give you).

 

Thanks!

 

XhenEd, can you give me a link to the HMP.A reference above (I have no idea what it is)?

 

It's HitmanPro.Alert.
http://www.surfright.nl/en/alert

Edit: I went ahead and installed Rollback RX on my Windows 10 64-bit laptop. So far, even when I rolled back to test, no issues arose. Yay!

 

To test you will have to run Hitman and then see if it has destroyed Rx. You will know if you get a failed reboot or a failed restore. I strongly suggest you create an image of the drive without Rx installed before you do this test as your system will be destroyed if there is a problem.

One thing you should be aware of even if there is no problem. An update to Hitman may well cause problems in the future so you should proceed accordingly.

 

So I thought I'd give Rollback RX and Drive Cloner Rx a whirl. (Anyone know the return / refund policy... I thought the website said 30 day Money Back G)

Here is what happened.

Run the software in windows and get this message "get protected disk part info is false"...Can't proceed any further....Tried all compatibility modes with administrator privileges, eve for the shortcut.

Make iso or usb, or cd and boot up with any of these and see the error "Failed to load FLClover Recovery Console. if you know the location you can run it manually - OK or No."

But since my usb mouse and keyboard do not work in the cd or usb or iso boot up environment. I can't click OK, and If I could I don't know what the FLClover is or where it is at.

So RollbackRX seems to work great, but if I have any hopes of imaging the drive along with the snapshots made by Rollback, I'm out of luck, since Drive Cloner is not working.

 

Based on my previous experience with the product... your description would be pretty accurate.

 

Hi! After using Rollback RX (10.2-4) the last year there is a consistent bug (already reported in 2013 here): There is only the installation snapshot and after rolling back to it, the (C System harddrive keeps loosing space (Gigabytes) until it is drained. And the only thing that sorts it is when updating the baseline also after rolling back to the installation snapshot.
By the way: Posting on Horizon Datasys forum doesn't work after login.

Windows 7 - 64 bit
32 GB memory
GeForce GTX 770
Harddisk is SAMSUNG MZ7PD128HAFV-000
Windows system memory has been set manually to 800MB.
The space eating bug appears both with hibernation turned off (hiberfil.sys deleted) and on.
It also appears when a folder in advanced settings is excepted from the snapshot and when none are excepted.

 

Smuck, if your snapshots aren't important at the moment, I would do the following...

1. Uninstall Rollback to your CURRENT SYSTEM STATE and do a hard reBOOT (Restart).
2. If you're running any sort of SSD specific management (Samsung Magician, etc.), stop the process from doing anything to your SSD.
3. Download this SSDtool and run it. It requires no installation and performs on your SSD (after you select it) the exact same manual OPTIMIZATION function that Windows 8.x would perform... it will TRIM all the FreeSpace inside of your SSD using the operating system itself. After its execution, the actual OS TRIM function takes place in the background and should be finished in 10-15 seconds. Make sure you keep the Samsung ssd tool from running anymore.
4. ReInstall Rollback and see if you keep experiencing the same type of problem.

Understand the following...

1. Any OS automatic TRIMming of your SSD is inhibited while Rollback is installed. That type of operation will only occur after a Rollback unInstall and a complete reBOOT of your system. On Windows 7, only the SSDtool will do it for you as an "optimization" ON DEMAND (on demand "optimization" didn't appear until W8, only automatic TRIMming existed in W7). Automatic "optimization" (dynamic TRIMming) will occur normally but only after Rollback has been unInstalled and your system has been reBOOTed).

2. There have been reported cases of the Samsung SSD tool, Magician I believe, talking directly to the SSD behind the back of the protected OS... this is an absolute no-no for Rollback to be successful. This may only be done following the successful uinstallation of Rollback followed by a reBOOT.

It's safest to schedule any disk/system/FileSystem maintenance activities while Rollback is uninstalled and following a reBOOT. You'll notice I keep saying "following a reBOOT." I say this because if you uninstall Rollback to your CURRENT SYSTEM STATE (rather than a previous snapshot), it will not ask for a reBOOT when it's complete. The problem with this is the flawed driver Rollback uses while it's installed is still in place following the unInstall... it's this driver that contains the SSD management flaw associated with the lack of TRIMming an SSD while it's protected by Rollback. A reBoot will eliminate this driver if Rollback has been uninstalled.

PS- I posted your inquiry above in the Rollback forum for you...

Exactly what have you done here... restricted the PageFile size (Windows virtual memory) or some other change... I see 32mB of RAM in that system of yours.

 

Hi

I wonder what happens when one has RBRX installed and makes a backup with, lets say Aomei or Flashback/AX64, and restores named backup at a later moment. Are ALL, even the baseline, of the snapshots of RBRX that one may had gone after the restore but with RBRX otherwise ok ?

 

The answer varies with the backup tool in play. "Standard" backup tools (not using what's called a TRACKING FILE <to account for changes in the file system>), running under the LIVE Windows system, will contain only the CURRENT SYSTEM STATE and the special Rollback MBR (Master BOOT Record). If this image is restored, it will not BOOT correctly until the System's MBR has been restored to a normal state. Once that's done, the system will BOOT with a completely neutered Rollback protection system, a few unrecognizable Rollback errors, and no usable snapshot data, including the baseline... and the longer that system stays running, the worse the chance is that you may even be able to resurrect any useful snapshot data at all, even using the supposedly great Horizon DataSys SCAVENGER tool (used for attempted restore of data from blown up Rollback systems).

 

@TheRollbackFrog thanks! Yes the 800MB is the pagefile limit; it should force windows to use the 32GB memory instead of the harddrive.

Now the SSDtool has been run according to your instructions., but it takes at least a couple of weeks to notice the difference ...

 

What does the above exactly mean ? I mean if i do a backup with C: and the BOOT partition would that not even boot correctly or how do you mean it ?


So, does it help to do a sector by sector ?

 

The System will not BOOT successfully, it will hang with a <BLACK> screen or you'll get some nasty error message. You get that because you are using the special Rollback MBR to BOOT the system but none of the linkages needed by that BOOT path were saved in the image that was done. You either need those linkages (not imaged) or a standard BOOT path (not imaged either). Most users recover from this situation by restoring a STANDARD Windows BOOT record. Macrium Reflect has this capability in its Recovery Media (others may) but usually a separate MBR management tool is required (usually running from a WinPE environment).

An all SECTOR (sector-by-sector, RAW... term depends on what imager you use) image should work just fine with the snapshots in place when done... but the backup image will be significantly larger than the "used" sector image done under LIVE Windows, especially if you have "stale" (deleted from both the system and the RecycleBin) data laying around on your imaged HDD. SSDs should image well since Windows (7 & beyond) should be actively TRIMming them upon file deletion. It also helps the SSD under Windows 7 if you run the SSDtool prior to your creation of the image... this will insure the "cleanest" SSD you can have. Of course this only applies to SSDs using either DRAT (Deterministic Read After TRIM) or RZAT (Read ZERO After TRIM). SSDs using"non-Deterministic TRIM" (each read command to the Logical block address <LBA> after a Trim may return different data) will, of course, create a very large ALL SECTOR image. The only one of these I've run across was made by TRANSCEND but I'm sure there are others out there (it's probably determined by the internal controller in use by the SSD itself).

 

That should pretty much happen normally even without resizing the PageFile. Windows will use as much RAM as possible for applications first before heading into that PageFile. Its big need is File Caching and it loves to use available RAM for that to really speed up file moves/copys.

I run a 425mB PageFile on an 8gB system based on my application mix (not very sophisticated and for sure, not very multi-tasked). That size is needed at a minimum if you want to save DMP files from Windows' crashes... otherwise they won't be saved.

 

Mr Frog

Ok, got it, thank you !
That was consistent with the info i had so it was good to get that confirmed.

I tried a sector by sector recently and it was faster then i thought so to do those is no big issue in any way.

 

I think so.
In the past, with Rx v9.x you could backup and recover all the snapshots along in a backup, with a sector by sector backup,
but I don't know if it works anymore with Rx v10.x ...

 

It works just fine with most of the ALL SECTOR (RAW, sector-by-sector) backup tools I have used.

 

Are you talking about Rx 10.x ? Windows 10?
(not that it matters what OS is installed,when you do RAW cold sector-by-sector off an hard drive..would be program compatability issues rather..)

I will play around a bit with RX/Clone RX,once I have done RAW s-b-s off my current setup.
Got hybrid sshd on this new laptop, so why not.
(will be interesting to see how RX works/if it works at all, with a hybrid drive,since it can't disable the SSD cache, as it's not accessible by any software)

 

Stode, an SSHD looks no different to your system than a standard HDD... the internal NAND caching completely manages itself. They're usually WRITE THROUGH caches with the cache itself assisting the speed of the most referenced read elements.

As you suggested, the OS in use has little or no affect on RAW sector imaging. I have used Acronis RAW and IFW RAW on v10.x versions of Rollback RX and it acts as it always has... it restores the system just fine.

 

Hmm,seems like they released a new version again...

Rollback Rx Pro 10.4 Build #: 2700722190
Last updated: October 9, 2015



What's New:

• Supporting Windows 10.
• Added an option on the new snapshot screen to create new snapshot using Windows Volume Shadow service.
• Added UseVss=1/0 switch in the setup.ini to set the VSS option.
• Moved entire license activation process from the Windows service to the subsystem to avoid cracking.
• Added a check in the subsystem to automatically defrag snapshot when free space is below 10GB.
• Fixed various compatibiltiy issue reported by customers.
• Added Turkish language support.