Hi, I recently updated 3 machines. One had McAfee, one Norton and one
Avast!, all three updated and recently scanned. Also had Microsoft
Anti-spyware on there, so the machines clean of viruses and spyware.

Apparently Microsoft Update (NOT Windows Update) downloaded and installed
and update that makes all three machines boot up to the following screen:

STOP: c0000269 {Illegal System DLL Relocation}
They stsyem DLL user32.dll was relocated in memory. The application will not
run properly.
The relocation occured because the DLL C:\WINDOWS\system32\ntdll.dll
occupied an address range reserved for Windows System DLLs. The vendor
supplying the DLL should %s %s

I do NOT want to pull out the hard drives, hook them up to another PC, save
the data, reinstall Windows and restore all the data ... NOT an option! Why
would updates via Microsoft Update cause this?

Hi Jeremy,

I've not seen nor heard of that happening on any machine from MS Update. It
must be something specific to how you have your machines configured. Can you
copy the windowsupdate.log from any of them? Did the system reboot
successfully at least once after the most recent installations?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org

"Jeremy" <Jeremy@discussions.microsoft.com> wrote in message
news:3D32A48E-E61F-4E88-9C2A-B19DD26240F1@microsoft.com...
> Hi, I recently updated 3 machines. One had McAfee, one Norton and one
> Avast!, all three updated and recently scanned. Also had Microsoft
> Anti-spyware on there, so the machines clean of viruses and spyware.
>
> Apparently Microsoft Update (NOT Windows Update) downloaded and installed
> and update that makes all three machines boot up to the following screen:
>
> STOP: c0000269 {Illegal System DLL Relocation}
> They stsyem DLL user32.dll was relocated in memory. The application will
> not
> run properly.
> The relocation occured because the DLL C:\WINDOWS\system32\ntdll.dll
> occupied an address range reserved for Windows System DLLs. The vendor
> supplying the DLL should %s %s
>
> I do NOT want to pull out the hard drives, hook them up to another PC,
> save
> the data, reinstall Windows and restore all the data ... NOT an option!
> Why
> would updates via Microsoft Update cause this?

Hi Rick -

Thanks for the response. I spent an hour on the phone with a very helpful
Microsoft guy using the free phone support that accompanies Windows Update
Issues. He threw the book and the kitchen sink at it... to no avail. We had
to end up reformatting all three machines after getting the data off of it.

His recommendation is that I discontinue use of Microsoft Update and just
use regular Windows Update. Errr ...

"Rick "Nutcase" Rogers" wrote:

> Hi Jeremy,
>
> I've not seen nor heard of that happening on any machine from MS Update. It
> must be something specific to how you have your machines configured. Can you
> copy the windowsupdate.log from any of them? Did the system reboot
> successfully at least once after the most recent installations?
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Associate Expert - WindowsXP Expert Zone
> www.microsoft.com/windowsxp/expertzone
> Windows help - www.rickrogers.org
>
> "Jeremy" <Jeremy@discussions.microsoft.com> wrote in message
> news:3D32A48E-E61F-4E88-9C2A-B19DD26240F1@microsoft.com...
> > Hi, I recently updated 3 machines. One had McAfee, one Norton and one
> > Avast!, all three updated and recently scanned. Also had Microsoft
> > Anti-spyware on there, so the machines clean of viruses and spyware.
> >
> > Apparently Microsoft Update (NOT Windows Update) downloaded and installed
> > and update that makes all three machines boot up to the following screen:
> >
> > STOP: c0000269 {Illegal System DLL Relocation}
> > They stsyem DLL user32.dll was relocated in memory. The application will
> > not
> > run properly.
> > The relocation occured because the DLL C:\WINDOWS\system32\ntdll.dll
> > occupied an address range reserved for Windows System DLLs. The vendor
> > supplying the DLL should %s %s
> >
> > I do NOT want to pull out the hard drives, hook them up to another PC,
> > save
> > the data, reinstall Windows and restore all the data ... NOT an option!
> > Why
> > would updates via Microsoft Update cause this?
>
>
>