WSUS no longer working for any clients

[Sheridan]

We've run WSUS on our network for as long as I can remember, most recently on a 2008 R2 server. I noticed most of the Windows 7 client stopped reporting in a good few weeks ago. Nothing I tried on any of these machines (reseting the id, running the full wsus script to reset the components etc) seemed to make them connect to WSUS anymore - they simply showed up on the server as 'Not yet reported'

 

So I removed and reinstalled WSUS on the 2008 server - same result.

 

I then built a VM, installed Server 2012 R2 and installed WSUS on that, redirected the clients to the new server and same result again! And now WSUS on the new server cannot be accessed as it constantly comes up with the Reset Server Node error, even after deleting the file from the user profile that MS suggest as a fix.

 

So apart from the fact I can't get WSUS to even run properly on 2012, does anyone know if there was a Windows 7 update since maybe July/August that broke WSUS? We had ours setup to automatically authorise Critial/Security updates which I guess is what most of you do?

 

Other than that I can't see any way forward unless I a) ditch WSUS or b) start reimaging 100's of W7 PCs!

[mowgli82]

I've noticed a similar thing and tried much the same as you.... My console is still loading but I am having problems getting clients to report in.

[Sheridan]

Hmm,this is why I suspect a W7 update has broken something.

[truebluesteve]

Does the WSUS console come back alive after you run an iisreset command from Powershell?

[Sheridan]

Does the WSUS console come back alive after you run an iisreset command from Powershell?

 

I can get the console up (for a period of time anyway) by restarting the server - it crashes out pretty quickly after that but not at any specific time.

 

I can move wsus back to the 2008 R2 server as the console worked ok on that, the big problem is the clients not reporting. I know MS are pushing us to us W10 but the update mechanism in that is pretty unreliable with wsus as well!

 

Each client logs the error 'Windows Update Client failed to detect with error 0x80244010' and I can't run the Update diagnostics tool as it generates another error:

 

 

This does suggest an update killed WSUS at the client end.

Edited September 21, 2016 by Sheridan

[truebluesteve]

We have had WSUS issues here recently (with console too) and saw quite a number 13032 event ID's in the event logs of the WSUS server. These can be caused (apparently) by -

 

Unused updates and update revisions

Unneeded update files

Expired updates

 

There is a cleanup Wizard in the WSUS console that can lean them up if that is the issue. Some instructions -

 

Log on to the server as administrator.

Click Start, All Programs, Administrative tools and then Microsoft® Windows® Server Update Services.

In the Updates Services tree, expand the server that you want to manage and then click Options.

On the Options page, click Server Cleanup Wizard.

On the 'Welcome to the Server Cleanup Wizard' page, select all the following options to clean up:

Unused updates and update revisions

Computers not contacting the server

Unneeded update files

Expired updates

Superseded updates

Click Next to start the cleanup process.

When the process completes, click Finish.

Log on as administrator on the server in which the cleanup wizard was run.

Click Start, Run and then type iisreset and click OK.

[Sheridan]

We have had WSUS issues here recently (with console too) and saw quite a number 13032 event ID's in the event logs of the WSUS server. These can be caused (apparently) by -

 

Unused updates and update revisions

Unneeded update files

Expired updates

 

There is a cleanup Wizard in the WSUS console that can lean them up if that is the issue. Some instructions -

 

Log on to the server as administrator.

Click Start, All Programs, Administrative tools and then Microsoft® Windows® Server Update Services.

In the Updates Services tree, expand the server that you want to manage and then click Options.

On the Options page, click Server Cleanup Wizard.

On the 'Welcome to the Server Cleanup Wizard' page, select all the following options to clean up:

Unused updates and update revisions

Computers not contacting the server

Unneeded update files

Expired updates

Superseded updates

Click Next to start the cleanup process.

When the process completes, click Finish.

Log on as administrator on the server in which the cleanup wizard was run.

Click Start, Run and then type iisreset and click OK.

 

I've run the cleanup wizard on the original WSUS server and it didn't help the client connectivity. I ran it on the new server and it only removed a handful of updates as the WSUS database will have been pretty clean anyway.

[Sheridan]

Well, full reinstall of WSUS on a new server (again) and every single W7 client failing to update. All now logging:

 

2016-09-21 13:39:48:857 988 51c PT WARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200

2016-09-21 13:39:48:857 988 51c PT WARNING: PTError: 0x80244008

2016-09-21 13:39:48:857 988 51c PT WARNING: GetCookie_WithRecovery failed : 0x80244008

2016-09-21 13:39:48:857 988 51c PT WARNING: RefreshCookie failed: 0x80244008

2016-09-21 13:39:48:857 988 51c PT WARNING: RefreshPTState failed: 0x80244008

2016-09-21 13:39:48:857 988 51c PT WARNING: PTError: 0x80244008

