Re: Microsoft's latest Security update M03-007
From: Duncan, Eric A. (eric@cdc.net)
Date: 03/20/03
- Next message: DigiQuestion: "Thanks! I'll give it a try!"
- Previous message: Ed Thurber: "Re: How do I allow USB accessibility to W2K Restricted user?"
- In reply to: John Aird: "Microsoft's latest Security update M03-007"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: eric@cdc.net (Duncan, Eric A.) Date: 20 Mar 2003 12:18:08 -0800
John's advice worked for me and my 13 workstations that blew up this
morning. Us IT Managers have better things to do then to fix this
crap.
Rolling out SP3 to all Active Directory clients and servers this
weekend. Can't afford for the other 50 machines to blow up.
Eric
"John Aird" <jaird@vwc.edu> wrote in message news:<1bec01c2ee2a$eb55c8a0$3301280a@phx.gbl>...
> Subject: Hotfix 815021 Blue Screen
> SESSION5_INITIALIZATION_FAILURE
> From: "Ryan Belcher" <ryanb@sealevel.com> Sent:
> 3/18/2003 6:18:03 AM
>
>
>
>
> I'm posting this as a dual purpose post. 1) Documenting
> my problems and requesting feedback from anyone who knows
> what is going on. And 2) Documenting what I did to roll
> myself back.
>
> I've got a Win2k Sp2 Server with Exchange 2000 Sp3
> installed with all the latest hotfixes installed. Upon
> installing 815021
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;815021, I rebooted and promptly blue screened with
> STOP ERROR: SESSION5_INITIALIZATION_FAILURE 0x00000071
> (0x0, 0x0, 0x0) I've trimmed the useless "0"'s. No GUI
> mode
> would work (safe mode, AD Restore Mode, etc). If any
> Microsoft People want
> to take a stab at this let me know and I'll be happy to
> give you as much info as possible.
>
> What I did to fix it:
>
> 1) Using the Win2k server installation disk, I booted to
> the Recovery Console Repair mode. I copied the new %
> windir%\system32\ntdll.dll (which was installed by the
> hotfix) to c:\.
> 2) I copied the %windir%\$NtUninstallQ815021$\ntdll.dll
> to %windir%\system32\
> 3) Reboot
>
> I do not know what else the patch did, but this appeared
> to allow me to return to normal operation.
>
> I hope this helps some other poor souls that ran into
> this. I was sweating bullets.
>
> Ryan
>
>
> .
>
> --------------------
> Here are the links and other resources for the above
> problem.
> (orginal)
> http://communities.microsoft.com/NewsGroups/previewFrame.a
> sp?
> ICP=technet&sLCID=us&sgroupURL=microsoft.public.win2000.ge
> neral&sMessageID=%253Cv7eaitq0nna0a2@corp.supernews.com%
> 253E
> (others related to topic may shed more like on what
> happend)
> http://communities.microsoft.com/NewsGroups/previewFrame.a
> sp?
> ICP=technet&sLCID=us&sgroupURL=microsoft.public.win2000.ge
> neral&sMessageID=%253C108001c2ed73%2524bab6a870%
> 2524a301280a@phx.gbl%253E
>
> http://communities.microsoft.com/NewsGroups/previewFrame.a
> sp?
> ICP=technet&sLCID=us&sgroupURL=microsoft.public.win2000.ge
> neral&sMessageID=%253C15a101c2ed86%2524234c9fe0%
> 25243301280a@phx.gbl%253E
>
> These were all found on the following microsoft news group
>
> www.support.microsoft.com
>
> >-----Original Message-----
> >has any one experianced problems with this update. Our
> >PC's failed this moring with Blue screens after the
> >update...
> >
> >
> >.
> >
- Next message: DigiQuestion: "Thanks! I'll give it a try!"
- Previous message: Ed Thurber: "Re: How do I allow USB accessibility to W2K Restricted user?"
- In reply to: John Aird: "Microsoft's latest Security update M03-007"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
