Free ways to push updates and force reboots
Pushing updates for free often fails because machines will not restart automatically to finish the installation. End users never restart their computers on their own, and servers frequently get stuck in a pending reboot state during scheduled maintenance windows. This forces administrators to manually trigger the reboots via RDP or remote tools just to get the updates installed.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Using free tiers of cloud endpoint patch management tools like Action1
- 2Setting local GPO or Intune update deadline policies to force reboots after a grace period
- 3Scripting updates with PowerShell using winget or Chocolatey and logging to a network share
- 4Bundling patch management through endpoint security software like ESET or Malwarebytes
- 5Baking a pre-patch reboot into the maintenance script to ensure a clean state.
- 6Running automated scripts to query the pending reboot flag and force a restart without interaction.
- 7Relying on application-level High Availability (HA) to manually reboot servers whenever needed.
- 8Configuring dual-reboot maintenance windows (one reboot before patching, one after).
- 9Executing scheduled weekly reboots regardless of patch cycles to clear any lingering states.
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“what's the best way to push updates?”source ↗
“Obviously this is a thing where users never restart their computers to complete the updates and such.”source ↗
“What's free way to do it?”source ↗
“for one reason or another some servers remain in a pending reboot state after scheduled maintenance window monthly CUs install.”source ↗
“we have those: dev, test, prod. but a lot of times servers just don't reboot after install”source ↗
“we have 4 hour maintenance windows. sometimes they do not install and have to be triggered, sometimes just stuck on reboot or sometimes .NET installs first asks for a reboot while CU stays there needing a trigger via Remote Click Tools or RDP”source ↗
Where this came up
People with this problem also raised
- 2How to update BIOS and firmware remotely across mixed device fleets
- 3How to stop accidental production deployments from policy cloning
- 2Intel extension update stuck in a reboot loop
- 3Why does software installation fail on secure systems?
- 6Why do wireless access point firmware updates keep breaking deployments?
- 3Windows Server 2019 fails to boot after cumulative update