Fix Error 80072EE2 with Windows Update

Project Description

Customer needed help with fixing the error 80072EE2 with Windows Update that started to occur in February 2016 on these 2 sets of hardware:

Hardware Set 1


Hardware Set 2


The installation process looked like this:


Windows Update error 80072EE2

Windows Update error 80072EE2



Windows Updates before error 80072EE2

Windows update history before error 80072EE2 starts to appear



Below is the end of C:\Windows\WindowsUpdate.log file showing error 80072ee2. It looks like Windows Update Agent is having basic connectivity issues.

2016-02-26	17:22:18:626	 912	4e4	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2016-02-26	17:22:18:626	 912	4e4	Misc	 Microsoft signed: NA
2016-02-26	17:22:18:626	 912	4e4	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP20C6.tmp with dwProvFlags 0x00000080:
2016-02-26	17:22:18:626	 912	4e4	Misc	 Microsoft signed: NA
2016-02-26	17:22:18:626	 912	4e4	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2016-02-26	17:22:18:626	 912	4e4	PT	  + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2016-02-26	17:22:40:856	 912	4e4	Misc	WARNING: Send failed with hr = 80072ee2.
2016-02-26	17:22:40:856	 912	4e4	Misc	WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2016-02-26	17:22:40:856	 912	4e4	Misc	FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
2016-02-26	17:22:40:856	 912	4e4	PT	  + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2016-02-26	17:22:40:856	 912	4e4	PT	  + Caller provided credentials = No
2016-02-26	17:22:40:856	 912	4e4	PT	  + Impersonate flags = 0
2016-02-26	17:22:40:856	 912	4e4	PT	  + Possible authorization schemes used = 
2016-02-26	17:22:40:856	 912	4e4	PT	WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2016-02-26	17:22:40:856	 912	4e4	PT	WARNING: PTError: 0x80072ee2
2016-02-26	17:22:40:856	 912	4e4	PT	WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
2016-02-26	17:22:40:856	 912	4e4	PT	WARNING: Sync of Updates: 0x80072ee2
2016-02-26	17:22:40:856	 912	4e4	PT	WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2016-02-26	17:22:40:856	 912	4e4	Agent	  * WARNING: Failed to synchronize, error = 0x80072EE2
2016-02-26	17:22:40:856	 912	4e4	Agent	  * WARNING: Exit code = 0x80072EE2
2016-02-26	17:22:40:856	 912	4e4	Agent	*********
2016-02-26	17:22:40:856	 912	4e4	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-02-26	17:22:40:856	 912	4e4	Agent	*************
2016-02-26	17:22:40:856	 912	4e4	Agent	WARNING: WU client failed Searching for update with error 0x80072ee2
2016-02-26	17:22:40:872	 912	7e0	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {F5C9E1BC-9750-4086-8EF2-73697E16D5EC}]
2016-02-26	17:22:40:872	 912	7e0	AU	  # WARNING: Search callback failed, result = 0x80072EE2
2016-02-26	17:22:40:872	 912	7e0	AU	  # WARNING: Failed to find updates with error code 80072EE2
2016-02-26	17:22:40:872	 912	7e0	AU	#########
2016-02-26	17:22:40:872	 912	7e0	AU	##  END  ##  AU: Search for updates [CallId = {F5C9E1BC-9750-4086-8EF2-73697E16D5EC}]
2016-02-26	17:22:40:872	 912	7e0	AU	#############
2016-02-26	17:22:40:872	 912	7e0	AU	Successfully wrote event for AU health state:0
2016-02-26	17:22:40:872	 912	7e0	AU	AU setting next detection timeout to 2016-02-27 06:22:40
2016-02-26	17:22:40:872	 912	7e0	AU	Setting AU scheduled install time to 2016-02-27 11:00:00
2016-02-26	17:22:40:872	 912	7e0	AU	Successfully wrote event for AU health state:0
2016-02-26	17:22:40:872	 912	7e0	AU	Successfully wrote event for AU health state:0
2016-02-26	17:22:40:872	 912	7b0	AU	Getting featured update notifications.  fIncludeDismissed = true
2016-02-26	17:22:40:872	 912	7b0	AU	No featured updates available.
2016-02-26	17:22:45:864	 912	4e4	Report	REPORT EVENT: {3D890A38-845F-412A-9B91-A49798213196}	2016-02-26 17:22:40:856-0800	1	148	101	{00000000-0000-0000-0000-000000000000}	0	80072ee2	AutomaticUpdates	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80072ee2.
2016-02-26	17:22:45:864	 912	4e4	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
2016-02-26	17:22:45:864	 912	4e4	Report	WER Report sent: 7.6.7600.320 0x80072ee2 00000000-0000-0000-0000-000000000000 Scan 101 Unmanaged
2016-02-26	17:22:45:864	 912	4e4	Report	CWERReporter finishing event handling. (00000000)


