To those troubleshooting Kb891711

I have another data point to aid you in your search for the cause of the mal
behavior of this critical update. Running Win98SE, I installed this update
when it was first issued - no problems. Last night, I installed Microsoft
..Net 1.1 and the four critical updates that were identified as required by
the Microsoft update site. The system barely ran. Even the simplest program
like filemon gave me the BSOD and regmon resulted in a fatal exception. I
removed Kb891711 from startup, but not the machine, and everything returned
to normal.

Hope this helps those working to solve the Kb891711 mystery.

Don Kirkpatrick

What (4) updates were those?
kb891711 was the last shown for me.
I also have .Net 1.1sp1.
Thanks
--
mae


"Don Kirkpatrick" wrote in message
.. .
| I have another data point to aid you in your search for the cause of the
mal
| behavior of this critical update. Running Win98SE, I installed this update
| when it was first issued - no problems. Last night, I installed Microsoft
| .Net 1.1 and the four critical updates that were identified as required by
| the Microsoft update site. The system barely ran. Even the simplest
program
| like filemon gave me the BSOD and regmon resulted in a fatal exception. I
| removed Kb891711 from startup, but not the machine, and everything
returned
| to normal.
|
| Hope this helps those working to solve the Kb891711 mystery.
|
| Don Kirkpatrick
|
|

At the time, it didn't seem like noting which updates were being applied was
important. I now regret not noting exactly which were applied. One was a
cumulative service pack for Explorer and one was an MDAC 2.6 update. I do
not remember what the other two were. My system was up-to-date until I added
the .Net 1.1 update, then these other four poped up as needed. I do remeber
that the total download size for the four was 13 Meg.

Is there a way I can get update install dates so I can better answer your
question?


"mae" wrote in message
...
What (4) updates were those?
kb891711 was the last shown for me.
I also have .Net 1.1sp1.
Thanks
--
mae


"Don Kirkpatrick" wrote in message
.. .
| I have another data point to aid you in your search for the cause of the
mal
| behavior of this critical update. Running Win98SE, I installed this
update
| when it was first issued - no problems. Last night, I installed
Microsoft
| .Net 1.1 and the four critical updates that were identified as required
by
| the Microsoft update site. The system barely ran. Even the simplest
program
| like filemon gave me the BSOD and regmon resulted in a fatal exception.
I
| removed Kb891711 from startup, but not the machine, and everything
returned
| to normal.
|
| Hope this helps those working to solve the Kb891711 mystery.
|
| Don Kirkpatrick
|
|

"Don Kirkpatrick" wrote in message
.. .
At the time, it didn't seem like noting which updates were being applied
was
important. I now regret not noting exactly which were applied. One was a
cumulative service pack for Explorer and one was an MDAC 2.6 update. I do
not remember what the other two were. My system was up-to-date until I
added
the .Net 1.1 update, then these other four poped up as needed. I do
remeber
that the total download size for the four was 13 Meg.

Is there a way I can get update install dates so I can better answer your
question?

Run Windows Update.

In the left pane, it should offer you the ability to
"View installation history".

I before I installed .net framework 1.1, the machine was up-to-date. After I
installed .net, the following four critical updates were flagged as
required. They were all downloaded and installed at the same time.

Kb837009
.net framework 1.1 service pack 1
Q329414 (MDAC 2.6)
Security update MSXML 2.6

No issues arose during download and install.



"mae" wrote in message
...
What (4) updates were those?
kb891711 was the last shown for me.
I also have .Net 1.1sp1.
Thanks
--
mae


"Don Kirkpatrick" wrote in message
.. .
| I have another data point to aid you in your search for the cause of the
mal
| behavior of this critical update. Running Win98SE, I installed this
update
| when it was first issued - no problems. Last night, I installed
Microsoft
| .Net 1.1 and the four critical updates that were identified as required
by
| the Microsoft update site. The system barely ran. Even the simplest
program
| like filemon gave me the BSOD and regmon resulted in a fatal exception.
I
| removed Kb891711 from startup, but not the machine, and everything
returned
| to normal.
|
| Hope this helps those working to solve the Kb891711 mystery.
|
| Don Kirkpatrick
|
|

