Thanks, Bryan. I'll try that...but I'm really hoping I can find someone with
an XP Home CD I can use to boot the thing. Appreciate the insight!!
"Bryan1234" wrote:
> I've found the best solution is to recover with the xp disk. Unfortunely,
> that requires the disk that doesn't exist. Other then that, I tried swapping
> files in and out and I had windows working with a failed explorer. Once
> again, that requied the disk. By looking at the updates, I narrowed it down
> to two culpits. I don't remember the exact names, but there were around last
> numbers 538 and 555, something to do with kernel. Uninstalling those updates
> got the failed explorer interface, but nonetheless, enough to backup with.
>
> "cuzzinkc" wrote:
>
> > I am also having the same problem, but with XP Home Edition SP2. The PC will
> > not boot to safe mode and "last known good" configuration doesn't work,
> > either. This is a friend's computer, and he can't find (or doesn't have) the
> > original XP Home. Before downloading the updates the machine was operating
> > perfectly, and now it won't boot at all.
> >
> > "Bryan1234" wrote:
> >
> > > Using Windows Professional. No other system information will be required for
> > > this.
> > >
> > > I installed Windows Pro SP2. Things run correctly. I go to update enmass.
> > > Updates install correctly, restarts and the following appears instead of my
> > > login screen..
> > >
> > > Summerized.
> > > ----
> > > STOP: c0000269 {Illegal System DLL Relocation}
> > > kernel32.dll relocated, will not work properly
> > > GDI32.dll occupied address range reserved for Windows System Dlls.
> > > ----
> > >
> > > I know that this is a culpit of an offending update, and this issue has been
> > > reported before. I have consulted a support article for the replacement of
> > > kernel32, to no avail. What update is causing this error, because I will
> > > uninstall that update. Thanks.
> > >
|