If you have Event ID: 364 in Application Event Log related to Windows Server Update Services (WSUS) can’t download some updates, like this one:

WSUS Event 364

Then you are lucky by reading this article, because there is a workaround for this nightmare:

This error happens because of some proxies or routers (that maybe not in your internal environment, it might be in the ISP or any place in the way to Microsoft Update Servers) doesn’t support the ancient 10 years old HTTP 1.1 Protocol used by BITS service. The workaround is to configure BITS with a command by connecting to WSUS Database with SQLCMD.exe tool as following steps (If you have SQL 2012 installed in the WSUS Server (As the command to connect to a named pipe changed in SQL 2012) :

  • Install both of the above tools.
  • In a command prompt, navigate to C:\Program Files\Microsoft SQL Server\90\Tools\Binn\ and run the following command:
    exe -S \\.\pipe\MICROSOFT##WID\tsql\query -E -b -Q “USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1”
  • If everything works ok, you will see the following result:

    C:\Program Files\Microsoft SQL Server\90\Tools\Binn>SQLCMD.exe -S \\.\pipe\mssql
    $microsoft##ssee\sql\query -E -b -Q “USE SUSDB update tbConfigurationC set BitsD
    Changed database context to ‘SUSDB’.

    (1 rows affected)

  • Restart WSUS Service and initiate a Synchronization Process from Configuration Manager or from WSUS if you don’t have SCCM

This solution is described by Microsoft in this TechNet Article (but with another tool called osql.exe that didn’t work with new WSUS Version):


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s