Win/XP recent update(s)

  • Thread starter Thread starter Anonymous
  • Start date Start date
A

Anonymous

I've posted here in xp.general for help with diagnosis.

Although, the failure seems IE related.

Win/XP, SP2, Pro(aka MCE).
2GB, +3ghz dual-core processor(s).
IE v6.0.2900.2180.xpsp_sp2_qfe.070227-2300

Prior to last Wednesday/Thursday(12/12-12/13), this system was fully
updated. This is stated to give an
estimate of base service prior to the recent update(s).

During one of those days/evenings, I proceeded with
my normal update process for general maintenance
purposes.

I was presented with many(about 8-10) various security
/defender updates. I only note this because it was quite
a few more updates that I usually see. Additionally, I'm
always presented with an IE7 update choice.

I cleared the IE7 choice, and let the remaining updates
fly, as I always do. Everything completed successfully,
and a cold restart(warm required) was performed.

Since then, my IE has been experiencing intermittent
problems/failures. These issues are easily identified by
an IE termination with that - "Internet Explorer has
encountered a problem and needs to close. We are
sorry for the inconvenience / Send / Don't Send" box.

This failure seems very intermittent to me, but has bec-
ome quite a prevalent irritant. To date, I have chosen
the don't send option at the failure. The failure(s) are
not consistent. IOW, if I hammer the url with IE enough
times, it will/may eventually connect successfully.

Sometimes, only to have the failure later, during some kind of site access.


Now, for the things I don't know.


1). Any of the update identifiers?
2). If the update(s) application / IE failures are related?
3). If it's an IE problem?


So, do I:


1). Gut up, and live with it.
2). Send the details of the failure to MS via the Send
option.
3). Try and get any/more information on the recent up-
dates, for further research.
4). Other.


Thanks, for the help.

Anon
 
>I've posted here in xp.general for help with diagnosis.
>
>Although, the failure seems IE related.
>
>Win/XP, SP2, Pro(aka MCE).
>2GB, +3ghz dual-core processor(s).
>IE v6.0.2900.2180.xpsp_sp2_qfe.070227-2300
>
>Prior to last Wednesday/Thursday(12/12-12/13), this system was fully
>updated. This is stated to give an
>estimate of base service prior to the recent update(s).
>
>During one of those days/evenings, I proceeded with
>my normal update process for general maintenance
>purposes.
>
>I was presented with many(about 8-10) various security
>/defender updates. I only note this because it was quite
>a few more updates that I usually see. Additionally, I'm
>always presented with an IE7 update choice.
>
>I cleared the IE7 choice, and let the remaining updates
>fly, as I always do. Everything completed successfully,
>and a cold restart(warm required) was performed.
>
>Since then, my IE has been experiencing intermittent
>problems/failures. These issues are easily identified by
>an IE termination with that - "Internet Explorer has
>encountered a problem and needs to close. We are
>sorry for the inconvenience / Send / Don't Send" box.
>
>This failure seems very intermittent to me, but has bec-
>ome quite a prevalent irritant. To date, I have chosen
>the don't send option at the failure. The failure(s) are
>not consistent. IOW, if I hammer the url with IE enough
>times, it will/may eventually connect successfully.
>
>Sometimes, only to have the failure later, during some kind of site access.
>
>
>Now, for the things I don't know.
>
>
>1). Any of the update identifiers?
>2). If the update(s) application / IE failures are related?
>3). If it's an IE problem?
>
>
>So, do I:
>
>1). Gut up, and live with it.
>2). Send the details of the failure to MS via the Send
> option.
>3). Try and get any/more information on the recent up-
> dates, for further research.
>4). Other.
>
>
>Thanks, for the help.
>
>Anon


There have been some postings on this for IE6 but IE7 crashing is new
to me. I guess this means the same bug-up is now present in IE7. There
is a KB article fix posted earlier so try checking 2-24 hours ago.
Here's the referring article about the crashes for IE6. May there's
one for IE7 too but I don't know about it as of this writing:

http://support.microsoft.com/kb/942367/en-us

- Thee Chicago Wolf
 
Anonymous,

Post in either:

microsoft.public.windowsupdate
or
microsoft.public.internetexplorer.general

