Re: 828028 -- is it safe yet?
From: Jerome M. Katz (jerrymkatz_at_NOSPAM@yahoo.com)
Date: 02/22/04
- Next message: sharon: "windows"
- Previous message: Alan Edwards: "Re: Finding the files that were infected"
- In reply to: hctbn: "Re: 828028 -- is it safe yet?"
- Next in thread: Jerome M. Katz: "Re: 828028 -- is it safe yet?"
- Reply: Jerome M. Katz: "Re: 828028 -- is it safe yet?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 21 Feb 2004 19:35:05 -0500
I appeared to also have similar problems. I could never get my Toshiba
laptop with XP home to boot up completely except in safe mode after
installing 828028. I then proceeded to a system restore before it was
installed and I could get it to boot up once. The next time it
wouldn't. I finally used add/remove to remove 828028 and I have gotten
two consecutive bootups without problem. Hopefully the problem is
solved now. I did not have any problem on my Dell desktop.
Jerry
On 21 Feb 2004 15:59:59 -0800, bmiller@btinternet.com (hctbn) wrote:
>> There is no known bugs with 828028 as far as I know. Of what I have seen of
>> reports from large deployments (thousands of computers, server and clients),
>> no issues has emerged. This is also the internal experience in the company
>> I work for, distributed to thousands of computers, no problems reported.
>
>I can say from personal experience (last weekend I had to re-format
>and reinstall Win2k from scratch) and from the experience across our
>company that there are serious problems with 828028 (about 15
>computers and servers out of 300). My m/c locked up in continuous
>reboots, my laptop left blank widows lying around, other PCs and
>servers running XP took ages to reboot, some lost printer settings,
>etc. A Google groups search for 828028 shows that we are certainly
>not alone. We have now stopped deploying, and removed it from any
>machine showing any problems (and it cures the problems which rather
>supports the suggestion that it was the hotfix). This means that we
>are now relying on the firewall and anti-virus until MS come up with
>an 'improved' fix - not a particularly happy scenario.
>
>Bob
- Next message: sharon: "windows"
- Previous message: Alan Edwards: "Re: Finding the files that were infected"
- In reply to: hctbn: "Re: 828028 -- is it safe yet?"
- Next in thread: Jerome M. Katz: "Re: 828028 -- is it safe yet?"
- Reply: Jerome M. Katz: "Re: 828028 -- is it safe yet?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|