Running Windows Update on a TMG Firewall Fails with Result Code 80072EE2
Recently I have encountered a few instances in which the Windows Update client on a system with Forefront Threat Management Gateway (TMG) 2010 installed is unable to retrieve updates and fails with an error code of 80072EE2.
When this occurs, Malware Inspection and Network Inspection Systems signature updates are received without issue.
To resolve this issue, open an elevated command prompt and enter the following command:
netsh winhttp set proxy localhost:8080
If it is necessary to access HTTP and/or HTTPS web sites or services on your Internal network from the TMG firewall, you will need to configure the proxy bypass list. To learn how, enter the following command:
netsh winhttp set proxy ?
If you need to configure Windows Update on the TMG firewall to work with WSUS, read this blog post on the Forefront TMG product team blog.
Nice one Richard, saved me some head scratching
You absolute gun, I could not figure out what the issue was!
Thanks mate.
Great fix. Thank you for helping us slower lead paint fans.
My pleasure! : )
I have a similar issue but the error is 80072F7C, the above solution did not help, any ideas?
There are a few error codes that are similar that this fix resolves…not sure if that includes yours though. If it does not resolve the issue, you’ll have to continue troubleshooting. Perhaps looking at a network trace will yield some clues?
Thanks!! Fixed my problem!
You da man Richard !
Many Thanks
Thanks…glad you found the post useful!
Tnx Dude, cost me whole day to find this was my problem, and your string solved my problems. SO TNX
Glad I could help you out!
pingback from
http://blog.chrislehr.com/2011/08/super-quick-way-to-windows-update-on.html
Thanks! Save my night!
Here’s a weird one – setting proxy to 8080 allowed the detection of the updates, but downloading them failed with the same error.
Setting proxy back to direct (netsh winhttp reset proxy) then lets the downloads through.
Very confusing, especially as this is an identical build to another server which updates fine. TMG is a bit flakey isn’t it?
Glad you found the post helpful!
This is a very odd issue with Forefront TMG 2010 firewalls, that’s for sure. I have systems that work without issue, and others that have this problem. I’d be interested in knowing if installing SP2 for TMG resolves this issue.
Thanks very much for that, tried all sorts before I came across this post!
I’m happy you found the post helpful!
brilliant, thanx for sharing, 1 min to fix a problem that would have taken hours to figure out
thanks again
Installing SP2 first did NOT resolve the issue. I had to apply the fix above..thanks have not been able to update this server for 3 months!
Thanks!