--
Newbie Coder
(It's just a name)



"Anonymous" <com@com.com> wrote in message
news:%7W8j.30429$lD6.23260@newssvr27.news.prodigy.net...
>
> I've posted here in xp.general for help with diagnosis.
>
> Although, the failure seems IE related.
>
> Win/XP, SP2, Pro(aka MCE).
> 2GB, +3ghz dual-core processor(s).
> IE v6.0.2900.2180.xpsp_sp2_qfe.070227-2300
>
> Prior to last Wednesday/Thursday(12/12-12/13), this system was fully
> updated. This is stated to give an
> estimate of base service prior to the recent update(s).
>
> During one of those days/evenings, I proceeded with
> my normal update process for general maintenance
> purposes.
>
> I was presented with many(about 8-10) various security
> /defender updates. I only note this because it was quite
> a few more updates that I usually see. Additionally, I'm
> always presented with an IE7 update choice.
>
> I cleared the IE7 choice, and let the remaining updates
> fly, as I always do. Everything completed successfully,
> and a cold restart(warm required) was performed.
>
> Since then, my IE has been experiencing intermittent
> problems/failures. These issues are easily identified by
> an IE termination with that - "Internet Explorer has
> encountered a problem and needs to close. We are
> sorry for the inconvenience / Send / Don't Send" box.
>
> This failure seems very intermittent to me, but has bec-
> ome quite a prevalent irritant. To date, I have chosen
> the don't send option at the failure. The failure(s) are
> not consistent. IOW, if I hammer the url with IE enough
> times, it will/may eventually connect successfully.
>
> Sometimes, only to have the failure later, during some kind of site access.
>
>
> Now, for the things I don't know.
>
>
> 1). Any of the update identifiers?
> 2). If the update(s) application / IE failures are related?
> 3). If it's an IE problem?
>
>
> So, do I:
>
>
> 1). Gut up, and live with it.
> 2). Send the details of the failure to MS via the Send
> option.
> 3). Try and get any/more information on the recent up-
> dates, for further research.
> 4). Other.
>
>
> Thanks, for the help.
>
> Anon
>
>
>
 
"Anonymous" <com@com.com> wrote in message
news:%7W8j.30429$lD6.23260@newssvr27.news.prodigy.net...
>
> I've posted here in xp.general for help with diagnosis.
>
> Although, the failure seems IE related.
>
> Win/XP, SP2, Pro(aka MCE).
> 2GB, +3ghz dual-core processor(s).
> IE v6.0.2900.2180.xpsp_sp2_qfe.070227-2300
>
> Prior to last Wednesday/Thursday(12/12-12/13), this system was fully
> updated. This is stated to give an
> estimate of base service prior to the recent update(s).
>
> During one of those days/evenings, I proceeded with
> my normal update process for general maintenance
> purposes.
>
> I was presented with many(about 8-10) various security
> /defender updates. I only note this because it was quite
> a few more updates that I usually see. Additionally, I'm
> always presented with an IE7 update choice.
>
> I cleared the IE7 choice, and let the remaining updates
> fly, as I always do. Everything completed successfully,
> and a cold restart(warm required) was performed.
>
> Since then, my IE has been experiencing intermittent
> problems/failures. These issues are easily identified by
> an IE termination with that - "Internet Explorer has
> encountered a problem and needs to close. We are
> sorry for the inconvenience / Send / Don't Send" box.
>
> This failure seems very intermittent to me, but has bec-
> ome quite a prevalent irritant. To date, I have chosen
> the don't send option at the failure. The failure(s) are
> not consistent. IOW, if I hammer the url with IE enough
> times, it will/may eventually connect successfully.
>
> Sometimes, only to have the failure later, during some kind of site
> access.
>
>
> Now, for the things I don't know.
>
>
> 1). Any of the update identifiers?
> 2). If the update(s) application / IE failures are related?
> 3). If it's an IE problem?
>
>
> So, do I:
>
>
> 1). Gut up, and live with it.
> 2). Send the details of the failure to MS via the Send
> option.
> 3). Try and get any/more information on the recent up-
> dates, for further research.
> 4). Other.
>
>
> Thanks, for the help.
>
> Anon
>
>
>





There have been some postings on this for IE6 but IE7 crashing is new
to me. I guess this means the same bug-up is now present in IE7. There
is a KB article fix posted earlier so try checking 2-24 hours ago.
Here's the referring article about the crashes for IE6. May there's
one for IE7 too but I don't know about it as of this writing:

http://support.microsoft.com/kb/942367/en-us


- Thee Chicago Wolf






Thanks Wolf. But understand, I am speaking of an IE6 problem, not IE7. Your
response read, at least to me,

like you thought I was speaking of IE7.

I'll take a look at the link you referenced.

Thanks again,

Anon.







Post in either:


microsoft.public.windowsupdate or
microsoft.public.internetexplorer.general


--
Newbie Coder
(It's just a name)




Thanks Newbie. I'll move there pending Wolf's url

review.



Anon
 
Back
Top