Skip to main content
All CollectionsRemote Monitoring & Management
Identifying assets that require a reboot
Identifying assets that require a reboot

See which assets may require a reboot to ensure that patches are always thoroughly installed on your client's endpoints.

Updated over a year ago

An asset may need rebooting for various reasons, one of the most common being critical patch updates. For critical patch updates, a reboot might be needed when the patch installation is incomplete. But without visibility into which assets need rebooting and why, assets in the network may remain unprotected.

That’s why we’ve added the “Reboot Required” indicator on the assets page, which appears whenever the following conditions are met:

1. System updates may require a restart for the completion of a successful installation.

2. Some software installations mandate a restart to finalize the installation process.

3. Renaming a file that is currently in use may demand a restart to ensure smooth execution.

4. Changing the machine name typically requires a restart to apply the new name effectively.

5. Rebooting is often necessary after third-party software installation.

6. Windows components may require a reboot to fully activate changes or updates.

Click on the tools icon as shown below, and you’ll see the reboot option for the assets that require a reboot. You can also use the remote desktop tools you’ve integrated to remote in and reboot the asset.


💡SuperTip: When you hover over the icon that is marked with the exclamation point (!), you will be able to see the reasons for which the reboot is required.


You can also filter the assets that require a reboot and bulk-select them to start the reboot process, as shown below.

If the following conditions are true, then the reboot indication is triggered.

Key

Value

Condition

Module

HKLM:\SOFTWARE\Microsoft\Updates

UpdateExeVolatile

Value is anything other than 0

SOFTWARE__OR_OS_UPDATE

Key

Value

Condition

Module

HKLM:\SYSTEM\CurrentControlSet\Control\ComputerName

\ActiveComputerName

ComputerName

Value ComputerName in HKLM:\SYSTEM

\CurrentControlSet

\Control\ComputerName

\ComputerName is different

HOST_RENAME

Key

Value

Condition

Module

HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

\Auto Update\RebootRequired

NA

key exists

WINDOWS_AUTO_UPDATE

HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

\Auto Update\PostRebootReporting

NA

key exists

WINDOWS_AUTO_UPDATE

HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing

\RebootPending

NA

key exists

CBS


📝 Note: The agent “reads” only the registry values listed above and triggers the reboot indication.


Did this answer your question?