WSUS Support Tip: “WARNING: Skipping scan, self-update check returned 0x800B0001” in WindowsUpdate.log

WSUS Support Tip: “WARNING: Skipping scan, self-update check returned 0x800B0001” in WindowsUpdate.log

  • Comments 4
  • Likes

toolsignExample Scenario: You just got some new servers and patch them online against Microsoft Update before pointing them to your WSUS server for updates.

Symptom: In the WindowsUpdate.log you may see the following.

“WARNING: Skipping scan, self-update check returned 0x800B0001”

“WARNING: WU client failed Searching for update with error 0x800b0001”

In the Windowsupdate.log, you notice your client is at version 7.6.7600.256

Cause: This can be due to a version mismatch between the Windows update agent and the WSUS server. WSUS needs to be at version 3.2.7600.251 in order to properly communicate with clients at version 7.6.7600.256

Solution: Install KB2720211 to get your WSUS to the correct version for your clients. http://support.microsoft.com/kb/2720211

Since there are a few known issues with the patch, be sure to read the whole article so you can gather information about what issues may apply in your situation. There is also an excellent blog post by Joao Madueria that give you some great guidelines on what to do before installing the KB, and what to do if you do encounter an issue after installing KB272011: http://blogs.technet.com/b/sus/archive/2012/06/20/wsus-kb272011-common-issues-encountered-and-how-to-fix-them.aspx.

- Meghan Stewart

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Exactly what I was looking for - solver my Win2008 R2 problem :)

  • I'm getting this problem in Windows 8 Enterprise RTM, where the client version is 7.8.9200.16384

    Is there another update to WSUS required to support this newer client version?

  • Dear Collegues!

    We have same problem as [Paul]. Will be there any update to current WSUS ?

  • Thanks a lot. This solved my issue clients not reporting to the WSUS server.