Completion Notes

The problem was eventually narrowed down to how Windows Update Agent 7.6.7600.320 interacts with a particular model of a router - Telus model # T1200H, firmware version T1200H-31.128L.05.

The error occurs when a Windows systems is connected by a CAT5 cable to the T1200H router, which is connected to an ISP via a modem in an additional unit.

Connecting the system to a modem directly (via a hub) solves the issue. Also, using a different router (in our case Linksys WRT300N) solves the issue as well.

Router Notes

It is difficult to say whether customer has a faulty router. We have tried, unsuccessfully, to play with router settings to see if the problem goes away.

We observed that trying to do a Factory Reset on the router does fix the problem temporarily and only for a short time about 1 minute after router reboot. Then, the connectivity problem resurfaces again.

Summary

A workaround for error 80072ee2 with Windows Update in our case was to either connect to the Internet directly, or use another router.

T1200H router we use may or may not be faulty. Other operating systems (Mac OSX, FreeBSD, and various flavors of Linux) do not show any connectivity / update issues when connected via both routers.

Windows Update Agent version 7.6.7600.320 cannot connect to an update server through a factory-reset T1200H router after approximately 1 minute since router reboot. However, a brief period of connectivity (approx. 1 min) was observed immediately after router reboot.

It looks like Windows Update Agent 7.6.7600.320 may have an issue here, since we know that updates prior to agent update itself work reliably via the same router.

An additional test for a fully up-to-date Windows 7 x64 system with a newer version of Windows Update Agent 7.6.7601.19116 shows the same error and the same problem when connecting via T1200H router:

2016-02-28	16:59:02:736	 272	148	AU	Triggering AU detection through DetectNow API
2016-02-28	16:59:02:736	 272	148	AU	Triggering Online detection (interactive)
2016-02-28	16:59:02:736	 272	abc	AU	#############
2016-02-28	16:59:02:736	 272	abc	AU	## START ##  AU: Search for updates
2016-02-28	16:59:02:736	 272	abc	AU	#########
2016-02-28	16:59:02:736	 272	abc	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {6DC5ABE7-F823-4032-8BAD-F172DFBC13B3}]
2016-02-28	16:59:02:736	 272	33c	Agent	*************
2016-02-28	16:59:02:736	 272	33c	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-02-28	16:59:02:736	 272	33c	Agent	*********
2016-02-28	16:59:02:736	 272	33c	Agent	  * Online = Yes; Ignore download priority = No
2016-02-28	16:59:02:736	 272	33c	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"
2016-02-28	16:59:02:736	 272	33c	Agent	  * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2016-02-28	16:59:02:736	 272	33c	Agent	  * Search Scope = {Machine}
2016-02-28	16:59:02:736	 272	33c	Setup	Checking for agent SelfUpdate
2016-02-28	16:59:02:736	 272	33c	Setup	Client version: Core: 7.6.7601.19116  Aux: 7.6.7601.19116
2016-02-28	16:59:02:736	 272	33c	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:
2016-02-28	16:59:02:736	 272	33c	Misc	 Microsoft signed: NA
2016-02-28	16:59:02:751	 272	33c	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPC313.tmp with dwProvFlags 0x00000080:
2016-02-28	16:59:02:751	 272	33c	Misc	 Microsoft signed: NA
2016-02-28	16:59:02:751	 272	33c	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-win7sp1-wuredir.cab with dwProvFlags 0x00000080:
2016-02-28	16:59:02:767	 272	33c	Misc	 Microsoft signed: NA
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: Send failed with hr = 80072ee7.
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: WinHttp: SendRequestUsingProxy failed for <http://ds.download.windowsupdate.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab>. error 0x8024402c
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c

It seems like the root cause if the problem lies within Windows Update Agent, which may interpret proxy list parameters incorrectly. While it is apparent from C:\Windows\windowsupdate.log, that there is no proxy, for some reason it calls SendRequestUsingProxy API.

2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: Send failed with hr = 80072ee7.
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2016-02-28	16:59:33:561	 272	33c	Misc	WARNING: WinHttp: SendRequestUsingProxy failed for <http://ds.download.windowsupdate.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab>. error 0x8024402c

You can leave a comment on this project, or post a new project for consideration.