I  facing an issue with importing update from catalog to the WSUS server.

Here is the error message

I have only one stand alone WSUS server serving 700 clients. Not sure what is causing the issue. 

Any pointers?

Hello,

I am configuring WSUS on our network (Server 2012), and have a couple concerns regarding Driver updates.

I would like the machines connected be able to update their drivers when necessary.

It is important to note that for the Update Files and Languages, I do not plan to update the files locally, but rather have them download from the MS Update Servers.

What I want to avoid is a reporting nightmare.

For example, I do not want my reporting to come back and say:

Group A does not need 1,226 updates.

What are your thoughts on Driver updates via WSUS?

For some reason, clients on my domain with older versions of Silverlight are not reporting that they need KB2977218 when they check with my WSUS Server but when I click to check online it says they need the update.

This is Happening on many Windows 7 and Server '08 R2 systems.

I verified on the WSUS server that the update is in fact Synchronized, Approved, and fully Downloaded.

I noticed on the Update Report for KB2977218 on my WSUS Server, it says "The update is installed/not applicable on" all my systems.  This tends to suggest that the KB2977218 that WSUS downloads has a problem in the detection method of this update.

I verified on one of the Windows 7 systems that the installed version of Silverlight is 5.1.30214.0 while KB2977218 is version 5.1.30514.0

Is anyone else experiencing the same problem?

Any help is much appreciated.

Recently, Microsoft has identified a possible issue with WSUS server and Windows update clients.
These issues would occur and reflect in event logs with following event ID:
Event ID: 16
In the WindowsUpdate.log you may see the following entries:
“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”
While going through event logs under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operational you may find an error event ID: 25 as follows
===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 25
Task Category: Windows Update Agent
Level: Error
Keywords: Failure, Check for Updates
User: SYSTEM
Computer: <computer name>
Description: Windows Update failed to check for updates with error 0x800b0001.
======================================

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 or later in order to properly communicate with clients at version 7.6.7600.256 or later.

Resolution:
Meanwhile to resolve this issue, one of the most workable troubleshooting steps listed as follows:

