Knowledgebase : RollBack Rx
 

Rollback Rx will only protect Disk Zero (the primary drive). Prior to the installation of RollBack Rx, make sure the drive C is on Disk 0.

To find out if the drive C is on Disk 0- follow the below steps:

1.) Start > Computer (right-click) > Manage:




2.) It should open up 'Computer Management' application -> Click on 'Storage' -> Click on 'Disk Management'

 

As you will notice from the above screenshot, that the disk is on Disk 0.

If you require further assistance, contact technical support -> 'Submit a Ticket'

 

The following steps are applicable to disable automatic Rootkit scan on AVG Internet Security 2014:

1. Open AVG Internet Security 2014 Console.

2. Click on the 'Scan Now' settings. (See below screenshot)

3. Next, click on 'Scan whole computer' settings. (See below screenshot)



4. The final step is under- 'Scan whole computer settings', make sure to uncheck 'Scan for rootkits'. (See below screenshot)

5. Save the current settings and AVG Internet Security scan should now have rootkit scan disabled. 

 

Did you forget the password to the RollBack Rx console?  This is only applicable to RollBack Rx v9.x

To recovery password, please follow the below steps on RollBack Rx:

1. During the sub-console password prompt of the RollBack Rx: (Below is screenshot of what it should look like) 

 

2. The next step is to press: 'Alt-F1' simultaneously - If done correctly, RollBack Rx will provide an encrypted string: (Such as below)

3. The next step is to "Submit a ticket" along with the encrypted string retrieved from RollBack Rx, the email address used during the purchase and the Product ID and Order information for verification.

 

Once the ticket is submitted, the technical support will verify the information and provide you the password for the RollBack Rx console.

During the setup of RollBack Rx- you may come across this error message: "Total sectors not consistent with disk size setup cannot continue". This error is most likely to occur during the subconsole setup of RollBack Rx. 

In order to realise why the error is caused- lets take a look at how RollBack Rx setup takes place.

As you know it, RollBack has two main components, the Windows component (drivers, registry settings, DLLs, GUI...) and the Subsystem Component.

When we run the setup of RollBack, we first setup the Windows component in Windows O.S. and then we reboot the system to install the Subsystem Component.

During the setup of the Windows component, we get the disk information such as the disk size, how many partitions...all that stuff from Windows O.S.


When we install the Subsystem component, we get the disk information from BIOS (because there is no Windows at that point).

Because we are essentially getting the information about the same disk, in most cases, the information match.

But in this case, the disk information that we received from Windows and the BIOS do not match. For example the Windows says it's a 100GB disk but the BIOS says it's a 98GB disk (therefore the total sectors do not match).


When RollBack detects this inconsistency, it stops the setup and reports the error ""Total sectors not consistent with disk size setup cannot continue". 

The problem is most likely caused by the BIOS. Because BIOS is a much older technology than Windows OS and it’s less frequently updated, so sometime an old BIOS is not able to recognize the newest and latest hard disk.

In order to resolve this error - update your system's BIOS  so it can recognize newer hard drives. After updating the BIOS- run the RollBack Rx setup again.

 

If updating the BIOS does not solve this problem, there is an overwrite switch for RollBack to ignore this check during setup, so RollBack can go ahead be installed.

To do that, we just need to enable VerifySector=0 switch in the setup.ini (By default this setting is commented off, remove the ; before VerifySector=0 will enable the switch).

Go to your RollBack Rx setup folder and open the setup.ini text document using notepad. Remove ';' from the line 'VerifySector=0'. This will enable the switch. (See screenshot below)

 

After commenting out the line. Run the RollBack Rx setup.

NOTE:  There is some risk involved by editing the 'VerifySector' line in the Setup.ini. Going back to the aforementioned example, Windows reports the disk is 100GB, the BIOS reports the disk is 99GB.

If Windows writes some data to the 99.5GB part of the disk, RollBack subsystem will not be able to restore (access) this data when the subsystem restores the disk.


