SConfig provides an interactive way to search for and install Windows updates on Server Core without a graphical Windows Update interface. A reliable patching procedure includes preparation, the scan and installation, required restarts and application validation. Finishing the menu prompts is not the same as proving the production workload is healthy.
This guide applies to Windows Server 2019, 2022 and 2025 Server Core. Use the update source and maintenance process approved for the server. A centrally managed machine may receive update policy from Group Policy or another management system, and those controls should not be bypassed simply because a local scan offers a different result.
Review the workload and maintenance window
Identify the roles and applications affected by a restart. Check for active RDS users, database jobs, backups and business processing. Notify the appropriate owners and decide how service will be drained or paused. A server with no visible console activity can still be running important scheduled work.
Review the applicable update release notes and known issues for the installed Windows version and the required role. Do not assume that an update for one server release applies to another. If the environment has a test stage or deployment ring, complete that stage before patching the production instance.
Have verified backups and a recovery procedure appropriate to the server’s role. A database, domain controller or cluster node can require more than a generic disk restore. Know who can approve downtime and recovery if post-update validation fails.
Keep independent console access available. Patching can restart networking or the operating system and end remote sessions. Confirm the console works before the window, rather than discovering during an outage that nobody has access.
Capture the pre-update state
In elevated Windows PowerShell, record the version, build, free space and service state relevant to your application:
Get-CimInstance Win32_OperatingSystem |
Select-Object Caption, Version, BuildNumber, LastBootUpTime
Get-Volume | Select-Object DriveLetter, HealthStatus, SizeRemaining, Size
Get-HotFix | Sort-Object InstalledOn -Descending |
Select-Object -First 10 HotFixID, InstalledOn
Get-HotFix can provide useful installed-update information, but it is not a complete inventory of every package, driver or application update. Use the build number, servicing records and management platform’s reports together when establishing compliance.
Check storage headroom and resolve pending maintenance issues before installation. Do not delete servicing folders or backup data indiscriminately to create room. Determine why capacity is low and use supported cleanup or expansion procedures.
Open SConfig and review effective settings
Sign in through the console or approved Remote Desktop administrative session and run:
SConfig
Windows Server 2022 and 2025 Core normally start SConfig automatically after sign-in; Windows Server 2019 commonly requires launching it manually. Use the displayed labels because menu presentation can differ across releases.
Review Update Settings and the organization’s patching policy. Automatic, download-only and manual modes change future behaviour, not just the current installation. Do not permanently switch a managed server to manual as an incidental step and leave no owner responsible for future patching.
On Core, graphical notifications such as Action Center are not available as a dependable reminder. Download-only mode needs an explicit operational process that notices available updates, schedules installation and follows up on required restarts.
Search for and install approved updates
- Choose Download and Install Updates. Read the menu label on the actual server rather than relying on an old screenshot’s option number.
- Select the appropriate search category. Use the options shown for all applicable or recommended updates according to your policy. A scan uses the configured update source and does not automatically change that source.
- Review the returned list. Compare update identifiers and descriptions with the approved maintenance scope. An optional component, driver or major version offer requires its own decision.
- Select the approved updates. Follow the prompts to download and install them. Do not repeatedly interrupt an apparently slow servicing operation without checking its state.
- Record the outcome. Capture any failed update identifier, error code and message, as well as the time. This is more useful than reporting only that Windows Update failed.
- Handle restart prompts deliberately. Confirm user work and dependent services are ready, then allow the required restart within the agreed window.
Do not mistake an upgrade to a newer Windows Server release for an ordinary monthly quality update. Moving from 2019 or 2022 to 2025 needs its own compatibility, licensing and recovery review. The update menu should not become an accidental operating-system migration plan.
Validate after every required restart
Allow the server time to complete servicing at boot. Reconnect through the approved route and check the operating-system build and last startup time again:
Get-CimInstance Win32_OperatingSystem |
Select-Object Caption, Version, BuildNumber, LastBootUpTime
Get-Service | Where-Object Status -eq 'Stopped' |
Select-Object Name, DisplayName
The stopped-service list is not itself an error report; many services are deliberately stopped or start on demand. Compare the application’s required services with the documented baseline instead of starting everything indiscriminately.
Run a second scan when the process calls for it. Some updates or prerequisites become applicable only after installation and restart. Confirm the remaining results against policy rather than assuming that an empty list from one source proves universal patch compliance.
Test the actual role from a representative client. For an RDS application, verify ordinary user sign-in and a meaningful application workflow. For a DNS or file server, test resolution or access from another machine. Local service status alone does not validate client access.
Inspect failures before changing components
The scan finds no updates: confirm the configured source, product approval and policy. A WSUS-managed server can legitimately see a different set of approved updates than a server using Microsoft’s public service.
Download fails: check DNS, proxy settings, network access and the configured update service. Do not disable TLS or firewall controls broadly. Record whether other servers using the same source are affected.
Installation fails repeatedly: preserve the update identifier and error, check free space and review servicing logs. The CBS log and WindowsUpdateClient operational events can provide context. Avoid deleting update caches or resetting services as an automatic first step.
The server boots but the application fails: compare the application’s logs, dependencies and update known issues. Establish whether the problem is an actual regression or a delayed service, changed policy or unrelated capacity problem before removing updates.
Plan recovery without unsupported shortcuts
Not every update can be uninstalled, and some servicing changes have role-specific recovery implications. Use the documented method for the particular update and operating system when uninstall is supported. Do not publish a blanket command that removes the newest package from any server.
If recovery requires restoring a backup or replacing the server, follow the approved application and data procedure. Preserve current business transactions where possible and have the owner validate the recovered state. A quick restore that loses recent records can create a second incident.
After recovery, decide how the update will be retested or mitigated; leaving the server indefinitely unpatched is not a completed maintenance outcome. Record the exception, owner and review date.
Close the maintenance record
Document installed updates, resulting build, restart completion, client-side tests and any remaining actions. Confirm monitoring and backup schedules are active, and ensure temporary access or maintenance exceptions are removed. Keep the chosen ongoing update mode consistent with the team’s process.
For future update behaviour, see configuring SConfig update settings. For recovery planning, read the backup and restore guide. Microsoft’s SConfig documentation explains the supported menu workflow.