Naturally, we have all heard of machines that do work with Kb891711
installed. We have heard of those that don't, like mine. It is a
novelty, though, to hear of one that once did work but has stopped! (But
I have no advice for you. Be patient, maybe, as some have reported the
odor of MS brains hard at work in the air. Take a sniff!)

I don't know. Try an un/re-install of it. If it works for you, I'll go
next!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Don Kirkpatrick" wrote in message
.. .
| I before I installed .net framework 1.1, the machine was up-to-date.
After I
| installed .net, the following four critical updates were flagged as
| required. They were all downloaded and installed at the same time.
|
| Kb837009
| .net framework 1.1 service pack 1
| Q329414 (MDAC 2.6)
| Security update MSXML 2.6
|
| No issues arose during download and install.
|
|
|
| "mae" wrote in message
| ...
| What (4) updates were those?
| kb891711 was the last shown for me.
| I also have .Net 1.1sp1.
| Thanks
| --
| mae
|
|
| "Don Kirkpatrick" wrote in message
| .. .
| | I have another data point to aid you in your search for the cause
of the
| mal
| | behavior of this critical update. Running Win98SE, I installed
this
| update
| | when it was first issued - no problems. Last night, I installed
| Microsoft
| | .Net 1.1 and the four critical updates that were identified as
required
| by
| | the Microsoft update site. The system barely ran. Even the
simplest
| program
| | like filemon gave me the BSOD and regmon resulted in a fatal
exception.
| I
| | removed Kb891711 from startup, but not the machine, and everything
| returned
| | to normal.
| |
| | Hope this helps those working to solve the Kb891711 mystery.
| |
| | Don Kirkpatrick
| |
| |
|
|
|

Thank you, thought I had missed something but I had previously installed
those.

09/14/04 .Net Framework 1.1 sp1
04/13/04 Kb837009
11/20/02 Q329414 --
02/13/02 Security update MSXML
--
mae

"Don Kirkpatrick" wrote in message
.. .
| I before I installed .net framework 1.1, the machine was up-to-date. After
I
| installed .net, the following four critical updates were flagged as
| required. They were all downloaded and installed at the same time.
|
| Kb837009
| .net framework 1.1 service pack 1
| Q329414 (MDAC 2.6)
| Security update MSXML 2.6
|
| No issues arose during download and install.
|
|
|
| "mae" wrote in message
| ...
| What (4) updates were those?
| kb891711 was the last shown for me.
| I also have .Net 1.1sp1.
| Thanks
| --
| mae
|
|
| "Don Kirkpatrick" wrote in message
| .. .
| | I have another data point to aid you in your search for the cause of
the
| mal
| | behavior of this critical update. Running Win98SE, I installed this
| update
| | when it was first issued - no problems. Last night, I installed
| Microsoft
| | .Net 1.1 and the four critical updates that were identified as
required
| by
| | the Microsoft update site. The system barely ran. Even the simplest
| program
| | like filemon gave me the BSOD and regmon resulted in a fatal
exception.
| I
| | removed Kb891711 from startup, but not the machine, and everything
| returned
| | to normal.
| |
| | Hope this helps those working to solve the Kb891711 mystery.
| |
| | Don Kirkpatrick
| |
| |
|
|
|

Don, I've received a request from the team that's working on the
KB891711 issue. They would like everyone in the USA who has had problems
with KB891711 to call 1-866-PCSafety (1-866-727-2338). If you can help
them with some info, they say they're close to reproducing the
problem--first step toward solving it. I have asked for, though not yet
received, assurances that callers will be taken more seriously than has
been reported thus far.

(According to at least a couple of people, when they called PSS they
were told that KB891711 wasn't a critical problem on Win98 and to just
uninstall it. KB891711 deals with a very *serious* vulnerability,
affecting pretty much all Windows systems, and anyone who can't get
patched decently should don at *least* a dozen condoms before journeying
out onto the internet.)

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"Don Kirkpatrick" wrote in message
.. .
I have another data point to aid you in your search for the cause of
the mal
behavior of this critical update. Running Win98SE, I installed this
update
when it was first issued - no problems. Last night, I installed
Microsoft
.Net 1.1 and the four critical updates that were identified as
required by
the Microsoft update site. The system barely ran. Even the simplest
program
like filemon gave me the BSOD and regmon resulted in a fatal
exception. I
removed Kb891711 from startup, but not the machine, and everything
returned
to normal.