If you still have trouble installing RollBack Rx- contact Horizon DataSys technical support -> "Submit a Ticket"

 

When you purchase a license key for a software solution (i.e- RollBack Rx, Drive Vaccine or Drive Cloner)  from Horizon DataSys, there is no limit to the number of times that license key may be activated - these licenses are perpectual as well.

Single license key can only be used on a single machine at any given time. 

When you use the license key for the first time it will "lock" itself to that specific computer. If you subsequently do a proper uninstallation of the software from that PC, your license key will automatically be "freed" up for you to reuse.

If you own a single Product ID on which you have multiple license keys then a single key can't be isolated and reset. Instead that Product ID  will be reset. All the machines on which you have the software installed with that Product ID will initiate an activation check. If they're connected to the internet this will occur in the background and you won't even notice this automatic re-activation. Any of your licenses key that are not currently "locked" on any machines will then be "freed" up and are available for reuse.

In order to resolve this error:  Please "submit a ticket" with that Product ID and your email address that you used for the purchase.

The following steps are applicable to disable automatic Rootkit scanning in Kaspersky Internet Security/Anti-Virus 2012 or any older version:

1. Open Kaspersky Console window and click on Settings.

2. Under Setting click on Scan icon.

3. Under Scan menu,  select General Settings.

4. Once you have clicked on General Settingson the right-hand side of the menu- Uncheck “Perform Regular Rootkit scan”

See the below screenshot 

5. Rootkit scanning is now disabled for Kaspersky Internet Security 2012. 

The following steps are applicable to disable automatic Rootkit scanning in Kaspersky Internet Security/Anti-Virus 2014:

  1. Open Kaspersky Internet Security 2014 Console Window.
  2. In the lower part of the window, click the Settings link. (See below screenshot)

3. Under 'Computer resources' section, uncheck  the option 'Perform rootkit scan'. (See below screenshot)

4. Rootkit scanning is now disabled for Kaspersky Internet Security 2014.

No. An uninstall deletes all snapshots.

Rollback Rx does not use a copying technology to build snapshots. The technique used (Sector Redirection) means that a snapshot cannot "survive" without Rollback Rx. Therfore, the uninstallation of Rollback Rx means that all snapshots are lost.

Please employ great care when uninstalling Rollback, as Rollback Rx will give you an opportunity to uninstall either to the current image or to a specific snapshot. Make sure you select the right one. Once Rollback Rx is uninstalled, your snapshots are gone as well.

Prior to transferring the software(i.e RollBack Rx, Drive Vaccine or Drive Cloner) onto a new system - please uninstall the software solution from the old system in order to release the license to the license server. After the un-installation, the software can be re-used onto the new system using the same Product ID

These software solutions uses the hard drive's serial number as the unique identifier for a client registration. If the software has not been uninstalled from the old system, the software installer will think that this is a new activation.

If the old machine's hard drive have unexpectedly crashed and you could not uninstall the software :

Please send your Product ID along with the email address used during the purchase to our support desk by submitting a ticket and we will reset the Product ID for the software.

We’ve all been there. Tuesday hits and Microsoft releases a slew of new Windows updates. After spending time downloading them, they sit there waiting for your approval. After a while you think, “All right. Might as well.” You click accept and the install starts. The PC then asks for a reset to finish. You accept and watch as the PC turns off and back on.

Then the screen loads up and boom –the dreaded Blue Screen of Death (BSoD).

The dreaded BSoD.
The dreaded BSoD.

Wait, what? You just downloaded an update.

What happened? Who is responsible for this?

The easy answer for some people is to blame RollBack Rx or Drive Vaccine. Why? Because our software is designed to instantly get people out of disasters. In their minds, this counts as a disaster and therefore the software should be able to get out of it. Fairly enough, our software does allow the user to load up an older snapshot with RollBack Rx, or load into the “LGK” (Last Good Known) image on Drive Vaccine, erasing the mistake most of the time. But there have been some updates where even RollBack Rx and Drive Vaccine weren’t able to get out. The reason is Windows was so heavily altered that it effectively removed, blocked, or deleted our subconsole system. RollBack Rx and Drive Vaccine are good – very good – but there’s nothing that can withstand deep rooted changes of the entire OS.

