-
Title
How Rapid Recovery checks for a pending reboot prior to installation -
Description
This article provide you with the registry keys that the core installer will check while the core installation or update is starting. For instance, if several Core servers need to be upgraded, you can do it with an script but it would fails due to a previous reboot is pending. -
Cause
Using script to upgrade multiples core servers may fail while it is checking if there is a pending server reboot. -
Resolution
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.
Rapid Recovery installation check for 2 registry keys:
The following registry key is related to Rapid Recovery in terms of previous installation options – if it was done with no reboot flag and you try another upgrade with the same option installer wouldn’t allow upgrade.
[HKEY_LOCAL_MACHINE] or [HKEY_CURRENT_USER ] (depends on how upgrade was initiated) - Software\Microsoft\Windows\CurrentVersion\RunOnce - AppRecoveryRebootFlag
And
This second one is windows updates that require reboot.
[HKEY_LOCAL_MACHINE]\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
In both cases we strongly recommend to reboot the system and not try to change any flags manually since we can’t guarantee that everything will work fine after the change.