Windows update error 80072EE2 connecting to WSUS

[phreak]

We have a new laptop we are trying to deploy on our network HP elitebook 8440p's with Windows 7 Pro 64-bit. When connected straight out to the outside world they do windows updates fine. However, when I point them to my internal WSUS server they come back with the error code 80072EE2. The WSUS server itself appears to work for all other computers in the domain apart from this new model. I have tried rebuilding windows 7 Pro from scratch. I have also checked the registry for any vendor WSUS servers and there are non apart from mine. We are not running any proxy to connect to the server. We have eliminated Firewall and any security software from the equation. Tried with and without AV, as well as fresh build with no AD ever installed. Tried with the firewall on and with it off. Also connected the laptop directly to the network the WSUS server was on with no luck. Checked the laptops for any spyware/malware and as I said, have rebuilt them from scratch while ensuring that any media connected was clean. So that has been ruled out. Registered the following dlls: oleaut32.dll, jscript.dll, vbscript.dll, msxml.dll, softpub.dll, wintrust.dll, initpki.dll, cryptdlg.dll Tried changing the MTU of the LAN card. Also rolled back the driver to an older version. Tried running MS Fixit (both the newer version as well as the older version that allows you to run it in aggressive mode). Same. Tried installing the latest version of Windows update agent. Also tried the following Start > type cmd in start search > right click “run as administrator”. Ø Copy and paste the command below as given. net stop wuauserv cd %systemroot% ren SoftwareDistribution SoftwareDistribution.old net start wuauserv net stop bits - The BITS service is not started (message) net start bits net stop cryptsvc cd %systemroot%\system32 ren catroot2 catroot2.old - net start cryptsvc regsvr32 Softpub.dll /s regsvr32 Wintrust.dll /s regsvr32 Initpki.dll /s regsvr32 Mssip32.dll /s Ø Restart the computer. Success, Windows update now working. No joy. I can see it make the connection through my network and I can see it come up on the WSUS server under computers, however it just never seems to actually get past that. Also tried installing the windows 7 64bit server update readiness tool. Here is my Windowsupdate.log

 

2016-01-29 15:35:50:634 916 b84 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2016-01-29 15:35:50:634 916 b84 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://172.16.8.21:8530/ClientWebService/client.asmx 2016-01-29 15:38:16:182 916 b84 Misc WARNING: Send failed with hr = 80072ee2. 2016-01-29 15:38:16:182 916 b84 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2016-01-29 15:38:16:182 916 b84 Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2 2016-01-29 15:38:16:182 916 b84 PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0 2016-01-29 15:38:16:182 916 b84 PT + Caller provided credentials = No 2016-01-29 15:38:16:182 916 b84 PT + Impersonate flags = 0 2016-01-29 15:38:16:182 916 b84 PT + Possible authorization schemes used = 2016-01-29 15:38:16:182 916 b84 PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200 2016-01-29 15:38:16:182 916 b84 PT WARNING: PTError: 0x80072ee2 2016-01-29 15:38:16:182 916 b84 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2 2016-01-29 15:38:16:182 916 b84 PT WARNING: Sync of Updates: 0x80072ee2 2016-01-29 15:38:16:182 916 b84 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2 2016-01-29 15:38:16:182 916 b84 Agent * WARNING: Failed to synchronize, error = 0x80072EE2 2016-01-29 15:38:16:182 916 b84 Agent * WARNING: Exit code = 0x80072EE2 2016-01-29 15:38:16:182 916 b84 Agent ********* 2016-01-29 15:38:16:182 916 b84 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2016-01-29 15:38:16:182 916 b84 Agent ************* 2016-01-29 15:38:16:182 916 b84 Agent WARNING: WU client failed Searching for update with error 0x80072ee2 2016-01-29 15:38:16:213 916 588 AU >>## RESUMED ## AU: Search for updates [CallId = {EDED43F9-1E65-4EE2-ABC6-8ECBD9F69190}] 2016-01-29 15:38:16:213 916 588 AU # WARNING: Search callback failed, result = 0x80072EE2 2016-01-29 15:38:16:213 916 588 AU # WARNING: Failed to find updates with error code 80072EE2 2016-01-29 15:38:16:213 916 588 AU ######### 2016-01-29 15:38:16:213 916 588 AU ## END ## AU: Search for updates [CallId = {EDED43F9-1E65-4EE2-ABC6-8ECBD9F69190}] 2016-01-29 15:38:16:213 916 588 AU #############

[dapaulio]

Can you check the registry key on the symptomatic computer has all the server settings you expect it to be

HKLM/SOFTWARE/Policies/Microsoft/Windows/WindowsUpdate– the values WUServer
WUStatusServer

[phreak]

Hi there,

 

Yes, I can confirm that the server setting I would expect it to be. Have also checked it against another machine that does work.

[PyROm]

From memory this happens because windows update was designed with a maximum amount of catalogue data it can transfer per session, with so many updates in windows updates now it exceeds this limit. It will download so much then error. If you keep hitting retry it will eventually work from then on (it resumes download rather then restarts), after imaging it takes our laptops about 4 attempts before it runs successfully.

[phreak]

An interesting problem you have described there for sure, but I am afraid I have sat there all day constantly trying again and it always just comes back with the error

[PyROm]

Ah, sorry, I was thinking of 80244010.

[dapaulio]

can you confirm it is win 7 SP1?

Try:wuauclt /resetauthorization /detectnow

 

The error like alway WU updates error messages seem very ambigious.

[phreak]

Yes. I can confirm that it is Windows 7 Pro SP1 (64bit if that is of any note).

 

I tried Wuauclt but it doesn't seem to do anything and when I go into windows update again, same error.

[free780]

Is the ip of the wsus server in the proxy exceptions?

[phreak]

We do not use proxy.

Also, I have tried disabling the firewall on the laptops. Still the same.

[phreak]

On another note. I have also today tried allowing certain IP addresses through the main firewall to allow them to get updates from MS directly. That works ok. So my theory about network drivers possibly having issue with one part of my infrastructure was debunked.

[phreak]

As a side test I am going to put WSUS on another server on my network and try pointing them to that to see if they can update. I'll let you know how that gets on.

[dapaulio]

Would be interesting to know the outcome. You got a really annoying problem there

[PyROm]

Do you have ipv6 enabled? I believe this has caused us problems in past with windows update.

[phreak]

Strangeness abound. My new server won't allow anyone to pickup updates at all it seems despite me installing them exactly as the notes say. Just getting a timeout error on it.

So just trying what PyROm suggested and turning off IPv6 and then back to trying to figure out why my new one will not allow updates from it.

 

But as it is, still having the same old issue on the original one.

[phreak]

Tried disabling IPv6. Still the same I am afraid.

 

When I started tweaking my new Wsus server it started presenting even more strange errors. So for that one I have removed and now re-installing wsus from scratch to hopefully get it working. Once I can confirm it works from another pc I will try it from these problematic laptops.

[phreak]

Also, just for curiosity sake, I am going to upgrade one of these laptops to windows 8.1 and see if that then allows me to get updates from my current Wsus server

[dapaulio]

Out of curiosity try spoofing your mac address by right clicking on your network connection, configure, advanced, locally administered mac address and set to 123456789000

This advanced setting may be called something different depending on the vendor of your nic. Mine is a broad com wireless. My wired is marvell and is called physical address.