What's new 
I’m testing Auto Patch on a Windows pilot device and ran into two related issues.
Several app update tasks, including browsers and utilities deployed through winget, stayed in In progress for a long time. The Hexnode agent itself looked healthy because actions like Scan Device and Scan for Updates completed quickly. Winget was also working manually from the device, and the same packages updated successfully when run locally.
After the device restarted, one of the pending app updates completed, so it looks like the installer was waiting because the application was open and files were locked.
The bigger concern is reboot timing. We have the App Updates policy set to run Outside of device’s Active Hours, but a third-party app update completed during working hours and triggered a 5-minute restart countdown. There was no separate restart action configured in the automation.
I’m trying to understand:
1. Can Auto Patch stay in progress while the app is open?
2. Does “Outside of device’s Active Hours” control only the installation, or the reboot too?
3. Where do we configure a fixed maintenance window for app patches?
4. Does the Windows Update Experience policy control reboots from app patches?
14 Views