Hope this helps those working to solve the Kb891711 mystery.

Don Kirkpatrick

I wish I could reply to you in private, as what I have to say is not good.
The results of calling this number was a total waste of time. The lady I
talked with was oblivious to the Kb891711 problem and the existence of any
special team. She did not want to talk with me at all. The best I can offer
is to have you forward this Kb891711 thread to the team and, if they wish,
they can contact me. I'm more than willing to supply any information I have.

Don Kirkpatrick

"Gary S. Terhune" wrote in message
...
Don, I've received a request from the team that's working on the
KB891711 issue. They would like everyone in the USA who has had problems
with KB891711 to call 1-866-PCSafety (1-866-727-2338). If you can help
them with some info, they say they're close to reproducing the
problem--first step toward solving it. I have asked for, though not yet
received, assurances that callers will be taken more seriously than has
been reported thus far.

(According to at least a couple of people, when they called PSS they
were told that KB891711 wasn't a critical problem on Win98 and to just
uninstall it. KB891711 deals with a very *serious* vulnerability,
affecting pretty much all Windows systems, and anyone who can't get
patched decently should don at *least* a dozen condoms before journeying
out onto the internet.)

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"Don Kirkpatrick" wrote in message
.. .
I have another data point to aid you in your search for the cause of
the mal
behavior of this critical update. Running Win98SE, I installed this
update
when it was first issued - no problems. Last night, I installed
Microsoft
.Net 1.1 and the four critical updates that were identified as
required by
the Microsoft update site. The system barely ran. Even the simplest
program
like filemon gave me the BSOD and regmon resulted in a fatal
exception. I
removed Kb891711 from startup, but not the machine, and everything
returned
to normal.

Hope this helps those working to solve the Kb891711 mystery.

Don Kirkpatrick

I was afraid of that. I *knew* I should have waited for assurances
before passing along that request! I will forward your comments and your
invitation (which is incredibly gracious under the circumstances.) The
email addy I use for posting is a real one, if you still want to
correspond in private.

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"Don Kirkpatrick" wrote in message
.. .
I wish I could reply to you in private, as what I have to say is not
good.
The results of calling this number was a total waste of time. The lady
I
talked with was oblivious to the Kb891711 problem and the existence of
any
special team. She did not want to talk with me at all. The best I can
offer
is to have you forward this Kb891711 thread to the team and, if they
wish,
they can contact me. I'm more than willing to supply any information I
have.

Don Kirkpatrick

"Gary S. Terhune" wrote in message
...
Don, I've received a request from the team that's working on the
KB891711 issue. They would like everyone in the USA who has had
problems
with KB891711 to call 1-866-PCSafety (1-866-727-2338). If you can
help
them with some info, they say they're close to reproducing the
problem--first step toward solving it. I have asked for, though not
yet
received, assurances that callers will be taken more seriously than
has
been reported thus far.

(According to at least a couple of people, when they called PSS they
were told that KB891711 wasn't a critical problem on Win98 and to
just
uninstall it. KB891711 deals with a very *serious* vulnerability,
affecting pretty much all Windows systems, and anyone who can't get
patched decently should don at *least* a dozen condoms before
journeying
out onto the internet.)

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"Don Kirkpatrick" wrote in message
.. .
I have another data point to aid you in your search for the cause
of
the mal
behavior of this critical update. Running Win98SE, I installed this
update
when it was first issued - no problems. Last night, I installed
Microsoft
.Net 1.1 and the four critical updates that were identified as
required by
the Microsoft update site. The system barely ran. Even the simplest
program
like filemon gave me the BSOD and regmon resulted in a fatal
exception. I
removed Kb891711 from startup, but not the machine, and everything
returned
to normal.

Hope this helps those working to solve the Kb891711 mystery.

Don Kirkpatrick