In response to this our software by default now only downloads Windows updates, but does not install them. It opens the door for the user to proceed, but it’s up to each individual whether or not to step in right away, or wait for the all clear by our team (announced in this forum thread here: http://bit.ly/113jHvh).

When something went wrong with our software

That’s not to put all the blame on Microsoft, as there have been moments where our software was at fault. It doesn’t happen often, but there’s a surefire way to know when something went wrong with our software and when it did not. Simply enough if it was our software that was at fault, the subconsole system will simply be removed entirely.

In this case the best course of action would be to go to support.horizondatasys.com and Submit a Ticket. If possible, once back into the machine, navigate to Program Files --> Shield and attach these four files to the ticket (preferably merged into one zip file): 128.dat, shield.dat, subconsole.log, setup.log.

Navigate to Program Files --> Shield to locate these files.
Navigate to Program Files --> Shield to locate these files.

In the ticket description box please define what OS you’re using, what build number of RollBack Rx or Drive Vaccine you’re running (which can be found by navigating to the About menu), and define the steps you took before the issue occurred. The more information provided the better. A technician will review the ticket and respond within 48 business hours.

When the software is not at fault

Let’s say the BSoD happened.

You reset the PC, press the ‘HOME’ key and boot into the subconsole menu for either RollBack Rx or Drive Vaccine. If you can enter into this subconsole after a Windows update, then our software is still in tact. Even if a snapshot cannot be loaded, or the “LGK” in Drive Vaccine cannot load, then this is due to the Windows update itself and not the software being ineffective.

This is why the software team here at Horizon DataSys cannot stress enough how important it is to follow our Windows updates thread here on our community forum. From there all announcements are made first in regards to updates.

We also share our information through our Facebook page (www.facebook.com/horizondatasys) and our Twitter @HorizonDataSys.

Information is power!

In order to resolve certain technical issues with the installation process or otherwise , it is necessary to retrieve 'log files' of RollBack Rx.

After you log into the Windows, please collect the following 3 files from:

C:\Program Files (x86)\Shield [32-bit machine]

                            OR

C:\Program Files\Shield [64-bit machine]

and attach them in your Support ticket:

1. setup.log
2. subconsole.log
3. 128.dat
4. shield.dat or shield.dat.bak

FYI: Strongly suggest you compress the four log files before attaching it to your support ticket.

If you require further assistance, contact Horizon DataSys Support: "Submit a Ticket". 

 

Did you forget the password to the RollBack Rx console?  This is only applicable to RollBack Rx v10.x

To recovery password, please follow the below steps on RollBack Rx:

1. During the sub-console password prompt of the RollBack Rx: (Below is screenshot of what it should look like) 

 

 

2. The next step is to press: 'Alt-F1' simultaneously - If done correctly, RollBack Rx will provide an encrypted string: (Such as below)

 

 

3. The next step is to "Submit a ticket" along with the encrypted string retrieved from RollBack Rx, the email address used during the purchase and the Product ID and Order information for verification.

 

Once the ticket is submitted, the technical support will verify the information and provide you the password for the RollBack Rx console.

The following steps are applicable to disable automatic Rootkit scan on Avast Internet Security:

1. Open Avast's main menu

2. Click on Settings > Troubleshooting tab

3. Uncheck "Enable rootkit scan on system startup" (See below screenshot)

The following steps are applicable to disable automatic Rootkit scanning in Norton Internet Security 2014:

  1. Open Norton Internet Security 2014 Console Window.

  2. Click on "Performance" tab. (See below screenshot)



  3. Click on "Settings" tab. (See below screenshot)





  4. Click on "Computer Scan" tab. (See below screenshot)





  5. Now on the right side of the console, you will notice the option "Rootkits and Stealth Items Scan". (See below screenshot)





  6. Click on the option "Rootkits and Stealth Items Scan" to toogle it to 'Off' the scan. (See below screenshot)





  7. Next, click "Apply" and then click "OK" to finalize the changes. The Rootkit Scan is now switched off. 

NOTE: This guide is applicable to Windows 7, 8, 8.1 and 10 users.

On certain occassions some users may find the defaultly implemented scheduled task to take a snapshot at the first boot of the day is not functioning. More often than not this is not a bug, and the most common cause is due to Windows' Fast Boot feature being enabled, also known as Fast Startup on certain operating systems.

As the name implies Fast Boot/Startup helps your PC start up faster after shutdown. It accomplishes this by not fully shutting down the system and keeping certain pieces of data in a sleep state rather than powered down. While this feature is enabled, the next time the system is loaded up RollBack Rx will not take this as the "first boot of the day", thus not triggering the function. Unfortunately, programs are very literal.

To resolve this issue please disable Fast Boot/Startup on your PC. To do so, please follow these steps.

1. Right-click on the Start button and select Control Panel. In the search bar, please copy this string: Control Panel\Hardware and Sound\Power Options\System Settings

2. Click on the Change settings that are currently unavailable option at the top.

3. Under Shutdown settings locate the checkbox which states 'Turn on fast startup'. You will want to uncheck that option. Please be sure to also disable the Hibernate feature. Once this is done please click on the Save changes button to save your settings.



Congratulations! You have now disabled Fast Startup and RollBack Rx should work as intended.

However, should the issue persist please contact our Technical Support team by submitting a ticket.

NOTEIf the Turn on fast startup setting is not listed, then Hibernate has been disabled as well as Fast Startup.

RollBack Rx Professional and Home Edition as well as Drive Vaccine and Reboot Restore Rx are all compatible with cloud-based applications such as Dropbox and Google Drive.

Our programs work by protecting the harddrive on the local level. Cloud-based applications are entirely structured around offshoring data onto an external server, most commonly at these companies’ sites.

Any restore done by our program will strictly be to refresh data, drivers, registry entries, etc., only found on the local drive. Therefore any data uploaded to the cloud will be untouched.

RollBack Rx Professional Deployment Whitepaper (for version 10.x and up)
(please see attached for version 9.x)

 

Five Ways to Deploy RollBack Rx Professional

RollBack Rx Professional is designed with enterprise requirements in mind. To meet the demand of various scale enterprise clients, RollBack Rx Professional provides five deployment methods ranging from individual workstation setup to company wide deployment.

1. Single Setup: Install RollBack Rx Professional on individual workstations with the setup CD or electronic download.

2. Network Setup: Install RollBack Rx Professional from a network share folder with pre-configured program settings, or using a network software deployment tool to distribute RollBack Rx Professional.

3. Script Setup or Unattended Setup: Push out RollBack Rx Professional with a client script which runs automatically when the client PCs log onto the network.

4. Deploy RollBack Rx Professional In a System Image: Include RollBack Rx Professional in a system image and roll it out with the operating system deployment using a drive imaging utility such as Symantec’s Norton Ghost.

5. Create and Deploy Using an MSI: Install RollBack Rx Professional with an MSI executable using preconfigured settings.

 

Single Setup

To install RollBack Rx Professional on individual workstations, follow these typical setup procedures:

1. Unzip the installer package.

2. Go to folder “Rollbackv1(x)” and run setup.

3. Select Typical or Custom Setup at the setup selection menu and follow the on-screen instructions.


Network Setup

If you need to setup RollBack Rx Professional on multiple PCs on a network, to eliminate the hassle of carrying a CD around to setup each PC, RollBack Rx Professional allows you to run the setup from a network share. Follow these general guidelines to install RollBack Rx Professional over the network:

1. Copy all RollBack Rx Professional files from the extracted zip files into a folder on your server and create a share for the folder.

2. Create a Setup INI File (SETUP.INI) with the SETUP INI Wizard utility provided in the Deployment Tools folder of the RollBack Rx Professional installer package. Place the SETUP.INI file into the folder containing RollBack Rx Professional program files created in Step 1.

3. Open the SETUP.INI file in Notepad, scroll down to [Advanced.Partition], delete all lines underneath it and write in “ProtectDrives=systemonly” to have the SETUP.INI file protect the C: drive, or enter “ProtectDrives=all” to cover all drives. This is important, as when the INI file is created it will read the drive it was created on, including specific information related to that drive. By editing in either of these lines it ensures deployment onto any other drive will be successful.

4. To install RollBack Rx Professional on a workstation, access the shared folder from the workstation and run Setup.exe

5. Select “Unattended Setup” option at the setup selection menu. Unattended Setup will read-in the setup parameters (such as product ID, password, protection type, program settings and installation directory) from the SETUP.INI file that has been configured in Step 2 above. At the end of the setup the user will be asked to restart the computer.

If you use a network software deployment tool such as Microsoft SMS server, Novell ZENworks, etc., to deploy our software, please follow these guidelines:

1. Create a BEFORE snapshot of the system with the software deployment application.

2. Create a folder called Setup on the root of the C drive and copy all of the RollBack Rx Professional program files into the folder.

3. Create a SETUP.INI file as aforementioned in Step 2.

4. Place SetAutoSetup.exe (which can be found in the Deployment Tools folder on the installer package) into the Setup folder and double click to run it. SetAutoSetup.exe will write some deployment settings into the system registry.

5. Run the software deployment application again to create an AFTER snapshot and create the software deployment package.

6. Deploy the software package and reboot the client system.

 

Setup with Scripts (Unattended Setup)

For some network administrators who prefer to use client side scripts to deploy new applications to workstations, RollBack Rx Professional can also be easily integrated into their custom scripting install scenario. Follow these general guidelines to deploy RollBack Rx Professional within a network script:

1. Copy RollBack Rx Professional files from the installer package into a folder on your server and create a network share for the folder.

2. Create a Setup INI File (SETUP.INI) with the SETUP INI Wizard utility provided in the Deployment Tools folder of the RollBack Rx Professional installer package. Place the SETUP.INI file into the folder with the RollBack Rx Professional program files created in Step 1.

3. To use a client side script to install RollBack Rx Professional when clients log on, include “setup.exe /s” within the setup script. Setup /s allows RollBack Rx Professional setup wizard to silently read-in the setup parameter from the SETUP.INI file configured in Step 2.

4. Open the SETUP.INI file in Notepad, scroll down to [Advanced.Partition], delete the lines underneath it and write in “ProtectDrives=systemonly” to have the SETUP.INI file protect the C: drive, or enter “ProtectDrives=all” to cover all drives. This is important, as when the INI file is created it will read the drive it was created on, including specific information related to that drive. By editing in either of these lines it ensures deployment onto any other drive will be successful.

5. Please test the installation file and ensure it works as intended by running an installation with the SETUP.INI file.

No user intervention is required during the silent setup. Setup will restart the computer automatically at the end. If you do not wish to restart the computer automatically at the end of the setup, add “/norestart” to the “setup.exe /s” command.

 

Deploy RollBack Rx Professional In a System Image

RollBack Rx Professional can also be included in a system image and rolled out with the operating system deployment, such as one created with Norton Ghost or a similar utility. However, due to RollBack Rx Professional’ security design, some of the program’s features do not exist in a visible file format. Instead they exist as bits and bytes on the physical sectors of the hard drive. Therefore the typical Ghost approach of imaging all files on the hard drive to create a system image will not be able to include all RollBack Rx Professional components. Please follow these guidelines to prepare a hard disk for imaging including RollBack Rx Professional:

1. Copy RollBack Rx Professional program files from the installer package into a folder on the hard disk that you will use to create the system image (master image). Rename the folder as Setup.

2. Create an Advanced Setup Configuration File (SETUP.INI) with the SETUP.INI Wizard utility provided in the Deployment Tools folder of the installer package. Place the SETUP.INI file into the setup folder created in Step 1.

3. Open the SETUP.INI file in Notepad, scroll down to [Advanced.Partition], delete the lines underneath it and write in “ProtectDrives=systemonly” to have the SETUP.INI file protect the C: drive, or enter “ProtectDrives=all” to cover all drives. This is important, as when the INI file is created it will read the drive it was created on, including specific information related to that drive. By editing in either of these lines it ensures deployment onto any other drive will be successful.

4. Place the SetAutoSetup.exe utility, provided in the Deployment Tools folder of the installer package, into the Setup folder and double click to run it. SetAutoSetup.exe will write some deployment settings into the system registry.

5. Now the hard disk is ready for imaging. Image the drive with a Windows based imaging application or reboot the PC to a CD to create an image of this hard disk containing RollBack Rx Professional setup files. DO NOT reboot into Windows after running SetAutoSetup.exe which had created some registry entries to automatically start the RollBack Rx Professional deployment process, rebooting into Windows will kick off the RollBack Rx Professional auto-setup process.

The master image contains the RollBack Rx Professional deployment package rather than the already-installed RollBack Rx Professional program. Once the master image is dumped onto a hard disk, at the first startup, SetAutoSetup.exe generated registry entries will trigger the RollBack Rx Professional deployment process. This process is silent and transparent to the users. Setup reads in the program parameters from the SETUP.INI file configured in the previous step without any user interaction. At the end of the setup, SetAutoSetup.exe will automatically remove the RollBack Rx Professional setup files and restart the system.


MSI Deployment

If the best option for you and/or your organization is to create and deploy using an MSI file, then please click on the following links for a full set of instructions.

You will need to download the MSI creation tool, AppDeploy, by clicking on this link

Please follow this link for full instructions on creation and deployment of an MSI package: http://support.horizondatasys.com/Troubleshooter/Step/View/7

NOTE: Be sure to follow this guide's System Image Setup.INI file creation instructions for use of the ini file in the MSI package.


Contact Us

If you encounter any issues or have additional questions please contact our support team at http://support.horizondatasys.com and Submit a Ticket.

 

Once in a while you’ll come across a point where an installer for a specific program is taking a while to complete. You will first want to make sure whether you can replicate the issue without Rollback Rx installed. If there are no delays without Rollback Rx, then the most likely reason is due to the inability to create a system restore point when Rollback is installed.

Rollback Rx will sometimes lock the hard drive on certain machines and can prevent any third party applications from creating a system restore point.

A simple work around is to release the “Lock” that Rollback Rx has on the drive by going into the command prompt and entering  the following in the command prompt:

Shdcmd.exe /defrag /enable /u Administrator /p password

This will temporarily release the “Lock” on the hard drive and will allow your installer to create a system restore point. Keep in mind that, although this command switch includes the word defrag, there is no relation to windows defragmentation or the Rollback Rx snapshot defrag.

An important thing to note is that this is a temporary window. Once you restart the machine, Rollback will once again regain control of your hard drive and can prevent your installer from creating a system restore point.  

If you have created a snapshot after using defrag command, you may see an increase in the snapshot size as Rollback Rx will need to capture the system restore point as well as any action done by the third party installer.

If you have any other questions, please contact us via chat or create a ticket.

When you go to install our software, you may encounter an error message "Open Protect Sys Failed". This error message may appear when installing RollBack Rx Pro, RollBack Rx Home Edition, Reboot Restore Rx Pro, and Reboot Restore Rx.

Reason

This error message occurs when the two components of the software, the Windows Client and the Subconsole, are unable to communicate. When this happens, this is due to a 3rd party program or service, or Windows own proprietary services. In this guide, we'll detail what services may cause this error and how to best resolve this issue.

Drive Encryption

You may be using drive encryption to protect your data from unauthorized access. A feature of RollBack Rx and Reboot Restore Rx is that it will encrypt drives and data from unauthorized access. Windows, however, will only allow for one Drive Encryption service to be active. So if you have any drive encryption services active, this will often conflict with the installation of our software, which will often result in the "Open Protect Sys Failed" error message.

The most common of these is the Windows proprietary service, BitLocker. BitLocker has been included in Windows 7, 8.1, and 10. With Windows 7, it's only available in the Enterprise Edition; with Windows 8.1 and 10 it's available in every edition but the Home Edition. It's also worth noting that all Surface Pro tablets come with BitLocker enabled.

NOTE: If you are unsure if you are using BitLocker, you can check Disk Management to determine if it's active.

The process for disabling BitLocker for each OS varies slightly.

Windows 7

1) Open Control Panel; select System and Security.
2) Select BitLocker Drive Encryption.
4) Select Turn off BitLocker
5) A prompt will appear, choose Decrypt Drive to confirm.

