Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error Event ID 12002

Event ID 12002 and 12032: WSUS web services stop answering and clients stall

11 min read Updated October 5, 2026 Windows Server: RDS, Hyper-V & Clustering

Fix it now

Behind almost every one of these events is the same thing: the WsusPool application pool in IIS has stopped, so every WSUS web service answers 503 and clients quietly stop reporting. Microsoft’s documented cause for a WSUS 503 is exactly that, and the documented remedy is to give the pool more memory.

Run these in an elevated PowerShell session after making the IIS change below

iisreset
Get-Service WsusService
  1. Open Internet Information Services (IIS) Manager, select Application Pools in the Connections pane, and look at WsusPool. If it is stopped, that is your 503.
  2. Right-click WsusPool and choose Advanced Settings. The Private Memory Limit (KB) will usually be the default 1843200. Microsoft’s troubleshooting guidance is to raise it to 4000000, and to 8000000 or higher on larger environments.
  3. Restart the pool and then reset the web services with iisreset.
  4. Browse to the WSUS server’s own URL from another machine and confirm you no longer get HTTP Error 503.
  5. If it dies again within hours, the database is the reason: decline superseded updates and run the cleanup before changing any more IIS settings.

Microsoft’s WSUS best practices set Private Memory Limit to 0, meaning no limit, while its troubleshooting guidance raises it to 4 GB. Both are documented; 0 is only safe on a server with the memory to back it.

If WsusPool stays started through a full client check-in cycle, you can stop here. The next section explains why the pool keeps stopping.

Why it happens

WSUS is an ASP.NET application. Everything a client does goes through one of its web services, and all of them run inside a single application pool called WsusPool. When that pool stops, IIS answers every request with 503 – Microsoft’s documented symptom set is “The request failed with HTTP status 503: Service Unavailable” in the console and “HTTP Error 503. The service is unavailable” from a browser, with the most likely cause given as the WsusPool application pool being in a stopped state.

What stops it is usually memory. A WSUS server that has been running for a year or two knows about an enormous number of updates, and the metadata it builds for clients tracks that number. As more clients sync at once the pool’s working set climbs, hits its private memory limit, and IIS recycles it underneath requests that were in flight. Enough of those failures close together and the pool is stopped rather than restarted.

The events in the 12000 series arrive alongside this, one per service, which is why they look like several problems. They are not documented individually – Microsoft publishes no message list for them – so treat them as WSUS reporting that its own components cannot be reached, and work from the pool state and the 503, both of which are documented.

The pool is being recycled on its private memory limit

You have this one if WsusPool stops under load, particularly when many clients check in after a patch release.

  1. In IIS Manager, Application Pools, WsusPool, Advanced Settings.
  2. Raise Private Memory Limit (KB) from the 1843200 default to 4000000, or higher on a large estate.
  3. Where the server has the memory to back it, Microsoft’s best-practice value is 0 – no limit at all – together with Queue Length 2000, Idle Time-out 0, Ping Enabled False and Regular Time Interval 0.
  4. Restart the pool and watch it through a full client check-in cycle.

A limit of 0 does not remove the ceiling; it makes the operating system the ceiling. That is fine with headroom and dangerous without it.

The catalogue has grown until every request is expensive

You have this one if The pool restarts cleanly and dies again within hours. The console is slow and times out on large views.

  1. Decline superseded updates. Microsoft calls keeping superseded updates longer than needed the leading cause of WSUS performance problems.
  2. Run the cleanup: Get-WsusServer | Invoke-WsusServerCleanup -DeclineSupersededUpdates -DeclineExpiredUpdates -CleanupObsoleteUpdates -CleanupObsoleteComputers -CleanupUnneededContentFiles -CompressUpdates
  3. Reindex SUSDB. On a Windows Internal Database installation, connect over the named pipe \\.\pipe\MICROSOFT##WID\tsql\query.
  4. Repeat until a pass completes quickly, then schedule it monthly.

If you do not deploy drivers through WSUS, do not synchronise them. Driver classifications are the fastest way to make a catalogue unmanageable.

The pool is stopped and stays stopped

You have this one if Starting the pool works, and it is stopped again shortly afterwards without anyone touching it.

  1. Look at Rapid-Fail Protection in the pool’s Advanced Settings. It is enabled by default and stops the pool after 5 failures in a 5-minute interval.
  2. Read the Application log for the actual crash before raising those thresholds; the protection is a symptom, not the fault.
  3. Address the memory limit and the database first, then restart the pool.

The service or its database is not running

You have this one if The pool is up, the events persist, and the console cannot connect at all.

  1. Check the service: Get-Service WsusService, and start it if it is stopped.
  2. On a WID installation confirm the internal database service is running as well; every WSUS service except self-update needs the database.
  3. Confirm the WSUS content directory exists at the path WSUS is configured to use.
  4. Reset the web services with iisreset once the dependencies are healthy.

Full reference

The WsusPool settings, with Microsoft’s own numbers

Setting IIS default WSUS best practice Troubleshooting guidance
Queue Length 1000 2000
Idle Time-out (minutes) 20 0
Ping Enabled True False
Private Memory Limit (KB) 1843200 0 (unlimited) 4000000, or 8000000 and higher on larger environments
Regular Time Interval (minutes) 1740 0

The two positions in the last two columns are both Microsoft’s, and they answer different questions. Unlimited suits a dedicated WSUS server with memory to spare, where recycling mid-scan is the problem. A large fixed limit suits a server sharing memory with other roles, where an unbounded pool would push the machine into paging and turn a recoverable recycle into an unresponsive server. Pick the one that matches the box in front of you, and check how much memory the pool actually peaks at before deciding.

