Actually PA Bear,

I did consider starting a new thread about "my" problem. However, first I
decided to search to see if anyone else had a similar problem. As it turns
out, quite a few people did. In fact, there were multiple threads
essentially addressing the same problem.

It seemed to me that it would make more sense to have a single thread that
addressed this main problem. (Obviously there are a few threads dealing with
different aspects/angles of the same problem, so they make since being
seperate threads.)

If you'll notice, I did not actually ask for a solution to my problem.
Rather I shared that I was having a similar problem as the poster and
included some additional details of things that I had tried (but that didn't
work), including referencing a solution from Mandojim about downloading it
by bypassing Windows Update.

How is it that stating I was having a similar problem is any different from
Seaton or Gary Turner's replies in this same thread or JohnS's reply under
Update #KB829019 failed, to name just a few? My post was to provide possible
additional information. That is also the reason I posted it under multiple
threads.

Had I wanted to ask for help I would have started a new thread. I apologize
to others for this off topic conversation. I also apologize if I have
somehow violated posting etiqutte.

"PA Bear" wrote:

> Ever think about beginning a new thread about /your/ problem, instead of
> "piggybacking" onto all these other threads, no matter how similar their
> problems may be?
> --
> ~PA Bear
>
> tnlindsey wrote:
> > I have been unable to install the .NET update. I am running Windows 2000
> > Professional on an IBM ThinkPad Laptop. I do not have any beta versions
> > of .net installed. I have Microsoft .Net Framework 1.1 as well as the
> > hotfix for it - (KB886903). I tried installing it with the critical
> > updates, then seperate from the critical updates. Both times I got error
> > 0x659; I have no idea what that error means....
>
>