Alright, I'm having exactly this problem myself, and I must say, it's
frustrating. The only way I can find to "solve" the problem is a temporary
one and one that needs to be sontantly applied. You need to find your Windows
disk and put it in the CD tray, then when it starts up hit F8 until you get a
bootup screen asking you what to book with . Boot with the CD (I think it's
the last option). This takes a while. Set your language settings and
everything, click "next" then click "repair my computer" (or an option that
is close enough to that anyway). The computer will diagnose the problem and
try and fix it, then ask for you to restart again to see if it works. It
DOESN'T, at least not for me, but see if it does for you anyways. After that,
if you're still having the problem, then do the same thing, boot from the
disk and go to repair. This time after a while it will ask you if you want to
use system restore to go to the last known successful boot. Say yes, and your
computer should start and work fine...at least until Vista forces you to
download their buggy update again.
I have found that this problem is indeed the result of that faulty update.
It's even acknowledged on the Vista help site. They claim to have a second
version of the update that doesn't make your computer go into continuous
reboot mode, but as of yet it keeps screwing over my computer, so I'm putting
my money on the fact that that's a bunch of bs.
Good luck
"dvandusen" wrote:
> The f8, and last known good configuration did not work. There is some
> clarification now though. The boot process goes past the bios, then the boot
> up of the loader (the ........... at the bottom of the screen when allowing
> an F8), then through the windows 2k load (the splash screen with windows 2k
> with a progress bar at the bottom), past the keyboard initialization (the
> lights on the shift led's), through the final splash screen, and to the
> change to the light blue screen where the pointer is supposed show. It
> restarts just before the point where the pointer icon displays. There are no
> devices on this machine other than a Raid card that is/was working fine.
>
> Thx
>
> D
>
> "realcestmoi" wrote:
>
> > Hi there,
> >
> > Try booting with F8 from the menu appearing choose last known good
> > configuration. If that works and you are going to update again skip any
> > driver updates from windows update.
> >
> > Best regards,
> > Michel Denie
> >
> > "dvandusen" <> wrote in message
> > news:AEA00029-7B2C-42D7-9C41-...
> > > MowGreen:
> > >
> > > Thx
> > >
> > > Sadly, it boots the same way in safe mode, but I might be able to do
> > > Recovery Console. How can I determine what is making it restart? Is
> > > there a
> > > log to look at?
> > >
> > > D
> > >
> > > "MowGreen [MVP]" wrote:
> > >
> > >> Does the system boot to Safe Mode ? If so, once in SM, open Add/Remove
> > >> Programs in Control Panel, make a note of which update was installed,
> > >> and PLEASE *post back with the KB number of the update*.
> > >>
> > >> Then uninstall it and reboot the system to normal Windows mode.
> > >>
> > >> If it was a driver update, then boot to SM and use -
> > >>
> > >> How To Replace a Driver by Using Recovery Console in Windows 2000
> > >> http://support.microsoft.com/kb/313670
> > >>
> > >>
> > >> MowGreen [MVP 2003-2007]
> > >> ===============
> > >> *-343-* FDNY
> > >> Never Forgotten
> > >> ===============
> > >>
> > >>
> > >> dvandusen wrote:
> > >>
> > >> > I did a windows update on my w2k box and it now boots (nearly?) to the
> > >> > logon
> > >> > and then restarts automatically. How can I stop this cycle? Is it an
> > >> > installer 'feature' to install something at boot that then causes a
> > >> > restart?
> > >> >
> > >> > D
> > >>
> >
> >
> >
Similar Threads
Linear Mode
