STOP: c0000135/winserv error after SP2 install

[Steve Maser]

Hi all,

We've installed SP2 on dozens of machines with no hiccups. But on
two (so far), we restarted after installing SP2 and got:

STOP: c0000135 (unable to locate components)
The application has failed to start because winsrv was not found.
Re-installing the application may fix the problem.

A time-consuming "repair" of the system from a slip-streamed XP SP2
CD resolved this, but we are wondering:

1) Is there an easier way to resolve the above error than a complete
repair install?

2) Has anybody heard what might be generating this error message (ie,
some specific application installed, patches missing prior to update,
etc?)

Thanks!

- Steve

 

[matt]

I have the same problem here. The machine I was working
on was a Gateway Profile. The problem deosn't seem to be
vendor specific. I'm finding quite a few people that are
having this problem on forums though.

Has anyone been able to find a cause, or a quick fix for
this problem?

 

[davexnet02]

No quick fix chaps I'm afraid follow this through, and if that fails then
it's a clean install i'm afraid

I found this entry in experts-exchange.com.
http://www.experts-exchange.com/Operating_Systems/Q_20820709.html
It points the finger at setup.log for possibly having incorrect info.
Perhaps an MVP may know something about this :

"Yes u are right this is surely a problem with update.
This problem happens when u have not uptodate %SystemRoot%\Repair\Setup.log file.
if u done some update in past which involve winsrv.dl file and did not update
this file properely and then after that u did this windows update,
which did not go properly since it has repair.log file.

modify the %SystemRoot%\Repair\Setup.log file and then reapplying update will solve the problem.

This is the example for WinNT, but this may work for Windows 2000 too. -----------------
1) attrib -r -h %SystemRoot%\Repair\Setup.log
2) Make a backup copy of the %SystemRoot%\Repair\Setup.log.

NOTE: check this file on system where u did not have problem and system
who did not do this last update. get the following correct string. and compare that
with this string on these 6 system.

3) Edit Setup.log, search for line, correct this line: this line should look like this
one here(which u got from other system).

\System32\Winsrv.dll ="WINSRV.DLL","<some number>"

4) Save the modified Setup.log to the %SystemRoot%\Repair directory
and attrib +r +h %SystemRoot%\Repair\Setup.log
5) Re-apply the update. "

Dave

 

[ritesh.mcse]

Hi all,

I would recommended using the Windows XP recovery console to boot th
system and then accessing th
"%windir%\$NtServicePackUninstall$\spuninst" folder
Once in the folder, rename it to "spuninst.txt" to "spuninst.bat" an
execute the batch command "batch spuninst.bat." Once back in th
Windows operating system, open the registry and se
"HKLM\System\CurrentControlSet\Services\RpcSs\ObjectName" t
"LocalSystem." Next, execute th
"windir%\$NtServicePackUninstall$\spuninst\spuninst.exe," which wil
prompt an additional rollback changes to the registry.
It should resolve your issue, else let me know if the proble
persists

-
ritesh.mcs

 

[The Grass is greener]

Hi all,

I would recommended using the Windows XP recovery console to boot the
system and then accessing the
"%windir%\$NtServicePackUninstall$\spuninst" folder
Once in the folder, rename it to "spuninst.txt" to "spuninst.bat" and
execute the batch command "batch spuninst.bat." Once back in the
Windows operating system, open the registry and set
"HKLM\System\CurrentControlSet\Services\RpcSs\ObjectName" to
"LocalSystem." Next, execute the
"windir%\$NtServicePackUninstall$\spuninst\spuninst.exe," which will
prompt an additional rollback changes to the registry.
It should resolve your issue, else let me know if the problem
persists.

[/QUOTE]

Hey - bozo - try replying properly, quote some of the post you are
referring to - and do NOT indent with ">"

Also - try using a proper news server, not some stupid web interface
type beast