Apply Windows Server updates through a maintenance plan that includes recovery access and application checks. This procedure covers routine quality and security updates; an operating-system version upgrade needs a separate compatibility and migration decision.
IN THIS ARTICLE
01 Prepare the maintenance window
Record the Windows version, applications, database services and any cluster or high-availability role. Check the current backup and the method needed to recover the server. Confirm provider-console access and identify who can approve a restart.
Review the update's current Microsoft information and your application's support requirements. For a managed update environment, follow its policy and deployment rings instead of bypassing its update source. Plan customer communication around the actual expected interruption.
02 Install and restart deliberately
- Check available disk space and whether an earlier update already requires a restart. Resolve an incomplete maintenance state before beginning an unrelated change.
- On Desktop Experience, open Windows Update in Settings or use the organisation's approved update console. On Server Core, sign in through the console or RDP and run
SConfig. - In SConfig, choose 6, Install updates, and search the intended quality-update category. Review the returned list before choosing all or selected updates.
- Allow the installation to finish and record any failed update or error. Do not power off the server merely because an installation stage is taking longer than expected.
- When a restart is required, drain or stop workloads according to their own procedure and restart during the approved window. Clustered systems require their cluster-aware maintenance workflow.
- After sign-in is available again, confirm the installed update state and check whether another restart or follow-up update remains.
03 Verify the hosted services
Test the website, application login, database connection, scheduled jobs and remote administration that matter for this server. Review new System and Application events. A successful Windows login alone does not establish that the hosted application recovered.
Common questions
Can I run SConfig inside a remote PowerShell session?
Microsoft documents SConfig for local or Remote Desktop sign-in, not a remote PowerShell session. Use the supported management tool for that connection method.
Should automatic updates be disabled permanently to avoid restarts?
Set a controlled update policy with a responsible operator and maintenance schedule. Leaving a server without an active patching process creates a growing maintenance gap.