Windows 8.1

1) Open Control Panel; select System and Security.
2) Select BitLocker Drive Encryption.
3) You will need to unlock your C: drive and any other drives you wish to cover with the software. Select Unlock drive and enter the password and select Unlock.
4) An option should then become available to Turn off BitLocker, select that.
5) A prompt will appear, once again choose to Turn off BitLocker to confirm.

Windows 10

1) Open Windows Explorer, navigate to My PC.
2) Right-Click on Local Disk (C:) and select Turn On BitLocker.
3) Follow the steps for activation, you will be provided with a BitLocker key. You will need that. We recommend saving it in a word document or to a USB following the instructions provided.
4) Once active, open Windows Explorer again and once again navigate to My PC.
5) Right-Click on Local Disk (C:) and select Turn Off BitLocker.

NOTE: Some builds of Windows 10 will instead list Manage BitLocker, click that and then choose to Turn Off BitLocker.

It is important with Windows 10 to follow these steps as Bitlocker may appear off, but it is in fact partially active. Fully activating and fully disabling will remove BitLocker entirely.

For 3rd party Drive Encryption services, please consult with the software's developers and their User Guides when applicable for disabling or uninstalling.

Anti-Virus Programs

Some Anti-Virus tools will flag the installer for our software as a false positive, which can in some cases result in the "Open Protect Sys Failed" error message.

