> phaser-X <px (at) zeroday (dot) net [email concealed]> writes:
>
> > I had a different issue after Wednesdays updates. Two win2k computers in
> > my office were rendered useless after the patch. They were fine before,
> > but as soon as the patch finished and the PC was rebooted, the CPU usage
> > was 100% and nothing could be done. I left both PC's sitting for about 20
> > minutes and the 100% CPU usage never came down. Another coworker said he
> > had the same issue with his home PC and he was eventually able to get into
> > the task manager and noticed that the system process was taking up 99-100%
> > of the CPU.
> >
> > Anyone else experience this issue?
>
> A consulting client of mine had the same complaint. He was only able
> to fix it by re-installing Windows. You may want to mention it on
> NTBugTraq, they often discuss and sort out things like this.
>
> ----ScottG.
>
In this case, I suggest the "windowsupdate" newsgroup
These news groups are peer-peer support, although MVP's lurk.
If MSDN customer, MS guarantees an answer in 3 days or they will pick it
up.
You can search such newsgroups for answers by going to Google Groups
search.
--
***************************************************
.~. Jerry Winegarden
/ v \ OIT/Technical Support, Duke University
/( _ )\ jbw (at) duke (dot) edu [email concealed], http://www-jerry.oit.duke.edu
^ ^
***************************************************
> phaser-X <px (at) zeroday (dot) net [email concealed]> writes:
>
> > I had a different issue after Wednesdays updates. Two win2k computers in
> > my office were rendered useless after the patch. They were fine before,
> > but as soon as the patch finished and the PC was rebooted, the CPU usage
> > was 100% and nothing could be done. I left both PC's sitting for about 20
> > minutes and the 100% CPU usage never came down. Another coworker said he
> > had the same issue with his home PC and he was eventually able to get into
> > the task manager and noticed that the system process was taking up 99-100%
> > of the CPU.
> >
> > Anyone else experience this issue?
>
> A consulting client of mine had the same complaint. He was only able
> to fix it by re-installing Windows. You may want to mention it on
> NTBugTraq, they often discuss and sort out things like this.
>
> ----ScottG.
>
Check out the news groups at Microsoft:
http://communities.microsoft.com/newsgroups/default.asp
In this case, I suggest the "windowsupdate" newsgroup
These news groups are peer-peer support, although MVP's lurk.
If MSDN customer, MS guarantees an answer in 3 days or they will pick it
up.
You can search such newsgroups for answers by going to Google Groups
search.
--
***************************************************
.~. Jerry Winegarden
/ v \ OIT/Technical Support, Duke University
/( _ )\ jbw (at) duke (dot) edu [email concealed], http://www-jerry.oit.duke.edu
^ ^
***************************************************
[ reply ]