- Documentation
- Getting Started
Windows Server patching in maintenance windows
Windows Server patching in maintenance windows
WuInstall runs the update operation; your scheduler or management platform decides when and where it starts. Plan application downtime, backups and a pilot group before rolling out to production servers.
Audit before the window
Create the log directory and run this in an elevated command prompt on a test server:
wuinstall /search /logfile "C:\Logs\wuinstall-search.txt"
Check the configured update source and review the selection. If you add filters, use the same filters in the later installation. A search result can change when approvals or available updates change.
Install and handle restarts deliberately
The following command installs applicable updates and requests a restart only when an update installed in this run requires it. It can interrupt services; use it only in your approved window:
wuinstall /install /reboot_if_needed /logfile "C:\Logs\wuinstall-install.txt"
A restart already pending before the run does not itself trigger this switch. For multiple passes, review reboot-cycle behavior before enabling it. A runtime limit is not a guarantee that Windows servicing and a reboot will finish before your window ends.
Verify service recovery
Collect the return code, logs and a new search after reboot. Check application health separately. Expand the rollout only after the pilot behaves as expected. XEOX can complement these local operations with centrally managed jobs and fleet visibility.
Next step
Evaluate the workflow on a test machine first. Start a 30-day trial or request a quote.