Disabling the Anti-Virus temporarily during installation will ensure that it's not causing this issue. Please consult with your 3rd party Anti-Virus developer if you require assistance with disabling the program. With the variety of similar tools, it may also be that you have other security software that protects your machine from Malware and Ransomware which may also be similarly falsely flagging our software.

Windows 10 comes with a proprietary Anti-Virus tool called Windows Defender which comes pre-enabled. To disable Windows Defender:

1) Open Settings.
2) Click on Update & Security.
3) Click on Windows Defender.
4) Turn off the toggle switch for Real-time protection.

Once the installation of the software is complete, you can re-enable your Anti-Virus program.

Other Causes

In most cases, disabling Drive Encryption and Anti-Virus tools will correct the issue. There are some other small considerations to be taken into account.

If you compress your hard drives, you'll simply need to decompress them.

Any USB Flash Drives or External Hard Drives should be removed from the machine prior to installation.

Should the issue persist after following the steps in this guide, please contact our Technical Support team by submitting a ticket.

RollBack Rx Professional Edition (v11.1) and RollBack Rx Home Edition (v11.1) have changed the way the software handles Baseline Management.

Previously you would have to update your Baseline or restore to it from the Baseline Manager, but Version 11.1 streamlines the Baseline Management process.

Here's how you update your Baseline for either RollBack Rx Home Edition or RollBack Rx Professional Edition (v11.1 and higher)

