RE: 811493 repeatedly
From: Steve Hamer (anonymous_at_discussions.microsoft.com)
Date: 02/25/04
- Next message: bikermike: "RE: 811493 repeatedly (BillP)"
- Previous message: ALAN: "cant enter setup/upgrade"
- In reply to: Bill Peele [MS]: "RE: 811493 repeatedly"
- Next in thread: bikermike: "RE: 811493 repeatedly (BillP)"
- Reply: bikermike: "RE: 811493 repeatedly (BillP)"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 08:09:59 -0800
Well, my entire SQA group is being affected by this
issue. This particular hotfix was sucessfully installed
on all of our W2k SP3 workstations and W2K sp3 server in
Oct. (we are using a SUS server) In Feb. we started
getting daily messages saying to install 811493 again. We
have tried every solution offered, and verified all
registry settings etc. but to no avail. As a result, we
no longer have a "KNOWN, GOOD" OS configuration with which
to test our products. We have resorted to installing SP4
on all of our machines, which means WE are no longer
testing our software in what we have published as "the
minimmum supported OS configuration". God help us now,
because Microsoft can't seem to.
>-----Original Message-----
><Has anyone looked up that Q-number in the MSKB? It has
to do with WIN XP, of all things! Why are we WIN2K users
even
>getting it?!>
>
>>From the article:
>
> 811493 - MS03-013: Buffer Overrun in Windows Kernel
Message Handling Could Lead to Elevated Privileges
> http://support.microsoft.com/default.aspx?scid=kb;
[LN];811493
>
> The information in this article applies to:
>
> Microsoft Windows XP Professional
> Microsoft Windows XP Home Edition
> Microsoft Windows 2000 Professional
> Microsoft Windows 2000 Server
> Microsoft Windows 2000 Advanced Server
> Microsoft Windows NT Server 4.0 Terminal Server
Edition
> Microsoft Windows NT Server 4.0
> Microsoft Windows NT Workstation 4.
>
><One of the ones I feel maybe could not work for me,
namely your checking that the right registry keys are
created. I noted
>that at least one of them referenced Service Pack 4.
After the way that dingus crashed my one computer so I had
to drop a
>bomb on it to make it serviceable again, I will NEVER let
that thing onto a computer as long as I live, unless MS
Bill &
>Company can certify unequivocally promise that it is
safe. I see people, to this hour, are still having
problems with SP4.
>Would I need to check a registry key that names a package
that is not on my computer?>
>
>This is a post Service Pack 3 update. This means it came
out after SP3 and is included in SP4, which means the
update
>uses a SP4 naming convention. The below is also from the
article the URL above references.
>
> This patch requires Windows 2000 Service Pack 2 (SP2)
or Windows 2000 Service Pack 3 (SP3).
>
> To resolve this problem, obtain the latest service pack
for Microsoft Windows 2000.
>
> To verify that the patch is installed on your computer,
confirm that the following registry key exists:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows
2000\SP4\Q811493
>
>Since the SP4 in the registry key structure above tells
us this update came out after SP3 and was included in SP4,
you
>would need to look for a registry key that names a
package that is not on your computer. If you have any
post SP4
>updates installed we will also see a SP5 registry sub-key
under the Windows 2000 key.
>
>Bill Peele
>Microsoft Enterprise Support
>
>This posting is provided "AS IS" with no warranties, and
confers no rights. Use of included script samples are
subject to the
>terms specified at
http://www.microsoft.com/info/cpyright.htm
>
>Note: For the benefit of the community-at-large, all
responses to this message are best directed to the
newsgroup/thread
>from which they originated.
- Next message: bikermike: "RE: 811493 repeatedly (BillP)"
- Previous message: ALAN: "cant enter setup/upgrade"
- In reply to: Bill Peele [MS]: "RE: 811493 repeatedly"
- Next in thread: bikermike: "RE: 811493 repeatedly (BillP)"
- Reply: bikermike: "RE: 811493 repeatedly (BillP)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|