This issue affects any Rapid Recovery 6.1.x product installed on Windows 10 or Windows Server 2016 server with EFI and Secure Boot enabled.
After installer completes a windows will pop up stating "A digitally signed driver is required." After reboot of server the drivers listed in the warning will not start and cannot be started.
Example from an Agent install:
Or, after agent installation, server's reboot goes into OS repair request/loop, claiming a driver file, such as aavolflt.sys, is corrupt.
Note: sometimes, driver installation attempt may cause a Blue Screen of Death (BSoD) on machines with UEFI Secure Boot enabled.
Windows 10 and Windows Server 2016 with EFI and Secure Boot enabled is having problems with digitally signed drivers from many vendors as Windows 10 and Windows 2016 introduced a new way of signing drivers.
Rapid Recovery drivers have been submitted to Microsoft for certification and will be made available as soon as Microsoft completes the process.
Defect ID RR-101573 has been assigned to this issue.
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Certified drivers will be included in the next release of Rapid Recovery. Until then, experimental drivers are available for 6.1.x builds. Please open a service request to receive them.
NOTE: You may find the values for the registry subkeys match, in which case disabling Secure Boot should be the effective step to complete the work around.
Start Values Table:
|Registry Subkey||Value Name||Type||Value|