NOTE:
However please make sure that the issue that you try to resolve should have error 0x800b0001 and event ID 25 as shown above.
Troubleshooting steps:
1. Check windowsupdate.log in order to understand what is causing this issue.
2. If you find following entries:
“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”
(To understand how to access and read the Windowsupdate.log file please refer to following link –
http://support.microsoft.com/kb/902093 )
Follow the steps:
3. Stop the Automatic Update service or run command: “net stop wuauserv”.
4. Open Regedit and browse to the following Registry Key:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.
5. Save a copy of this WindowsUpdate key (File / Export or Right-click / Export).
6. Delete the following registry values:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\PingID.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AccountDo
mainSid.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId
7. Close Regedit.
8. Start the Automatic Update service or run command: “net start wuauserv”.
9. On client machine, force synchronization with the WSUS Server: “wuauclt /detectnow”.
10. Now check windows update and click “Check for new updates”.
11. If a message with green bar appears indicates that issue is resolved.
12. If a message with red bar appears indicates that issue is not resolved and proceed with
further troubleshooting.
13. In command prompt run the command: “netsh winhttp show proxy” – and check for
any proxy configuration. If proxy is not configured proceed as follows.
14. Stop WIN HTTP Proxy service and windows update service and registered important
DLLs required for the changes to take place.
net stop WinHttpAutoProxySvc
net stop wuauserv
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /s.
15. In windows registry, for following Registry Key - take a backup: "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate."
16. Delete the following registry value.
"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId”
17. Run iisreset command in command prompt to restart all IIS related services and start windows update service.
18. On the client, do force synchronization with the WSUS Server by running command: “wuauclt /detectnow”.
19. After conducting the troubleshooting steps, we checked the event logs and found following success event on the client machine under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operational:

===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 30
Task Category: Windows Update Agent
Level: Information
Keywords: Connection
User: SYSTEM
Computer: <computer name>
Description: Windows Update established connectivity.
===================================

Hence this issue is resolved. No further action is required.
20. If this event is not found proceed further with following steps:
21. Open "notepad"
22. Copy the following commands and then paste them into the opened Notepad window: net stop wuauserv net stop CryptSvc ren %windir%\system32\catroot2 catroot2.old ren %windir%\SoftwareDistribution sold.old net start CryptSvc net start wuauserv pause
23. We are renaming two files by this - catroot2 and SoftwareDistribution.
24. After pasting the above commands, please close the Notepad window. Choose "Save" when you are prompted to save the file. Type "rename.bat" as the file name and save it to the Desktop.
25. Return to the Desktop, right click the rename.bat file and choose "Run as administrator".
26. You will see a DOS-like window processing. Now try Windows Update to see if the issue has been resolved.
27. If your issue is not resolved again then apply following update on the WSUS server machine Please be sure apply this update to WSUS SERVER MACHINE

http://support.microsoft.com/kb/2734608

28. Apply this update. 29. You must restart the computer after you apply this update.
30. Start synchronization on WSUS
31. Wait for the synchronization to succeed.
32. On the affected client, open cmd.exe in elevated mode
33. Type the following commands. Make sure that you press Enter after you type each command: Net stop wuauserv Net start wuauserv
34. The issue would be resolved once and for all.

 Microsoft has released this update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 (SP2)

 This update strengthens the WSUS communication channels.

 The Windows Update Agent (WUA) on computers that are managed by this WSUS server will be automatically upgraded as needed after you apply this update.

 WSUS must be in a known, good working state for this update to work. If WSUS is configured to synchronize updates from Microsoft Update, make sure that WSUS can synchronize updates. And, clients must be able to communicate with the WSUS server.

 This update lets servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.

Any improvements or feedback on above troubleshooting steps is surely welcome.
Thank You.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi Guys,

Looking for some help to get my WSUS server back online.

I have 1 WSUS server in my environment running WSUS 3.0 SP2 on a Server 2008 R2 Virtual machine. For the most part it works as expected. However, it's not able to update our Server 2012 R2 servers.

After a quick google search I realised that I needed to install KB2734608. After downloading the update I tried to complete the install only for it to error and to my horror WSUS no longer seems to work. I've tried several reboots but from the server the MMC console fails and forces me to unload it and from my desktop machine I receive the Error: Connection Error message.

After looking in the install updates list I have noticed that KB2720211 was installed today (I believe it's part of the KB2734608 package). A quick google search on this shows that lots of people have had trouble with this update and I found many suggestions on how to fix my busted server. Unfortunately nothing that I've tried has made any difference so far.

Here's what I've tried...
1. http://www.synetx.com/tips/?p=80
2. Changing registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services\Server\Setup\wYukonInstalled  from 1 to 0 and rerunning installer (install fails for KB2720211 or KB2734608
3. Restoring WSUSSignDb.cer WSUSSignDb.dll & WSUSSignDb.sql From Backup

Most people have had success by performing one of the above steps but this hasn't worked for me... What else can I try to do before I'm forced to restore The entire VM from a backup?

Many thanks for any suggestions

Robbie

The server that my installation of WSUS sits on needs a rebuild. I want to keep all of my settings and config so that once I have rebuilt the server with Windows and put WSUS back on, I can just apply the same config and settings as what I have now.

I am assuming that all I need to do is stop the WSUS services, take a backup of the database (which is within a SQL instance), rebuild the server, install WSUS and recover over the database that the new version of WSUS has created?

Is there more to it that that, will my method even work?

We are trying to update ServicePack 1 on a Windows 2008 R2. The update is being executed with WSUS. We tried to download the package from internet and the problem is the same. Error 800F0818.

Here is the log of System Update Readiness Tool

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-07-29 16:30

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum  Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 310
 Found 1 errors
  CBS MUM Corrupt Total count: 1

Unavailable repair files:
 servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat

(w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache 

For short we use WSUS under System Centre Essentials to deploy updates and software. Untill now i have not succeeded to deploy updates or Software successfully in one time. Everytime there are different errors on different clients. But i have downloaded for one machine all updates and put it on a dvd. With updateinstaller.exe when i install all updates for the Windows 7 systems then the updates and/or software packages deployed with SCE successfully.

So which errors the updates show every time when updating completely the clients with that dvd all goes well. Conclusion: there are several updates missing on the clients which are needed to install other things like IE10 / several other updates etc.

The problem is that i cannot update every client with the DVD therefore i have WSUS i believe. Problem with WSUS or system centre that there are so many updates i don't know which one to select. Select them all is very time consuming and filtering in System Centre Essentials for lets say Windows 7 is also giving many other updates like flash etc etc and for WIndows 8 which i don't need.

Maybe someone got a idea how to find out which updates are nessesairy? I have looked in the Windowsupdate.log and run baseline security but there are so many updates there....

Another thing which i came across: On everal clients there where updates waiting, goiing to windows update and looked at important updates there was a update which was released 2 weeks ago. The quiestion here is why is it not installed automatically?
I have a policy run for all machines to download automatically updates and install on schedule. The update schedule start at a dspecific time. Could it be that the users are cancelling something? They do not get a message because the gpo setting is download and schedule install...? Some other updates are installed automaticcally..

freddie

I have our internal WSUS working over SSL for my entire domain EXCEPT for one particular OU. I can check for and download updates from all other machines with no problems. To complicate matters all of the clients in this problem OU are clones from the same image.

A few of the symptoms on the non-working clients:

• Duplicate SusClientIDs
  
• Domain certificates not automatically populated in certmgr.msc (as compared to all other machines where they are)
• If I change the WSUS GPO to HTTP the problem clients work with WSUS straight away.

I have addressed the duplicate SusClientID issue by deleting the bad registry entries and re-authenticating but still no joy over SSL. I have also corrected duplicate SIDs and no joy.

What on Earth am I missing?

Any help here is greatly appreciated.

When I select the products and classification that I would like to download from Microsoft for WSUS, Is there a way to see how much disk space I would need to hold all the updates?

Thanks

I want to use WSUS on Windows Server 2012 R2 in an environment that has only Server 2008 and Server 2008 R2 servers in production. I currently have one WSUS server setup on 2008 R2 that will serve in one geographic location and the WSUS Server 2012 R2 that I looking to setup will be at a separate geographic location.

Has anyone tried this? Are there any problems one can expect? Is this a bad idea?

I am having an issue when attempting to export updates from my WSUS.  My environment is a little unique compared to most.  I have WSUS 3.0 SP2 installed on 64-bit Windows Server 2008.  We have a single forward facing WSUS with an outside connection.  I should also mention upfront that upgrading my server to a newer OS and version of WSUS is NOT an option at this point in time so I need to make this work somehow. We use that to export updates using powershell with the following command:

./wsusutil.exe export E:\WSUS\Export_Cabs\export.xml.gz E:\WSUS\Logs\export.log

We then copy the exported metadata to a removable drive and air gap it over to our WSUS on an isolated network and import the metadata.

For the first few months after we implemented this WSUS installation, everything worked perfectly.  Then one day a couple months ago, I ran the export as I normally do but this time the export failed with the following error:

"The gzip stream can't contain more than 4GB data."

After researching potential causes/solutions, I came across KB2828185.  I checked my update history and it was previously installed far prior to encountering this issue.  At the time, I had .NET 3.5 and .NET 4.5.1 installed.  I have removed them and replaced them with .NET 4.0 and still receive the same error.  I am at my wits end on this.  Every solution I have found leads me to KB 2828185 but this does not fix the problem.  Anybody who can offer some advice or other avenues to explore would be greatly appreciated.



Hello,

We have a WSUS server that we are downloading the updates to. I have noticed that occasionally a few updates fail, and when checking the Windows Update log on the clients, I can confirm the update file they are seeking is not available. When I decline an update and run the cleanup wizard, and then re-approve, the clients can then download the update fine.

Is there any explanation for this behavior? The update might be old and have 100 PCs who successfully downloaded it, but a newly re-imaged machine might be trying to get it and fail.

If anyone can help provide some understanding for me, I'd appreciate it.

I have W7 VM with failing Windows Updates that MUST be repaired.

After spending some time trying to fix the problem I have no other choice but asking for help.

The messages are in French but I guess it will not create any problem for getting it...

Steps I took :

1. There was an entry with IE proxy for Windows update.

I reset winhttp.

Assured:

PS C:\Windows\System32\WindowsPowerShell\v1.0> netsh winhttp show proxy

Paramètres de proxy WinHTTP actuels :

    Accès direct (sans serveur proxy).

2. Windows update failed to download/install 11 updates with the error: Code 80072F78 (in GUI)

I run the command below it showed bunch of updates (probably the same 11) that tried to use erroneous proxy.

Here is one of them...

PS C:\Windows\System32\WindowsPowerShell\v1.0> 

JobId               : 5c3ed23d-6ec6-44df-b6aa-c83ca7b5e252
DisplayName         : WU Client Download
TransferType        : Download
JobState            : Suspended
OwnerAccount        : AUTORITE NT\Système
Priority            : Foreground
FilesTransferred    : 0
FilesTotal          : 1
BytesTransferred    : 0
BytesTotal          : 221123
CreationTime        : 2014-07-30 20:12:19
ModificationTime    : 2014-07-30 20:18:30
MinimumRetryDelay   :
NoProgressTimeout   :
TransientErrorCount : 7
ProxyUsage          : Override
ProxyList           : {http://1602proxy.xxxxxxxxxxx:8080/}
ProxyBypassList     : {172.20.*, *.xxxxx.xxx.ca, 10.*, <local>}

3. I created a scheduled task for batch execution (c:\windows\system32\bitsadmin.exe /reset /allusers ) and run under System\nt authority. After running the task and verifying  again:AllUsers | f, I got no files listed.

So I did hope that the problem was fixed... But not. The same error code.

4, Next I cleaned completely Download and DataStore folders (in Software Distribution).Stoped/Started services and restarted

computer. So no proxy is set. No abandoned updates... But the heck still gives the error.

I am out of ideas. What else could be done?

Thanks.

&quot;When you hit a wrong note it's the next note that makes it good or bad&quot;. Miles Davis

Good Day,

It has come to my attention that MS released a new update KB2938066 which increase security.  The recommendation is to run Server Cleanup Wizard (which I did) and then reindex the WSUS database which I have a question on.

I am running Windows Server 2008R2 with a standard download of WSUS 3.0SP2 installed.  I used the default database which is the internal database for windows.  The database files look like

SUSDB.mdf and SUSDB_log.ldf  and in services you see Windows Internal database (MICROSOFT##SSEE)

With that being said, I need to run the SQLCMD utility which is my problem.

When I go to install the software SQLSERVER2005_SQLCMD_X64   I get the following error and I am not sure what or where I have to go to fix it

Setup is Missing a Prerequisites

SQL Native Client

when I open the link up it really doesn't tell me what I need to do.  Am I running the right software to install SQLCMD or do I need to install some SQL Client first and if so where do I find the client?

Any help or suggestions would be appreciated

Thank You

Adam Raff

Dear Microsoft

Here we go again... you issue an update to fix bugs / improve security.... we spend money and time downloading and installing those updates when themselves need debugging as they fail to install.

Just like many other cases:

• Windows .net4 updtes fail repeated on server 2008 R2
• KB2656351 Fails to install. Signature could not be verified - the certificate could not be checked
• .NET 4 Install Error - Generic Trust Failure
• KB2600217 error code 800B010B "Generic trust failure"

I'm sorry but there has been ample time and community reports to fix these .NET install / update issues delivered via WSUS. I simply cannot afford to spend hours trying to figure out what fix is required this time and then to go and apply that manually to the 40+ servers on which this is failing.

I'm not asking what the manual fix for the above issue is - I don't care anymore. I'm expecting the quality assurance team to pull out their finger and get to grips with these problems and work with your product teams to get these updates working properly through WSUS. Issue a revision to the updates and have them install successfully.

Surely the great Microsoft can handle that? It is your updates for your software delievered through your software into hardware running your software. We the public are getting tired of fixing the same problem over and over, some don't get paid for it and it is becoming an intellectually wasteful past time.

Rant over, but I'm serious about fixing the root cause instead of "plugging the hole" in each update on each computer.

We noticed that our WSUS content folder was growing out of control on the master and downstream replicas.  The decision was made to delete everything in the content folders on all WSUS servers and issue a wsusutil.exe RESET command on all WSUS servers as well as change every patch to UNAPPROVED on the master server.

Everything worked great very quickly on the master which appears to be functioning fine but the downstream replicas are stuck.  The CPU is maxed on a core and WSUS is running queries indefinately.  There is absolutely nothing in the wsus content folder on these replica servers now and we have not approved a single patch after setting them all back to unapproved.  What is going on and how do I fix this?

Here is what is running in SQL on SUSDB:

SUSDB.dbo.spResetStateMachineAndReEvaluate;1 This query is running

SUSDB.dbo.spGetRevisionInfo;1This query is blocked by the first one

SUSDB.dbo.spGetRevisionIdListForCache;1This query is blocked by the first one

The downstream replicas are also not able to sync with the master while this is going on now.

How do I fix the downstream replicas?

Standard problem with WSUS Cleanup Wizard timing out without removing any unnecessary updates. SBS2K8. WSUS 3. 6000+ unnecessary updates awaiting approval. Huge database. Unresponsive SQL server. Lot of people have this problem:
http://social.technet.microsoft.com/Forums/en-US/9724778f-c1a0-4d24-82e4-8b2d054257d6/wsus-hangs-on-cleanup-wizard-for-unused-updates-then-disconnects-from-console?forum=winserverwsus

Drives are regularly defragged in the background. Not gonna shut down the server and have down time just to fix this.

Tried the reindexing script from
http://technet.microsoft.com/en-us/library/dd939795(WS.10).aspx
, (don't copy the command line, it has weird characters in it, just type it in manually.) and it completes but it didn't improve anything.

Found this:
http://wsus.codeplex.com/releases/view/17612
and it also times out.

Found this comment:
For anyone who is getting Timeout Expired with obsolete updates. I have a solution! Use server name : "
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
" to connect with SQL managment studio. Once connected manually run "
exec spGetObsoleteUpdatesToCleanup
". This will return a list of obsolete ID's. For each one run "
exec spDeleteUpdate @localUpdateID=000000
", where 000000 is the ID. For myself I found the first ID in the list took a full 37 minutes to delete and then after that I could run the cleanup through the GUI as per usual.

by jjdacl on Apr 23 at 12:55 PM 

Found that you actually need to do:
USE SUSDB
GO
exec spGetObsoleteUpdatesToCleanup

And to connect in the first place, I had to hit Options, and select named pipe from the middle pull down. 

First delete took 6 minutes and memory has spiked up to almost 15GB in use out of 16GB physical. But the WSUS console (Update Services) still shows the same number of old updates. Failure? I don't think so: I'm running the cleanup wizard again and so far it isn't timing out... It has run over night, and has made some progress; the bar has moved perhaps 5%. 

So... My take is that the SQL server causes this problem when there is to much data, because the indexes are poorly designed (not because the indexes need to be re-indexed) causing the first query to time out, which causes the cleanup to fail. Once you get past that first deletion, and have everything loaded into memory, the cleanup tool can stay connected long enough to delete each unneeded update.

Next step will be to find a command line method, such as:
http://wsus.codeplex.com/releases/view/17612
and put it into the task scheduler like Microsoft should have done at the beginning to keep this from getting out of hand.

P.S. Lawrence Garvin, please do NOT reply to this; I have no need of your arrogance.