Windows devices restarting unexpectedly after Hexnode patch automationSolved

Hi @harold,

This can happen if the Windows patch automation has restart-related options enabled, even if the device appears to be fully patched.

Check the patch automation applied to the affected Windows devices:

1. On the Hexnode UEM portal, navigate to Patches > Automations > Windows.
2. Open the automation targeting the affected devices.
3. Review the device-end notification settings for restart prompts.
4. Check whether a restart notification with a postpone limit is configured.
5. Check whether Configure or override maintenance window is enabled.

If restart notifications and maintenance window override options are enabled, the automation can notify users about a pending restart and eventually lead to a forced restart depending on the configured behavior. The actual reboot is performed by Windows, but the automation can influence when the restart requirement is presented or enforced.

For environments where users must not be interrupted during working hours, remove the forced restart configuration and avoid using the maintenance window override unless the update is critical. Allow users to restart manually after updates are installed.

It is also worth checking whether multiple patch automations target the same Windows device group. If different time zone or shift-based automations apply to the same devices, separate the devices into dedicated groups and apply the relevant automation to each group only.

Regards,
Sienna Carter
Hexnode UEM

We removed the restart notification and the maintenance window override from the automation, but some users still saw the same restart popup later. Does that mean the policy change did not apply?

Hi @harold,

If the earlier patch automation had already staged an update or scheduled a restart prompt before the policy was changed, the device may continue to show that pending prompt for the current update cycle.

The updated automation settings apply during the next policy sync and future patch automation runs. Any already-staged Windows Update reboot requirement may remain until Windows clears it, usually after the device completes the pending restart.

In this situation, allow the updated policy to sync across the fleet and have users manually restart once to complete any pending Windows Update reboot. After that, the devices should no longer receive new forced restart prompts from the removed automation settings.

Regards,
Sienna Carter
Hexnode UEM