1) Open up the program and navigate to your Snapshots.

2) Unlock your current Baseline by right-clicking on it and selecting 'Unlock'.

NOTE: By default, your Baseline will be labeled as 'Installation'.



3) Once unlocked, right-click again and delete the snapshot

IMPORTANT: Deleting a snapshot will also delete any and all data contained within that snapshot!

4) Your next snapshot chronologically will become the new Baseline! If there are multiple snapshots before the snapshot that you'd like as your new Baseline, you'll need to delete them as well so that the snapshot that you'd like as your Baseline is the first snapshot chronologically.



IMPORTANT: Deleted snapshots may not immediately reflect free disk space. Run the snapshot defragmenter after deleting snapshots to consolidate and reclaim disk space.

For any questions and/or comments about RollBack Rx Professional Edition, please Submit A Ticket and a Senior Technician will respond to you within 24 business hours. For any questions/comments about RollBack Rx Home Edition, please post on the Community Forum.

Every engineer faces a similar philosophical challenge when designing a product, no matter the product is a car or a software. For example, to make a car go faster, you need a more powerful engine but more powerful engine consumes more fuel. To save fuel, you need to make the engine smaller but smaller engine produces less power. Therefore, better engine design is the one that improves the balance of these opposing factors. The same thing for the Rollback Rx design, there are opposing factors of restoring speed and disk space consumption.