2016-09-21 13:39:48:857 988 51c Report WARNING: Reporter failed to upload events with hr = 80244008.

 

I think the phrase is 'I'm stuffed' as searching for those error numbers doesn't offer anything that is a solution.

 

So I'll have to find a way to manually download critical updates and push them out a different way as wsus looks like a dead duck for me. Is anyone else manually applying update like this?

[KevinH]

WSUS on 2012 requires a GPO change from http://wsuservername to http://wsuservername:8530 as the port is different

 

On the 2012 server, two updates (3148812 and its replacement 3159706) broke WSUS in dramatic fashion, see second post on this page.

 

https://community.spiceworks.com/topic/1567653-heads-up-kb3148812-for-wsus-servers-and-replacement-kb3159706?page=5

[mowgli82]

@Sheridan, not the news I was hoping for....... wouldn't this indicate a client issue? Could it be the version of the Windows Update Agent on the clients?

[mowgli82]

I get the same 0x80070002 message, mine only seems to be affecting newly built workstations or workstations that have been off the network for a while, existing workstations are checking in normally. Mine is running on a server 2012 r2 box Edited September 21, 2016 by mowgli82

[mowgli82]

@Sheridan just found this on experts exchange "Your clientdiag error hr=0x80070002 is because it doesnt run on 64 bit systems, clientdiag is 32 bit only"

[Sheridan]

WSUS on 2012 requires a GPO change from http://wsuservername to http://wsuservername:8530 as the port is different

 

On the 2012 server, two updates (3148812 and its replacement 3159706) broke WSUS in dramatic fashion, see second post on this page.

 

https://community.spiceworks.com/topic/1567653-heads-up-kb3148812-for-wsus-servers-and-replacement-kb3159706?page=5

 

I set mine to port 80, so the connection is just to http://servername.

 

It seems to be likely an update broke the update client on all of my windows 7 machines as they were quite happily updating from the original wsus server for about 2 years. All of a sudden they all stopped. I've tried Wsus on 2008r2 and 2012r2 and tried every reset/reinstall of the update client and settings on the affected PCs. Short of reimaging the clients I have nowhere else to look!

 

Time to find an alternative as I've wasted so much time on this already.

[mowgli82]

If I browse to http://servername-01:8530/SimpleAuthWebService/SimpleAuth.asmx from the WSUS server that page displays correctly

 

If I browse from a client I get this:

 

 

Any got any ideas?

[mowgli82]

If I browse to the site from Chrome it works fine, just IE11 thats not working.

[round2it]

My wsus clients are doing the same maybe i need to rebuild a wsus server again

[Guest kiest90]

I had the same issue. Running the command at the below link seems to resolve it.

 

https://social.technet.microsoft.com/Forums/en-US/7b04aa7a-8580-4026-be09-9d71093a37ac/wsus-stopped-working-after-may-2016-update-round?forum=ConfigMgrCompliance

[Sheridan]

I can occasionally get the console working (using a restart or the /postinstall command) but my clients refuse to connect.

 

I'm looking at a monthly batch of updates deployed by scripting now.

[mowgli82]

ok, I think mine might be image related or something.. If I do an initial a check via internet it then seems to contact the WSUS server on the next round and work correctly......

[Sheridan]

Yeah I think an update to outr W7 clients has broken it, but I've yet to find out which one!

[KevinH]

This may help some of you, or none of you, but probably worth a look.

 

Windows Update Error 80072ee2 (WSUS) - Scott Breen

 

The author has run into WSUSPool memory exhaustion as an issue - perhaps a peek at the relevant logs on the server is in order?

[Sheridan]

This may help some of you, or none of you, but probably worth a look.

 

Windows Update Error 80072ee2 (WSUS) - Scott Breen

 

The author has run into WSUSPool memory exhaustion as an issue - perhaps a peek at the relevant logs on the server is in order?

 

I'd seen something similar so I've already increased to limit on my server to 8gb. I've now gone back to Wsus 3.0 on Server 2008R2 and its still not working. Oddly though, I seem to have around 1/6th of the clients reporting in - the others have not yet reported in. Theres no logic to this as in a room of 30 PCs (all created from the same sysprep'd image and on the same hardware) I have maybe 3-4 reporting in!

[jonbd]

WSUS updates to Windows 7 clients stopped working for me in the last few weeks as well. Installing KB3050265 on Windows 7 clients seems to have sorted the problem out here after trying numerous other things

[Oaktech]

You haven't got a proxy wormed it's way into the clients somehow? can you run netsh winhttp show proxy and check that?

[Sheridan]

WSUS updates to Windows 7 clients stopped working for me in the last few weeks as well. Installing KB3050265 on Windows 7 clients seems to have sorted the problem out here after trying numerous other things

 

Out of curiosity how did you deploy this? My Wsus clients register in the console but never report in so I'd have to use a GPO to dish this out.