Rapid-fail protection, as configured out of the box

Property Default
Enabled True
Maximum Failures 5
Failure Interval (minutes) 5

So five worker failures inside five minutes take the pool out of service until somebody starts it. Raising those numbers hides repeated crashes rather than fixing them; the useful response is to find out what is killing the worker, which on a WSUS server is nearly always memory or the database.

Keeping the catalogue small enough to serve

Microsoft’s guidance is unambiguous about the priority here: keeping updates that are superseded for longer than you need them is the leading cause of WSUS performance problems. It is fine to keep them while you are still deploying them, and it is not fine to keep them afterwards. The documented maintenance order for a neglected server is to back up SUSDB, reindex it, decline superseded updates, and then run the cleanup – in that order, because a cleanup against an unindexed database on a busy server is what produces the console timeouts people then blame on the cleanup.

Cleanup switch What it removes
-DeclineSupersededUpdates Declines superseded updates
-DeclineExpiredUpdates Declines expired updates
-CleanupObsoleteUpdates Deletes obsolete updates from the database
-CleanupObsoleteComputers Deletes obsolete computers from the database
-CleanupUnneededContentFiles Deletes unneeded update files
-CompressUpdates Deletes obsolete revisions to updates from the database

Where SUSDB lives

Check HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services\Server\Setup, value SQLServerName. A value containing ##WID or ##SSEE means the Windows Internal Database, which on Windows Server 2012 and later is reached over the named pipe \\.\pipe\MICROSOFT##WID\tsql\query. Anything else names a full SQL Server instance, and the login the pool uses needs rights on SUSDB there.

When the pool is healthy and clients still do not report

  • Confirm client last-contact times in the console rather than trusting the computer list; a client that cannot reach the server keeps showing its last known state indefinitely.
  • Confirm the clients are pointed at the right server and port in policy, and that both the server and status server values agree.
  • Check whether a duplicate MIME map entry is breaking part of the site: Microsoft documents “Cannot add duplicate collection entry of type mimeMap” as a real WSUS failure with a web.config fix.
  • Confirm the content directory is present and reachable at the configured path before assuming the fault is in IIS at all.

When a licence is the actual fix

WSUS is a role included with Windows Server, so nothing here needs a purchase. The licensing question that does arise is a different one. If the pool keeps failing because WSUS shares a server with a production workload it should never have shared with, the durable answer is its own instance with its own memory – and that instance needs a Windows Server licence. Windows Server Standard covers two virtual machines plus one Hyper-V host per licence; Datacenter covers unlimited virtual machines plus one Hyper-V host. Worth weighing at the same time: Microsoft has published WSUS as no longer actively developed, while stating that all existing capabilities and content continue to be available for your deployments. Arco supplies Windows Server 2025 Standard and can check whether the CALs you hold already cover the arrangement.

Every code this article covers

Code What it points at Source
Event ID 12002 Logged by WSUS when one of its own components is not answering. Microsoft publishes no message list for the 12000-series health events, so read the event body and confirm the pool state not published by the vendor
Event ID 12032 Another of the same family, with no published message text. Where several arrive together, the pool itself is the thing to check rather than any individual service not published by the vendor
Event ID 12012 Same family, no published message text. Treat it as evidence of the outage rather than as a diagnosis of which component failed not published by the vendor
Event ID 12022 Same family, no published message text not published by the vendor
HTTP 503 IIS returning service unavailable. Microsoft’s documented cause for a WSUS 503 is that the WsusPool application pool is in a stopped state, with the remedy being to raise its private memory limit and restart it Microsoft Learn

Confirm the fix worked

  1. WsusPool shows Started in IIS Manager and stays started through a full client check-in cycle.
  2. Browsing to the WSUS server URL from another machine returns a page rather than HTTP Error 503.
  3. Get-Service WsusService reports Running, and on a WID installation the internal database service is running too.
  4. Client last-contact times are updating across the estate, not just for a few machines.
  5. The pool survives the days after a patch release, which is when the check-in load peaks.

Questions people ask about this

Should Private Memory Limit be 0 or 4 GB?

Both are Microsoft’s. The best-practice table sets it to 0 for a dedicated WSUS server with memory to spare; the troubleshooting guidance raises it to 4,000,000 KB and says 8,000,000 or higher may be needed. On a shared or memory-tight server, a large fixed limit is the safer of the two.

Do I need a licence or a bigger edition to fix this?

No. WSUS is a Windows Server role available in both Standard and Datacenter, and every fix here is configuration or database maintenance. Clients still need the CALs they already needed.

Is WSUS still supported?

Microsoft has published it as no longer actively developed, while stating that all the existing capabilities and content continue to be available for your deployments. Treat that as a reason to plan, not as a reason to abandon a server that is patching your estate today.

How often should the cleanup run?

Monthly suits most sites, and it must include declining superseded updates rather than only removing obsolete computers. A server that has gone years without one may need several passes before a single run completes quickly.

Will restarting the pool lose client data?

No. Clients retry, and an interrupted check-in simply happens again. The visible effect is a gap in reporting, not lost update state.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Event ID 56 and 50 from TermDD: a certificate or security-layer fault is dropping RDP sessions Free Fix 0xC0370027 and 0xC0370104: saved state and checkpoint data cannot be read License Error Event ID 1177 and 1564: quorum is lost and the cluster service shuts down License Error Event ID 129 and 153: iSCSI and SAN timeouts retry until the volume drops
โ† Back to Knowledge Base