The new Rollback Rx kernel design gives us the best of both worlds: Fast Restore Mode and Space Saving Mode. When you are in the Fast Restore Mode, The kernel drivers give priority to restore speed. It utilizes as much disk cache as possible and it simplifies as much disk IO as it can. While in the Space Saving Mode, the kernel drivers give priority to disk space consumption and system stability. It uses less disk cache and focuses on disk IO stability as the priority.

More importantly, you can switch between the modes seamlessly.

 Rollback Rx will automatically switch the kernel to the Fast Restore Mode when you are restoring a snapshot.

You can manually switch from Fast Restore Mode to Space Saving Mode or you can configure program settings to automatically switch to Space Saving Mode when creating a new snapshot or if the system has not been restored in X amount of time.

 

If you have any questions please let us know.

RollBack Rx Pro and Reboot Restore Rx Pro were recently updated to Version 11, which now allows for Windows 10 Feature Updates (formerly known as Creator Updates) to be installed without any negative effects for your machines. Each program will temporarily disable select elements of the software while the updates are running. This prevents the machine from changing the infrastructure of Windows 10 while affecting our software in a negative way.

First off, you will need to be using Version 11. If you're using an older version of the software and need to upgrade to Version 11, please contact our sales team. You can ask your Sr. Account Executive; or you can always email us at sales@horizondatasys.com, call us at 1-800-496-0148 option 1, submit a ticket, or chat with us using our live chat system.

