VERY DISSAPOINTED IN MS - [Error number: 0x80072EE2]

Microsoft, you have sent people round and round to fix these update issues.
Just take a look at all the posts and frustrated users. I have read evey news
group, bulletin, MS tips, read-me files etc... and all I hear from your MVPs
is belittling the user into a wild goose chase to fix a problem MANY are
having. Again, VERY dissapointed in your approach.

Duane wrote:
> Microsoft, you have sent people round and round to fix these update
> issues. Just take a look at all the posts and frustrated users. I
> have read evey news group, bulletin, MS tips, read-me files etc...
> and all I hear from your MVPs is belittling the user into a wild
> goose chase to fix a problem MANY are having. Again, VERY
> dissapointed in your approach.

You do realize that a user who is not technically oriented will not come
here to post anything "good" about the updates. Did you come to a technical
support newsgroup expecting to find anything but people having trouble and
asking for help? That's what your post implies - that you did not expect
there to be so many bad (without "in praise of") posts on a technical
support group availabe to help those (by volunteers) with microsoft update
issues around the world. "Many" is a relative term. 3000+ machines on my
part - no problem yet. Millions+ (likely) computers with Windows XP
installed - I'm not seeing the equal in posts.

I am *not* "belittling" anyone - just pointing out that you cannot expect to
walk into a Auto Mechanics Shop and expect to see all working cars.

I did a quick search of these newsgroups and found this, perhaps it will be
of help to you:

TaurArian [MVP] wrote:
> Error 0x80072EE2 is: ERROR_INTERNET_TIMEOUT
> Translation: The request has timed out.
>
> http://update.microsoft.com/windowsu...=en&IsMu=False
>
> When accessing the Update site, you receive the 0x80072EE2 or
> 0x80072EFD error.
>
> http://www.updatexp.com/0x80072ee2.html
> Finding a solution for the 0x80072EE2 error
>
> http://support.microsoft.com/?kbid=836941
> You receive an "Error 0x80072EE2" or "Error 0x80072EFD" error message
> when you try to use Windows Update
>
> See also:
> When searching for available updates on the Windows Update site, you
> receive the 0x8024502d error.
> http://v5.windowsupdate.microsoft.co...cleid=26&ln=en
>
> Posted by =Mac=
>
> <snip > I was getting the 0x80072EE2 message on a
> machine this evening. I never had a problem with it.
>
> I tried all of your suggestions to no avail. However, in a post from
> several months ago, someone mentioned an MTU seating on a router. I
> had upgraded the firmware on my home router several days ago and left
> the MTU set at the default of 1500. Come to think of it, my Internet
> connection seemed a little sluggish since I upgraded the firmware.
>
> I reset the MTU to 1492, and voila! Windows Update works again.
>
> I write this post so that someone else doesn't overlook a simple
> solution to a very frustrating problem.
>
> Router / Firewall / Wireless Router MTU ==> 1492 or less <snip>
>
> Result posted by "tinman"
> <snip> The problem is with the AOL connection. Basically you need to
> amend the MTU settings of the WAN down to 1400. You can experiment
> and see if it works going up to 1460 but it doesn't work past that.
> <snip>

As and aside - an MVP is not someone who works for or even truly represents
Microsoft in any way. They were "recognized" by Microsoft as someone
willing to give their time and effort into helping others and many of them
not only help on the Microsoft Newsgroups but elsewhere. It's time given
freely - no pay involved. And in order to get to that point - they had to
help for some time in order to be recognized as someone who was not just
passing through after solving an issue of their own by others.

Hopefully - something above will fix your issue.. Let us know - because if
you do not it will be the assumption that you have been helped and that one
of the solutions above worked. This type of system does not work properly
without circular feedback from those who needed the help originally.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

I've not seen posts that belittle others on this issue. And I saw one other answer to your *other post* that had on-point advice.

The error you cite is a internet "timeout" issue, which is extremely hard to cure, not even to try to keep from happening.
Real-time communications are bound to have several variants of timeouts.

Do a Google group search for 80072EE2.

Post an extract of your Windows update log.
Look at your log file for Windows Update.

Use Notepad or Wordpad and open & look at the Windows Update log file
C:\Windows\WindowsUpdate.log or C:\WINNT\WindowsUpdate.log

Scroll down all the way for the set of lines for the last session.
Get / copy / paste (ideally, put into a file & attach in reply ) back here the set of lines for the last session.

Do check to see if your Win2000 is configured to use a proxy server. And specify what software firewall is on this pc.
--
Maurice N
MVP Windows - Shell / User
-----


Duane wrote:
> Microsoft, you have sent people round and round to fix these update
> issues. Just take a look at all the posts and frustrated users. I
> have read evey news group, bulletin, MS tips, read-me files etc...
> and all I hear from your MVPs is belittling the user into a wild
> goose chase to fix a problem MANY are having. Again, VERY
> dissapointed in your approach.

It all misses the point, the current windows update software is crap.

Plain and simple.

We paid good money for a good OS that can't update itself becuase MS have
loaded lunatic amounts of proxy blocking, port scanning, and OS user sniffing
rubbish into update.

*sigh*

if they want to check who we are that's cool but for heavens sake can't they
just uses the .net passport service?

"Maurice N ~ MVP" wrote:

> I've not seen posts that belittle others on this issue. And I saw one other answer to your *other post* that had on-point advice.
>
> The error you cite is a internet "timeout" issue, which is extremely hard to cure, not even to try to keep from happening.
> Real-time communications are bound to have several variants of timeouts.
>
> Do a Google group search for 80072EE2.
>
> Post an extract of your Windows update log.
> Look at your log file for Windows Update.
>
> Use Notepad or Wordpad and open & look at the Windows Update log file
> C:\Windows\WindowsUpdate.log or C:\WINNT\WindowsUpdate.log
>
> Scroll down all the way for the set of lines for the last session.
> Get / copy / paste (ideally, put into a file & attach in reply ) back here the set of lines for the last session.
>
> Do check to see if your Win2000 is configured to use a proxy server. And specify what software firewall is on this pc.
> --
> Maurice N
> MVP Windows - Shell / User
> -----
>
>
> Duane wrote:
> > Microsoft, you have sent people round and round to fix these update
> > issues. Just take a look at all the posts and frustrated users. I
> > have read evey news group, bulletin, MS tips, read-me files etc...
> > and all I hear from your MVPs is belittling the user into a wild
> > goose chase to fix a problem MANY are having. Again, VERY
> > dissapointed in your approach.
>