Rollback RX v11.x (Home & Professional)

I keep System Restore, Drives Defrag, Fast Startup disabled with Eazy Fix installed on the system.

1. Windows Boot Optimization Function - I'll exclude this optimization in the system maintenance software.

2. Disabling outdated table of MS-DOS files format - I'll run the optimization for it.

Thank you @TheRollbackFrog for your support and time.

 

Why disabling fast startup?

 

Eazy Fix help files

Scheduled task for take snapshot at 1st bootup of the day does not work

If you setup Eazy Fix using the Typical Setup option, you will see there is a scheduled task for "take snapshot at 1st bootup of the day" after setup. But you notice this scheduled task does not appear to be working, no snapshots are created.

You probably have a Windows 10 system.
On Windows 10 system, there is a feature called "Fast Startup" which is supposed to make the system bootup faster after shutdown. Basically what Windows did is changing Shutdown to Hibernation. When you shutdown a Windows 10 system with this feature enabled (which is enabled by default), Windows is actually hibernating. So when you bootup the system, the system is resuming from hibernation.

Eazy Fix does NOT take snapshots when the system is resuming from hibernation.
That's because what Eazy Fix snapshots is the content of hard drive. When a system hibernates, it stores data in files (hibernation file) and in the memory, not everything is saved in the hard drive. Taking a snapshot of system resuming from hibernation will not guarantee the quality of the snapshot.

In this case, to make the "take snapshot at 1st bootup of the day" scheduled task to work, you need to disable the Fast startup option: https://www.windowscentral.com/how-disable-windows-10-fast-startup
Or you can Restart the system sometime during a day. In Windows 10, Restart is still a restart, not hibernation.
So new snapshot will be taken during restart.

 

I have all of thoose things inactivated or removed and with a customized install. So i guess this does not apply to me, if i got it right.

 

It seems the latest Windows cumulative update affects the EFI. I got an "EFI error" on boot.

I uninstalled Eazy Fix through boot console to the snapshot before Windows Update, tried to fix boot with Macrium bootable USB, it repaired two issues & mentioned to run chkdsk, chkdsk gave the error, write-protected. I used Win 10 Installation USB, tried Startup Repair, it fixed the boot issue.

Reinstalled Eazy Fix, restarted the system, and got the same EFI error. Followed the mentioned steps again & fixed it.
chkdsk didn't find any errors.
sfc /scannow repaired the detected corruptions.
Can I reinstall Eazy Fix now?

 

I reinstalled Eazy Fix & worked fine.

 

@TheRollbackFrog

Is it required to restart the system after turning off Eazy Fix or Rollback Rx protection to update Windows?

 

@khanyash - it's not required just for a Windows update, it would only be necessary if your RB/EAZ protected disk is an SSD. The only issue after deactivation/un-installation of your software deals with the special disk driver software used by RB/EAZ. Although the driver is removed/replaced in the System "configuration" by the deactivation process, the actual removal/replacement does not occur until the System has been reBOOTed.

Having said that, the only thing that is affected by not reBOOTing after the de-activation would be the SSD TRIM management performed by Windows. This is the function that maintains optimal use/wear of the SSD and is NOT ACTIVE (by design) while RB/EAZ is protecting your System. A lot of users who go through the deactivation/un-install process (and give up all their snapshots) usually perform most of their System maintenance functions at the same time, not just Windows updates. These functions sometimes include disk defragmentation/optimization as well as partition maintenance (increase/decrease size, etc.) and System imaging of important disks for disaster recovery (which RB/EAZ WILL NOT protect you against). If you're using an SSD, it would be important to perform an "optimization" of that volume while RB/EAZ is not running. This particular process will only work properly if your System has been reBOOTed following the deactivation of your protection.

Otherwise, no issues...

 

@TheRollbackFrog

I'm using an HDD. Thank you for the info.

 

I have a problem with version 11.2 Pro.
When I install the program then on restart it crashes on the windows boot manager (see picture). I tried to put 4 drivers from version 11.1 Pro for Win7 x64:
shdbus.sys
shield.sys
shieldm.sys
shieldf.sys
and it works. Can you tell me why? It seems like the new drivers of version 11.2 are defective.
thanks
https://i.postimg.cc/7L8bBCBC/Rollback-Rx-11-2-errore-nfo.png

 

I am also on Win7-64bit, and I also use the latest Rollback RX Pro version from March 2020. No problem here with the original drivers from this build. But I probably should mention that I have UAC turned off permanently on my machine, and this should disable the signature check for 64-bit drivers.

 

...and if there really is a SIGNATURE problem with shdbus.sys it should be reported to HDS (Horizon DataSys)... they're the only ones that can fix it.

 

If there is a problem with signature is not only for shdbus.sys
but also for these other 3 drivers:
shield.sys
shieldm.sys
shieldf.sys
that I tried one by one to replace with those of version 11.1 that are working flawless on 11.2

 

Wow. Playing with fire IMHO
Here is the size differences from RB v11.2.2705507224 (on the left) and RB v11.1.2704376597 (on the right) showing the included files that you over writ.



As you can see they are substantially bigger meaning a lot of code changes that goes together with what ever version they were written for.

I think it's dumb luck that your v11.2 of RB is working "flawlessly" with v11.1 drivers. . I would scrutinize very closely the integrity of your snapshots from now on as things could not be what they seem....

I would contact HDS tech support and send them your screen shot and let them deal with it properly.

Good Luck..... no really, good luck with tech support.

 

I have opened a ticket with them, fastly in one day reply:

"The new builds have updated digital certificates that older versions of Windows 7 do not natively support.
To make the new builds work, please make sure that you are using SP1 and the requisite KB patch for SHA2 certificates are installed.
Please check the link below for the Microsoft download links for SHA2 KB patch and SP1
https://horizondatasys.com/rollback-rx-pro-11-release-notes/#windows7

Jester Santos
Technical Support Department
Horizon DataSys Corporation"

Problem solved

 

Well that's a first..

 

...and probably a LAST

luanaTX's Windows System was either pre-SP1 (Apr 2011) or the update status of the System was over a year old. Not a good idea trying to use current software of any kind in that environment.

 

Objection, your Honour...

I was and still am using Win7 64 Pro SP1, and I always took great care to install the latest updates. These monthly updates DID NOT include the latest SHA-2 updates, and the Servicing Stack updates were also not installed. This caused update issues a little later, and I was not the only one having these issues. Luckily the fix was easily found on the Web, but for people with less Win expertise this really was a problem. Another example of the M$ incompetence when it comes to Operating System updates.

Even the very latest Win7 hotfix which repaired the black desktop background caused by the latest official Win7 update could only be installed after manual installation of the current SHA-2 update and the latest Servicing Stack update.

 

I stand corrected... (Getting beaten up by Mab )

 

HOLY COW!!! A Back To School sale HERE... unbelievable!

 

HorizonDataSys.com is offline right now.

Just temporary, or have they become a victim of the virus?
Rollback RX has not been updated since March 2020.

//EDIT//
Please disregard...
They are online again.

 

Two weeks ago HDS came out with a new build of RB-RX. Anybody tested it yet?

The changelog does only mention minor improvements for handling Windows updates. Otherwise I hope that they did not screw up things which worked in the last build from March 2020. I am a little reluctant to update because this previous build worked exceptionally well for me...

 

It's safe to use the new latest version (873, which they originally listed as 369).

I also was sure that they would stuff it up. But happy to be wrong.

 

Holy MOLY. I can't believe it.... they did it again! See HERE for details!!

 

They're comin' fast & furious now... first Black Friday, now End of Year, get 'em while they're hot!