Once you've installed the appropriate version, there are certain steps to follow to ensure that you are configuring the software correctly.

RollBack Rx Pro

IMPORTANT NOTE: Selecting this option for RollBack Rx Pro means that your snapshots will be deleted after the installation of a Feature Update. You will want to transfer any important data over to your current state prior to installation to avoid any unwanted data loss. 

1) Open up RollBack Rx Pro, select Tools > Settings



2) Navigate to Advanced Settings, once there, ensure that "Allow install of Windows Updates that cannot be rolled back" is checked.





Reboot Restore Rx Pro

1) Open up Reboot Restore Rx Pro and navigate to Tools & Settings and then click on Settings.

2) Navigate to Program Settings, once there, ensure that the 'Allow install of Windows Updates that cannot be rolled back'

NOTE: With both programs these settings can be changed from the Endpoint Manager, you can also preconfigure these settings using our various Deployment methods.

For any further questions and/or comments about Windows Updates, RollBack Rx Pro or Reboot Restore Rx Pro; please Submit a Ticket and a Senior Technician will respond to you within 24 business hours.

 

RollBack Rx is licensed per PC.  For Home & End-point users, you would need a license (PRODUCT ID) for each PC that you would like to have RollBack Rx installed onto.

Horizon DataSys has introduced 5 types of Home license packs. Each offering a discount based on license pack selected.  When ordering online - the customer will receive multiple PRODUCT ID's based on the license pack purchased. To view these home license packs visit: http://www.horizondatasys.com/