Reboot Loop C000135

  • Thread starter Thread starter Mike Weber
  • Start date Start date
M

Mike Weber

Hi. Have seen this posted many times. Appears in my case (at enterprise)
to be due to SP4. I saw that an earlier posting said the user uninstalled a
patch using the recovery console. How do you uninstall a patch using
recovery console? I see a folder in the patch called spuninst and in that
folder is a file called spuninst.exe (which i guess stands for service pack
uninstall). But I can't figure out how to run the uninstall. Any help is
much appreciated.
 
Thanks Dude! Just figured that out too. Looks like stupid SP4 has caused
the loop to about 10 of 250 pc's- all laptops or desktops which are updated
via SUS. Hope MS fixes this issue soon since so many have posted. Thanks
again and if I ever figure out the .exe portion, I will be sure to post.

Mike
 
Mike,

I think you're right about it being an SP4 problem. I just
installed the patch on my machine at work, which is SP3,
and it is just fine. Maybe it should have been installed
b4 my upgrade to SP4?
 
Update. Removing SP4 via recovery console, did indeed recover the pc. To
assist with this see the following:
www.jsiinc.com
And look for Tip 7074.

Prior to removing SP4, i reviewed the "dir" of winnt to see what patches had
been installed today. In this case it was sp4 as the directory date was
today's date. If it is a hotfix causing your issue, you can probably
uninstall it the same way.

Strangely enough, out of 250 servers and client pc's, no servers had issues
and only about 6 client pc's had issues. Not sure what the problem is with
these systems and sp4, but hopefully ms will figure this out. I will post
again to let everyone know if the SUS SP4 reapplying works or if it craps
out the system again.

Mike

We are now reinstalling SP$
 
Mike,

So you uninstalled SP4, not the KB824141 patch, correct?
I'm confused as to why MS, (OK, maybe I shouldn't be
confused because it is MS), would not test this patch
against SP4. I installed SP4 about a month ago. This patch
only became available last Friday. Those bastards!

Kevin
 
Final Update- SUS SP4 push worked fine after the recovery.

Kevin- the machine did not even have kb824141 installed. That was the first
thing I looked for. So there is something with SP4 with certain machines.
My theory is (and it is probably wrong) that after the patch pushes, i have
set group policy to prompt the user for reboot, as i can't force an auto
reboot in case they are in a critical file. I'm thinking that they didn't
reboot and something they clicked on ended up corrupting sp4 prior to the
reboot. I did observe a server issue with this in that a server used as a
print server stopped properly spooling and printing documents after i put in
sp4 UNTIL i gave a reboot. Then everything was fine again. Ahhhh, the life
of an i.t. person trying to figure out why fixes cause more problems. :-)

mike
 
Back
Top