What is WSUS? Deprecation, security and replacements
Approval control, local downloads and air-gapped networks keep WSUS in service, and Server 2016's January 12, 2027 cutoff sets the first hard deadline. This guide prices each replacement as of November 2026, maps it to clients, servers and disconnected sites, and lays out a four-step move with no patching gap.
WSUS (Windows Server Update Services) is Microsoft's on-premises update server, the Windows Server role that has decided which patches install on company networks, and when, for two decades. Microsoft stopped adding features to it in 2024 and shipped an emergency fix for a critical, actively exploited WSUS flaw in October 2025, so MSPs and in-house IT teams now have two jobs: keep the server safe while it runs, and decide what moves off it and when. This guide covers how WSUS works, what the deprecation changes, and which replacement fits which devices.
TL;DR
- WSUS (Windows Server Update Services) is a Windows Server role that downloads Microsoft updates once, lets you approve them, and serves them to your own devices.
- Microsoft deprecated WSUS in September 2024. It still ships in Windows Server 2025, still receives updates and is still supported. It gets no new features.
- WSUS has no end-of-life date of its own. It's supported for as long as the Windows Server version it runs on: until January 12, 2027 on Server 2016 and November 14, 2034 on Server 2025.
- In October 2025, Microsoft shipped an out-of-band fix for CVE-2025-59287, a critical WSUS flaw attackers exploited. Patch every WSUS server and keep ports 8530 and 8531 off the internet.
- For Windows clients, Microsoft points to Windows Autopatch and Intune. For servers, it points to Azure Update Manager.
- Configuration Manager isn't affected by the deprecation, and it still uses WSUS under the hood.
- You don't have to move everything at once. The scan source policy lets you pull one update type at a time off WSUS.
- Air-gapped networks are the one place WSUS has no like-for-like cloud replacement. Plan those separately.
What is WSUS?
WSUS stands for Windows Server Update Services. It's a server role you add to Windows Server, and its job is simple: sit between Microsoft Update and your devices.
Without it, every PC downloads its own updates from Microsoft and installs them on Microsoft's timing. With it, one server downloads each update once. You decide which updates get approved, which groups of computers get them, and by when.
Microsoft's own description puts it well: WSUS lets a company defer updates, approve them selectively, choose when they're delivered and decide which devices get them. That control is why it has lasted more than twenty years.
WSUS has no concept of tenants. An in-house IT team runs one server for its own fleet, or an upstream server with downstream servers at branch sites, while an MSP that still uses it runs a separate server inside each client's network.
How WSUS works
A WSUS setup has four moving parts:
- The upstream sync. The WSUS server connects to Microsoft Update on a schedule and pulls down update metadata, then the update files for anything you approve. In a bigger network, one upstream server syncs with Microsoft and downstream servers sync from it.
- Computer groups. Devices land in "Unassigned Computers" when they first check in. You sort them into groups that match your deployment rings, either by hand in the console (server-side targeting) or through Group Policy (client-side targeting).
- Approvals and deadlines. You approve an update for a group, optionally with an installation deadline. Automatic approval rules can do this for you after each sync.
- Group Policy on the clients. Two settings point each device at your server: Configure Automatic Updates and Specify intranet Microsoft update service location. The defaults are port 8530 for HTTP and 8531 for HTTPS.
Behind all of it sits a database. WSUS installs Windows Internal Database (WID) by default, or you can point it at SQL Server.
The client-side policy has a third box, Set the alternate download server. Fill it in and devices still scan and report to WSUS but pull the update files from that server instead, which keeps large downloads on a branch office's local link. Each of these settings lives in a Group Policy object, and our Group Policy Editor guide shows where to find them and how to force a refresh.
If you've ever had to grab a single KB by hand for a machine that WSUS couldn't reach, you've probably also used the Microsoft Update Catalog. WSUS is the same content, delivered on a schedule and under your approvals.
This Server Academy explainer covers the basics if you've never opened the console:
WSUS products, classifications and feature packs
Each sync is scoped by two lists in the console under Options > Products and Classifications. Products are the software you run: Windows 10, Windows 11, the Microsoft Server Operating System versions, SQL Server and the rest. Classifications are the kinds of update, including Critical Updates, Security Updates, Definition Updates, Drivers, Feature Packs, Update Rollups and Upgrades.
Feature Packs is the classification that puzzles new admins. Microsoft defines a feature pack as new product functionality that ships outside a full product release, with the next full release expected to include it. Windows 10 and 11 feature updates don't arrive there: they sync under Upgrades, so that's the classification to tick before you approve a move to a new Windows 11 version.
Office is the exception to plan around. Microsoft 365 Apps and Office LTSC 2024 are Click-to-Run products, and Microsoft's documentation says WSUS isn't used by itself to update Office LTSC 2024. Configuration Manager or Office's own update channels handle it.
WSUS service names, console and database
On the server, the role runs as the WSUS Service (service name WsusService) behind an IIS site called WSUS Administration with its own application pool, WsusPool. Its database is SUSDB, held in Windows Internal Database or SQL Server, and you manage the whole thing from the Update Services console or the UpdateServices PowerShell module, which is where Get-WsusServer comes from.
On each device, the client side is the Windows Update service, wuauserv, which runs inside a shared svchost.exe process. Our svchost.exe guide shows how to tell which service a given svchost process is hosting.
WSUS vs Windows Update client policies
The name Microsoft uses has shifted a few times. Windows Update for Business is now documented as Windows Update client policies, and Autopatch builds on top of it. The difference from WSUS comes down to where the updates come from.
With WSUS, your server is the source. Devices download from it, and nothing installs until you approve it there.
With Windows Update client policies, Microsoft's cloud is the source. You don't approve individual updates. You set rules: defer quality updates by a few days, defer feature updates by months, pick a deadline, and assign devices to rings. Each device downloads directly from Windows Update, wherever it is.
That trade is the whole decision in miniature. WSUS gives you per-update control and local downloads, at the cost of a server to maintain. Client policies give you no server and devices that patch from any network, at the cost of per-update approval.
On Windows 10, pointing a device at WSUS and setting deferral policies at the same time used to make it scan Windows Update instead, a behavior called Dual Scan. Microsoft replaced that with the scan source policy covered further down, and Dual Scan isn't supported on Windows 11.
What WSUS deprecation means
On September 20, 2024, Microsoft announced it had deprecated WSUS. The wording matters here, because "deprecated" got read as "dead" in admin forums.
Microsoft's clarification a few days later spelled it out. It's no longer investing in new capabilities or taking feature requests. It is preserving current functionality, will keep publishing updates through the WSUS channel, and has no current plans to remove WSUS from in-market versions of Windows Server, including Server 2025.
In plain terms, the WSUS role still ships in Windows Server 2016, 2019, 2022 and 2025, still gets monthly content, and is still supported for production. What's gone is any new feature, any feature request, and any reason to expect a roadmap.
One related change is easy to miss. Windows Internal Database, the default WSUS database, is also on Microsoft's deprecated list for Windows Server, with a note to consider SQL Server instead. WID still works today, though the same list now says it will be removed from Windows in a future release. A WSUS box on WID is a deprecated role sitting on a deprecated database.
Driver updates nearly went first. Microsoft planned to stop syncing drivers to WSUS in April 2025, then postponed that on April 7, 2025 after feedback from teams running disconnected networks. WSUS still syncs drivers from Windows Update and imports them from the Microsoft Update Catalog, and as of November 2026 Microsoft hasn't published a new removal date.
The r/sysadmin thread from the week of the announcement is a good read on how admins took the news:
When is WSUS end of life?
WSUS has no end-of-life date of its own. Microsoft supports the role for as long as it supports the Windows Server version it's installed on, and the deprecation didn't change those dates.
| Windows Server version | Mainstream support ends | Extended support ends |
|---|---|---|
| Windows Server 2016 | January 11, 2022 | January 12, 2027 |
| Windows Server 2019 | January 9, 2024 | January 9, 2029 |
| Windows Server 2022 | October 13, 2026 | October 14, 2031 |
| Windows Server 2025 | November 13, 2029 | November 14, 2034 |
Source: Microsoft lifecycle pages, read November 2, 2026.
The date that matters soonest is Server 2016's. A WSUS server on it stops getting security updates after January 12, 2027, so moving the role to a newer Windows Server, or retiring it, is a job for the next ten weeks. Our Windows Server 2012 R2 end of life guide covers the options for a server going out of support, with Server 2016 next in line.
Microsoft's commitment covers in-market versions of Windows Server, so the release after Server 2025 may not include the WSUS role at all.
WSUS security: CVE-2025-59287 and the 2026 fixes
Deprecated doesn't mean unpatched, and October 2025 showed why that matters. CVE-2025-59287 is a deserialization flaw in WSUS that lets an attacker who can reach the server's ports run code on it with no credentials, rated 9.8 out of 10 on CVSS. The October Patch Tuesday fix didn't fully close it, so Microsoft shipped an out-of-band update on October 23, 2025, and CISA added the flaw to its Known Exploited Vulnerabilities catalog the next day, with a November 14, 2025 deadline for federal agencies.
A WSUS server is worth an attacker's effort because of where it sits. Every managed device can reach it and takes its update list from it, so a compromised server can at the very least hold patches back from the whole fleet.
WSUS has kept getting security fixes since. The National Vulnerability Database lists nine more WSUS vulnerabilities fixed between January and October 2026, from a remote code execution bug in January (CVE-2026-20856, rated 8.1) to three privilege escalation fixes in October, and none of the nine was on CISA's exploited list as of October 30, 2026. Our October 2026 Patch Tuesday breakdown shows what one month's release looks like.
Hardening a WSUS server comes down to four habits. Install each month's cumulative update on the server itself, not only on the clients it serves. Allow inbound 8530 and 8531 only from the networks your clients sit on, never from the internet. Move clients to HTTPS on 8531 so they can tell the server is yours. And if a WSUS server no longer serves anyone, remove the role instead of leaving it running.
Why teams still run WSUS
WSUS stuck around because it solves a few problems well, and some of them have no clean cloud answer.
Approval control. Nothing installs until someone approves it. For a team that got burned by a bad cumulative update, that gate is the whole point.
Bandwidth. One server downloads each update once instead of every device pulling it separately. On a thin branch-office link, that still matters.
Disconnected networks. WSUS can run disconnected: you export updates from a connected server and import them on the isolated one. Labs, OT networks and classified environments depend on this.
No extra license. WSUS comes with Windows Server. Cloud replacements sit behind specific Microsoft 365 or Azure licensing. WSUS isn't entirely free of licensing, though: it runs under your Windows Server license, and Microsoft's older licensing FAQs count each device it updates as needing Windows Server CAL coverage, so confirm current terms with your licensing partner.
Servers. Some teams keep servers on WSUS because they want a human deciding when a domain controller reboots.
None of those reasons went away in 2024. What changed is that they now come with a deprecated tool attached.
WSUS offline update vs a disconnected server
WSUS Offline Update is a different thing with a similar name. It's a free, open-source community tool, not a Microsoft product, that downloads Windows and Office updates into a folder or ISO you can carry to a machine with no network. It was the closest thing to an open-source WSUS, but its community edition's latest release on GitLab is 12.6.1, from December 2021, so treat it as unmaintained for current Windows 11 and Server 2025 builds.
For air-gapped networks, the supported route is still WSUS itself. A connected WSUS server downloads and approves updates, you export its content and metadata, and the disconnected server imports them with wsusutil import. Microsoft also still publishes wsusscn2.cab, the offline scan file that tools use to check a machine for missing security updates without contacting any server.
Where WSUS costs you time
The other side of the ledger is maintenance. WSUS keeps working as long as someone keeps it tidy, and tidying it is a recurring chore.
- Database bloat. The update catalog grows every month. Superseded and expired updates pile up until the console times out.
- Cleanup that nobody schedules. The Server Cleanup Wizard and
Invoke-WsusServerCleanupin PowerShell exist for exactly this. On a neglected server, the first run can take hours. - Devices that never check in. A laptop that works from home and never touches the VPN never reaches an on-premises WSUS server. It either falls behind or gets updates from Windows Update with none of your approvals applied.
- Reporting. WSUS reports show what a client said it installed. Pulling that into anything a client or auditor wants to read takes exports and spreadsheets.
If you already script cleanup, the cmdlets in our PowerShell commands guide cover the basics of running them on a schedule.
Why WSUS clients stop reporting
A device that drops out of the console, or never shows up, comes down to one of three causes. First, the policy: run the registry check from the migration section below to confirm the device points at the right server and port. Second, the network: Test-NetConnection wsus01 -Port 8530 from the device shows whether it can reach the server at all. Third, cloned images: devices built from one image without Sysprep share a single SusClientId, and WSUS shows only one of them.
The fix for duplicates is to delete the SusClientId and SusClientIdValidation values under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate and restart the Windows Update service. On Windows 10 and 11, the old wuauclt /detectnow /reportnow switches no longer trigger a check-in, so start a scan from Settings > Windows Update instead and give the device a few minutes to report.
Keep WSUS healthy while you transition
A migration can take months, and the old server still has to patch devices in the meantime. Three habits keep it usable until the day you switch it off.
First, sync less. In the WSUS console under Options > Products and Classifications, untick products you don't run and the Drivers classification. Driver metadata is the fastest way to bloat the database.
Second, clean up on a schedule. The UpdateServices PowerShell module handles the whole job in one line, and it's worth running monthly from Task Scheduler:
powershellGet-WsusServer | Invoke-WsusServerCleanup -DeclineSupersededUpdates ` -DeclineExpiredUpdates -CleanupObsoleteUpdates ` -CleanupObsoleteComputers -CleanupUnneededContentFiles
Third, decline what you'll never approve. Superseded updates, ARM64 builds on an all-x64 fleet and old feature updates only slow down the console and every client scan.
What replaces WSUS
Microsoft named its replacements in the deprecation post: Windows Autopatch and Microsoft Intune for client update management, and Azure Update Manager for servers. Each covers a different slice of what WSUS did.
Windows Autopatch and Intune (Windows clients)
Windows Autopatch runs inside the Intune admin center. It handles quality updates, feature updates, and driver and firmware updates through update rings and Autopatch groups. You can set each content type to deploy automatically or wait for manual approval, which is the part WSUS admins miss first.
Microsoft says Autopatch aims to update 95% of devices by their target compliance date. Reporting refreshes in under four hours.
The catch is prerequisites. Autopatch needs Microsoft 365 Business Premium, Windows Enterprise E3 or E5 (including through Microsoft 365 F3, E3 or E5), or Education A3 or A5. Devices must be corporate-owned, enrolled in Intune or co-managed with Configuration Manager, and able to reach the internet. Our Intune review covers what the rest of the Intune license buys.
Azure Update Manager (servers)
Azure Update Manager patches Windows and Linux servers in Azure, on-premises and in other clouds. On-premises servers need to be connected through Azure Arc first. It schedules updates in maintenance windows, runs assessments every 24 hours and reports compliance in one view.
One detail makes the transition easier. Azure Update Manager can apply updates that are published to WSUS, so a server can keep its WSUS source while Update Manager handles scheduling and reporting.
Pricing depends on where the server runs. Azure Update Manager is free for Azure VMs and lists at $5 per Arc-enabled server a month, charged only for days the server is connected and has an update schedule or operation (November 2026). Microsoft waives that charge for Arc servers covered by Software Assurance or a Windows Server subscription, by Defender for Servers Plan 2, or by Extended Security Updates through Arc. Windows Server 2025 machines connected through Arc can also take Hotpatch updates at no extra cost: a cumulative update baseline every three months, then two months of security updates that install without a restart.
How WSUS, Intune and Azure Update Manager compare
| WSUS | Intune and Autopatch | Azure Update Manager | |
|---|---|---|---|
| Patches | Windows clients and servers | Windows 10 and 11 clients | Windows Server and Linux |
| Runs where | Your server, on your network | Microsoft's cloud | Azure, with Arc for on-premises servers |
| Approval model | Per update, per computer group | Rings, deferrals and deadlines, with optional approval per content type | Maintenance schedules by classification |
| Reaches remote laptops | Only on your network or VPN | Yes, from any internet connection | Not built for laptops |
| Third-party apps | Only with a publishing add-on | Enterprise App Management add-on, $2 per user a month | Linux packages from your configured repositories |
| Cost, November 2026 | Included with Windows Server | Intune Plan 1 at $8 per user a month, or included in Business Premium and Microsoft 365 E3 or E5 | Free on Azure VMs; $5 per Arc server a month unless waived |
Azure vs Intune: which one patches what
The two get compared because both live in Microsoft's cloud, but they patch different machines. Intune manages Windows 10 and 11, macOS, iOS, Android and Linux desktops, and Windows Server isn't on its supported platform list, so it won't patch a server. Azure Update Manager covers the other half: Windows Server and Linux servers in Azure, on premises through Azure Arc and in other clouds. When people say Azure in this comparison they sometimes mean Microsoft Entra ID, formerly Azure AD, the identity service both tools sign in through, which doesn't deploy updates at all.
An estate with clients and servers ends up with both, plus a decision on who watches each console. For an in-house IT team, that's one tenant and two consoles. For an MSP, it's two consoles per client tenant, which is where a single cross-client patching tool earns its place.
Configuration Manager
Configuration Manager (still widely called SCCM) uses a WSUS server as its software update point. Microsoft said the deprecation doesn't affect Configuration Manager's capabilities or support. If you run ConfigMgr today, you aren't forced off WSUS. You're on the same slow road as everyone else, just with more tooling around it.
RMM and third-party patching
An RMM or a dedicated patch tool is the fourth path, and for an MSP it's the one that spans every client. These tools talk to the Windows Update agent directly, apply their own approval policies, and the ones with an app catalog patch third-party apps too, which WSUS doesn't handle out of the box. Our patch management tools roundup compares the main options.
WSUS can carry third-party updates, but only with help. Configuration Manager's third-party software update catalogs, or a publishing add-on such as Patch My PC, push vendor updates into WSUS, and every client has to trust the code-signing certificate those updates carry. Without one of those, WSUS serves Microsoft content only.
Enterprise platforms sit in this group too. Tanium's Patch module, for example, can scan devices against Microsoft Update directly or use WSUS as a back end, so a WSUS vs Tanium comparison comes down to whether you want a WSUS server in the chain at all.
OpenFrame from Flamingo, open and AI-native infrastructure for IT and security, fits here as well. Patching is one of its first-generation modules alongside RMM, remote access, PSA, MDM, SIEM and documentation, with AI agents working inline: Fae resolves support requests and Mingo runs IT operations such as patch jobs and their follow-up. It costs $1 per device a month with 10M AI tokens included, or $0.80 on annual billing, after a 14-day free trial.
How to choose a WSUS alternative
Pick by device and license first, then by how much control you need.
Start with the network. If a network can't reach the internet, none of the cloud tools can patch it. Keep WSUS there, move it to SQL Server if it's still on WID, and document it as a deliberate exception.
Then check licenses. A client already on Business Premium or E3 has Autopatch included. Paying for an upgrade just to replace WSUS is a harder sell for a 20-seat office.
Then look at who owns the tooling. For an MSP, one patching tool across every client spares you a different Microsoft console per tenant. For an internal IT team with Microsoft 365 E3, Autopatch keeps everything in Intune.
Then decide on servers separately. Servers carry more risk per reboot. Azure Update Manager, ConfigMgr, an RMM with maintenance windows or a kept WSUS server can all be reasonable here, depending on what the rest of the estate uses.
Whatever you pick, keep an approval step for feature updates and a pilot ring for everything. That's the part of WSUS worth keeping.
WSUS alternatives for on-premises networks
An on-premises WSUS replacement can mean servers that should stay off the public cloud, or a network with no internet at all, and the options differ on both counts.
| Option | Where it runs | Works with no internet? | Notes |
|---|---|---|---|
| Keep WSUS | Your Windows Server | Yes, with export and import | Supported through the host server's lifecycle |
| Configuration Manager | Your servers | Yes, with an offline software update point | Still uses WSUS underneath |
| Azure Update Manager with Arc | Your servers, managed from Azure | No | Needs outbound access to Azure |
| On-premises patch servers, such as ManageEngine Patch Manager Plus | Your server | Check each vendor's offline support | Adds third-party apps |
| Red Hat Satellite or Canonical Landscape | Your servers | Satellite has a disconnected mode | Linux only, since WSUS has no Linux support |
For a free start on internet-connected devices, Action1 covers its first 200 endpoints at no cost, though it's cloud-hosted rather than on premises, and our Action1 review section has the details.
How to move off WSUS without a patching gap
The migration risk sits in the handover week, when devices get updates from nowhere, or from two places at once.
1. Find what still points at WSUS
Every device managed by WSUS carries its server address in the registry, written there by Group Policy. This one-liner shows it on a single machine:
powershellGet-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' | Select-Object WUServer, WUStatusServer
An empty result means the device isn't pointed at WSUS. Run it across the fleet and you have your real inventory, which can differ from what the WSUS console shows. OpenFrame can run a script like this across every device in a client's environment, or across your own fleet, and collect the output in one place.
2. Move one update type at a time
Windows 10 version 2004 and later, and Windows 11, support the scan source policy. In Group Policy it's Specify source service for specific classes of Windows Updates, under Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Server Update Service.
It splits updates into four classes: feature updates, quality updates, driver and firmware updates, and updates for other Microsoft products. You choose WSUS or Windows Update for each class. Microsoft's own advice is to move step by step, for example drivers first, then quality updates.
Two cautions from Microsoft's documentation. The old "Dual Scan" policy isn't supported on Windows 11 and conflicts with the scan source policy on Windows 10. And if you use Intune, set all four CSP policies, not just one. Our guide to Windows Update group policy covers the deferral settings that sit alongside it.
3. Pilot, then widen
Build a pilot ring in the new tool that mirrors your WSUS pilot group. Run it for at least one full Patch Tuesday cycle. Compare what installed with what WSUS would have approved.
An admin on r/Intune asked how to do exactly this move from WSUS to Intune-managed updates:
4. Remove the WSUS policy, then the server
Unlink the WSUS Group Policy objects only after the new tool shows devices reporting in. Then re-run the registry check to confirm nothing still points at the old server. Keep the WSUS server read-only for a month in case you need to roll back, then decommission it.
Should you replace WSUS now?
WSUS isn't going to stop working next Patch Tuesday. Microsoft says it's supported, patched and shipping in Server 2025. That gives you time to move on your schedule instead of in a hurry. The exceptions are a WSUS server on Windows Server 2016, which loses security updates after January 12, 2027, and any WSUS server still missing the October 2025 fix.
Use that time. Move the clients that can reach the cloud, split servers into their own decision, and keep WSUS only where the network leaves no other choice. For the wider picture of how updates fit into your security routine, read our patch management tools roundup next.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/what-is-wsus
Still deciding?
Ask Mingo answers from our docs and customer stories.