Fatal Error: Cannot start service MSSQL$MICROSOFT##WID on computer '.'.

The specified account has not been given login as a service right.

Now, I'm assuming they create that goofy named account to run the instance of the internal db, but they have apparently forgot to add automation to set the right to logon as a service. This is a bug, I have the same results on two different server 2012 R2 installs. Is there a manual fix for this somewhere I can try? Very irritating.

This in regards to the above link.  I tried what was recommended and it still pops errors.  Is there a resolution for this without reinstalling the OS?

I've got a fresh WSUS role deployed on a 2012 server, (so WSUS 6) I've got a GPO pointing my clients to a target group of computers and they're even pulling updates that are approved.
However even with all of that, WSUS still shows "This computer has not reported status yet"

Even more confusing, is if my Windows 7 Enterprise laptop pulls down the updates, WSUS says "Updates Installed / Not applicable - 28" for that machine, and yet STILL says This computer has not reported status yet. (See screenshot example at https://i.imgur.com/o3Nq2Sc.jpg)

I'm stumped. As far as I can see, windowsupdate.log shows no errors. The registry keys for all the computers all show that the update point is the WSUS server I pointed it to, and of course, they're able to pull updates (but not report back on them)
I've even asked out network team to monitor exactly what's happening between a client and a server, and not a single block is in place. These have free reign.
I'm completely stumped and I have no idea where else to go. Everything looks right from the client side, but the server just isn't reflecting it.
I've tried the standard wuauclt /resetauthorization /detectnow commands to no avail.

I've also tried deleting HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SuSClientID and restarting the Windows update service but with no luck

I'll go pull the windowsupdate.log file from my laptop now to show you what's going on, but there's no errors that I can see. Any assistance appreciated

(If you want another oddity in this mix, every client, EXCEPT the Windows 8 client is reporting to the correct URL)

I've also confirmed that the simpleauth URL is responding correctly. http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx

Edit: Here's an excerpt of the WindowsUpdate.log (With company sensitive names redacted) from a Server 2008 R2 machine that shows what my laptop does, i.e. updates available for install, all the right URLs, no Errors and still shows "This computer has not reported status yet"

2015-06-17  20:14:03:822    9168    19c4    Misc    ===========  Logging initialized (build: 7.6.7600.320, tz: -0500)  ===========
2015-06-17  20:14:03:822    9168    19c4    Misc      = Process: c:\Program Files\Microsoft Security      Client\MpCmdRun.exe
2015-06-17  20:14:03:822    9168    19c4    Misc      = Module: C:\Windows\system32\wuapi.dll
2015-06-17  20:14:03:822    9168    19c4    COMAPI  -------------
2015-06-17  20:14:03:822    9168    19c4    COMAPI  -- START --  COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2015-06-17  20:14:03:822    9168    19c4    COMAPI  ---------
2015-06-17  20:14:03:822    9168    19c4    COMAPI  <<-- SUBMITTED -- COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2015-06-17  20:14:03:822    1004    1f5c    Agent   *************
2015-06-17  20:14:03:822    1004    1f5c    Agent   ** START **  Agent: Finding updates [CallerId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2015-06-17  20:14:03:822    1004    1f5c    Agent   *********
2015-06-17  20:14:03:822    1004    1f5c    Agent     * Online = Yes; Ignore download priority = No
2015-06-17  20:14:03:822    1004    1f5c    Agent     * Criteria = "(IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains 'a38c835c-2950-4e87-86cc-6911a52c34a3' and CategoryIDs contains 'e0789628-ce08-4437-be74-2495b842f43b')"
2015-06-17  20:14:03:822    1004    1f5c    Agent     * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-06-17  20:14:03:822    1004    1f5c    Agent     * Search Scope = {Machine}
2015-06-17  20:14:03:932    1004    1f5c    PT  WARNING: Cached cookie has expired or new PID is available
2015-06-17  20:14:03:932    1004    1f5c    PT  Initializing simple targeting cookie, clientId = d5cae633-78ea-4f94-8eb7-df3f5b5b39fa, target group = Test-Dev, DNS name = testserver.contoso.com
2015-06-17  20:14:03:932    1004    1f5c    PT    Server URL = http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx
2015-06-17  20:14:04:010    1004    1f5c    PT  +++++++++++  PT: Starting category scan  +++++++++++
2015-06-17  20:14:04:010    1004    1f5c    PT    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusserver:8530/ClientWebService/client.asmx
2015-06-17  20:14:04:212    1004    1f5c    PT  +++++++++++  PT: Synchronizing server updates  +++++++++++
2015-06-17  20:14:04:212    1004    1f5c    PT    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusserver:8530/ClientWebService/client.asmx
2015-06-17  20:14:04:228    1004    1f5c    PT  WARNING: Cached cookie has expired or new PID is available
2015-06-17  20:14:04:228    1004    1f5c    PT  Initializing simple targeting cookie, clientId = d5cae633-78ea-4f94-8eb7-df3f5b5b39fa, target group = Test-Dev, DNS name = testserver.contoso.com
2015-06-17  20:14:04:228    1004    1f5c    PT    Server URL = http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx
2015-06-17  20:14:04:368    1004    1f5c    Agent     * Found 0 updates and 4 categories in search; evaluated appl. rules of 34 out of 89 deployed entities
2015-06-17  20:14:04:462    1004    1f5c    Agent   *********
2015-06-17  20:14:04:462    1004    1f5c    Agent   **  END  **  Agent: Finding updates [CallerId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2015-06-17  20:14:04:462    1004    1f5c    Agent   *************
2015-06-17  20:14:04:462    9168    203c    COMAPI  >>--  RESUMED  -- COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2015-06-17  20:14:04:462    9168    203c    COMAPI    - Updates found = 0
2015-06-17  20:14:04:462    9168    203c    COMAPI  ---------
2015-06-17  20:14:04:462    9168    203c    COMAPI  --  END  --  COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2015-06-17  20:14:04:462    9168    203c    COMAPI  -------------
2015-06-17  20:14:09:472    1004    1f5c    Report  REPORT EVENT: {17BBEE6C-9FC3-420E-9073-4A8315BE8217}    2015-06-17 20:14:04:462-0500    1   147 101 {00000000-0000-0000-0000-000000000000}  0   0   System Center Endpoint Protecti Success Software Synchronization    Windows Update Client successfully detected 0 updates.
2015-06-17  20:14:09:472    1004    1f5c    Report  CWERReporter finishing event handling. (00000000)

Second Edit - Here's an earlier log file for this machine which shows the Windows Update process rather than just SCEP

2015-06-17  11:29:27:918    1004    12c4    AU  #############
2015-06-17  11:29:27:918    1004    12c4    AU  ## START ##  AU: Search for updates
2015-06-17  11:29:27:918    1004    12c4    AU  #########
2015-06-17  11:29:27:918    1004    12c4    AU  <<## SUBMITTED ## AU: Search for updates [CallId = {10F1A1F9-C6DF-4CA2-878D-FAFDCAEC6352}]
2015-06-17  11:29:27:918    1004    1c74    Agent   *************
2015-06-17  11:29:27:918    1004    1c74    Agent   ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-06-17  11:29:27:918    1004    1c74    Agent   *********
2015-06-17  11:29:27:918    1004    1c74    Agent     * Online = Yes; Ignore download priority = No
2015-06-17  11:29:27:918    1004    1c74    Agent     * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2015-06-17  11:29:27:918    1004    1c74    Agent     * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-06-17  11:29:27:918    1004    1c74    Agent     * Search Scope = {Machine}
2015-06-17  11:29:27:933    1004    1c74    Setup   Checking for agent SelfUpdate
2015-06-17  11:29:27:933    1004    1c74    Setup   Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
2015-06-17  11:29:27:964    1004    1c74    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2015-06-17  11:29:27:980    1004    1c74    Misc     Microsoft signed: NA
2015-06-17  11:29:27:980    1004    1c74    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPA20D.tmp with dwProvFlags 0x00000080:
2015-06-17  11:29:28:011    1004    1c74    Misc     Microsoft signed: NA
2015-06-17  11:29:28:011    1004    1c74    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2015-06-17  11:29:28:011    1004    1c74    Misc     Microsoft signed: NA
2015-06-17  11:29:28:074    1004    1c74    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2015-06-17  11:29:28:074    1004    1c74    Misc     Microsoft signed: NA
2015-06-17  11:29:28:152    1004    1c74    Setup   Determining whether a new setup handler needs to be downloaded
2015-06-17  11:29:28:152    1004    1c74    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe with dwProvFlags 0x00000080:
2015-06-17  11:29:28:152    1004    1c74    Misc     Microsoft signed: NA
2015-06-17  11:29:28:152    1004    1c74    Setup   SelfUpdate handler update NOT required: Current version: 7.6.7600.320, required version: 7.6.7600.320
2015-06-17  11:29:28:152    1004    1c74    Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2015-06-17  11:29:28:932    1004    1c74    Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2015-06-17  11:29:28:932    1004    1c74    Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2015-06-17  11:29:28:947    1004    1c74    Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2015-06-17  11:29:28:947    1004    1c74    Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2015-06-17  11:29:28:994    1004    1c74    Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2015-06-17  11:29:28:994    1004    1c74    Setup   SelfUpdate check completed.  SelfUpdate is NOT required.
2015-06-17  11:29:31:570    1004    1c74    PT  +++++++++++  PT: Synchronizing server updates  +++++++++++
2015-06-17  11:29:31:570    1004    1c74    PT    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusserver:8530/ClientWebService/client.asmx
2015-06-17  11:29:31:586    1004    1c74    PT  WARNING: Cached cookie has expired or new PID is available
2015-06-17  11:29:31:586    1004    1c74    PT  Initializing simple targeting cookie, clientId = d5cae633-78ea-4f94-8eb7-df3f5b5b39fa, target group = Test-Dev, DNS name = testserver.contoso.com
2015-06-17  11:29:31:601    1004    1c74    PT    Server URL = http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx
2015-06-17  11:30:47:738    1004    1c74    PT  +++++++++++  PT: Synchronizing extended update info  +++++++++++
2015-06-17  11:30:47:738    1004    1c74    PT    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusserver:8530/ClientWebService/client.asmx
2015-06-17  11:30:55:336    1004    1c74    Agent     * Added update {B9D30936-8E3B-4728-988E-78CC39AEC684}.202 to search result
2015-06-17  11:30:55:336    1004    1c74    Agent     * Added update {6C8C0AC4-F40B-4E4B-AA83-1694FE0DBEC2}.201 to search result
2015-06-17  11:30:55:336    1004    1c74    Agent     * Added update {9A3A9B37-D93D-4982-93FB-A9271DBDFAC9}.203 to search result
2015-06-17  11:30:55:336    1004    1c74    Agent     * Added update {726B8D92-D183-4A25-9588-D45D0DC86E5F}.202 to search result
2015-06-17  11:30:55:336    1004    1c74    Agent     * Added update {6D155681-7172-4DD7-9341-46D42EC794F5}.202 to search result
2015-06-17  11:30:55:336    1004    1c74    Agent     * Added update {84BAF93F-3645-4EF2-887A-D1E5E883ADC7}.201 to search result
2015-06-17  11:30:55:336    1004    1c74    Agent     * Added update {922DE694-C7E6-42AC-8738-95F5A8E2390E}.201 to search result
2015-06-17  11:30:55:352    1004    1c74    Agent     * Found 7 updates and 75 categories in search; evaluated appl. rules of 6102 out of 8732 deployed entities
2015-06-17  11:30:55:352    1004    1c74    Agent   *********
2015-06-17  11:30:55:352    1004    1c74    Agent   **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-06-17  11:30:55:352    1004    1c74    Agent   *************
2015-06-17  11:30:55:461    1004    1f98    AU  >>##  RESUMED  ## AU: Search for updates [CallId = {10F1A1F9-C6DF-4CA2-878D-FAFDCAEC6352}]
2015-06-17  11:30:55:461    1004    1f98    AU    # 7 updates detected
2015-06-17  11:30:55:461    1004    1f98    AU  #########
2015-06-17  11:30:55:461    1004    1f98    AU  ##  END  ##  AU: Search for updates [CallId = {10F1A1F9-C6DF-4CA2-878D-FAFDCAEC6352}]
2015-06-17  11:30:55:461    1004    1f98    AU  #############
2015-06-17  11:30:55:461    1004    1f98    AU  Successfully wrote event for AU health state:0
2015-06-17  11:30:55:461    1004    1f98    AU  Featured notifications is disabled.
2015-06-17  11:30:55:461    1004    1f98    AU  AU setting next detection timeout to 2015-06-18 12:36:45
2015-06-17  11:30:55:461    1004    1f98    AU  Setting AU scheduled install time to 2015-06-21 08:00:00
2015-06-17  11:30:55:461    1004    1c74    Report  REPORT EVENT: {A1CE48DA-DF3C-422D-9208-0AAD4D46E652}    2015-06-17 11:30:55:352-0500    1   147 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Software Synchronization    Windows Update Client successfully detected 7 updates.
2015-06-17  11:30:55:461    1004    1c74    Report  REPORT EVENT: {FEA8676C-D6FD-4A5F-B349-6B4DCC2CC9DD}    2015-06-17 11:30:55:352-0500    1   156 101 {00000000-0000-0000-0000-000000000000}  0   0   AutomaticUpdates    Success Pre-Deployment Check    Reporting client status.
2015-06-17  11:30:55:461    1004    1f98    AU  Successfully wrote event for AU health state:0
2015-06-17  11:30:55:461    1004    1c74    Report  CWERReporter finishing event handling. (00000000)
2015-06-17  11:30:55:477    1004    1f98    AU  Successfully wrote event for AU health state:0
2015-06-17  11:31:00:460    1004    1c74    Report  CWERReporter finishing event handling. (00000000)

Francisco Mercado Jr.

Hello

I have WSUS configured on win 2012 which is also domain controller. I have configured GPO policy for my domain with windows update with specific settings. I can see that policy propagated to my windows7 client (confirmed by checking local windows update settings -> those are propagated from by GPO).

But on WSUS i do never see (already few days) any PC in Computers  - so no computers ever connected to use WSUS service. Also all WSUS reports shows zero computers.

I have tried wuauclt.exe /detectnow on windows7 - but without any result.

How to force windows7 station to use specific WSUS for updates ? And how to confirm that on windows7 station ?

Thanks,

Michal

Hi We have to setup a New WSUS server in DMZ 

I wanted to check the following:

Can we deploy Server 2012 R2 / WSUS v6  and make it the Upstream server for 2 of our Windows 2008 (WSUS 3.0) server

We wish to Use the new 2012 R2 server to just get Updates from MS and then Have the existing WSUS 3.0 servers get it from the Upstream Server in Autonomous mode.

I am hoping we only need to open following ports on firewall (80/443) between the 2 existing WSUS 3.0 to the new 2012R2 WSUS 

I have installed Windows 2012 R2 on a machine with 8 GB of memory and have activated the WSUS role. I have successfully built the WSUS database with the updates that I would like to push out to Windows 7 client machines. I have set up a LAN that both the WSUS server and the clients are connected to. Each client has a registry hack that points it to the WSUS server. When I try to update a client it will successfully communicate with the WSUS server and inform me, via Windows update, that it needs x number of updates but when I try to have the client download and install those updates I get aWindowsUpdate error 80244020 on the client. According to Microsoft that error is like anHTTP 500 error - the server does not support the functionality required to fulfill the request. Can anyone assist me in figuring out what the problem is. I am using the port 8530 and that is what the client is listening on. I also have configured the server firewall to allow traffic on that port.

I used to run WSUS under Windows 2003 server with NO problems at all. It has only been since I tried to use Windows 2012 R2 and WSUS that I am now having a problem which I DESPERATELY need to fix.

Thank you in advance!!!!

Hi

Can any one post real time scenarios and solution in production environment of sccm2012

G.V.Ramana

We have about 200 servers and regularly some servers don't report anymore.

However, the Last Contact is from today.

I have a workaround :

1. Stop the Windows Update service
2. Remove the %SystemRoot%\SoftwareDistribution folder
3. Start the Windows Update service

However, I wish to fix the issue instead of constantly using the workaround.

We have only one WSUS server.

Servers which do not report are running Windows 2008 or windows 2012.

Dear all,
Recently, I encountered a bad problem from my WSUS server and I found out lots of computers do not report to WSUS properly.

Here's the log.

From these log, what should I do in WSUS console and get them back to be reported properly?  Please advise.

During the investigation, I found out service status as below.
BITS - Started , automatic (Delayed Start)
Windows update - stopped, manual

But once I sent the command of "wuauclt.exe /resetauthorization /detectnow", the windows update will be started again.

May I ask if these 2 services supposed to be "started" automatically?

Thanks alot

Hi,
I'm currently experiencing a strange issue with updates installed on clients with WSUS.
Currently WSUS setting is "3-Auto download and notify for install" so when users poweroff the PC, the "Install Updates and Shut Down" message appear.The problem is that after reboot, the Updates process fails and the installation process enters in a "loop".
If I manually install upadates I have no problems.
The only difference seems to be that by leaving Windows installing updates (WSUS policy), the user is logged off and then the update process starts, while if I manually install updates the user is still logged on during instalaltion.

Since the error is the "classic" 0x80070005,Access Denied it seems to be a permission issue.

Before posting hundred lines of logs could someone tell me which user context is involved during the 2 ways to install updates?

Many thanks and best regards,

Andrea

Good Afternoon All,

Myself and a colleague have just thought we still have a few 2003 servers still running. I know its not the best but these run some of our WSUS services for selected applications. I was wondering with 2003 becoming end of line will this stop the WSUS server from downloading updates from the catalog for newer operating systems such as Windows 7 and above. I can not seem to see anything anywhere to indicate this apart from migrate away as soon as possible.

In a Alpha, Beta, and Production environments, What are the best practices for deploying WSUS? After patch Tuesday, we would like to push updates to Alpha. The next week we would like to push updates to Beta. and the last week of the month push updates to our Prod servers. Also, all the servers can't reboot at the same time per environment. Can I do this with one WSUS server or should I set up one WSUS server per environment and manually approve the updates? I would like to automate as much as possible.   

Input is greatly appreciated!

-Zach 

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 >Operationalyou 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 register important DLLs required for the changes to take place with following commands:

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.

21. 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.

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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hello

I need some serious assistance wrt WSUS.

I have WSUS 3.0 SP2 running on Server 2008 SP2.

My Sync to Microsoft Update fails (also fails via Server Configuration Setup).

I have tried to re-install.

Re-install IIS, WSUS and ReportViewer. And start with new Database. Then the sync works but no clients can report to WSUS.

I then installed WSUS-KB2734608 and then the clients start reporting in, but the sync fails.

The error I get is: Webexception: The underlying connection was closed. Could not establish trust relationship for the SSL/TLS secure channel. Then something about: Remote certificate is invalid according to the validation procedure.

But I have never used SSL on Wsus.

I have checked permissions on server. Proxy settings. Reboots. Services restarts. Wsusutil.exe resets.

I also see download failed on all updates. I only approved a few to test and see if they download. But to no avail.

I think the whole WSUS is broken at the moment and I don't know what else to troubleshoot and what to do next to get the Sync to microsoft working and getting the updates to download.

Please assist. Any tip or advice would be greatly appreciated.

Please ask if anything above is unclear or confusing.

Kind Regards