Cannot boot with Critical upgrades

[Jeff F]

I just visited the Win2k critical upgrades page and loaded
a number of different patches. Before I restarted, I
loaded some other patches that were not critical. Now the
computer goes through the boot process with the Win2K
screen, but then says "Stop: c0000135 {Unable tolocate
DLL} The dynamic link library winsrv could not be found in
the specified path Default Load Path." before it restarts
(resulting in an uninterruptable loop of restarts.

Any suggestions how this can be remedied?

 

[Daniel Chang [MSFT]]

173309 Blue Screen STOP Message C0000135 Appears at Startup
http://support.microsoft.com/?id=173309

--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.


: I just visited the Win2k critical upgrades page and loaded
: a number of different patches. Before I restarted, I
: loaded some other patches that were not critical. Now the
: computer goes through the boot process with the Win2K
: screen, but then says "Stop: c0000135 {Unable tolocate
: DLL} The dynamic link library winsrv could not be found in
: the specified path Default Load Path." before it restarts
: (resulting in an uninterruptable loop of restarts.
:
: Any suggestions how this can be remedied?

 

[Alan T.]

This solution appears to be only for NT4 and below.

Based on the solution, I copied the Software hive from the
repair directory to the \system32\config directory with
the same results. Is there any more information that you
can give that will help to resolve this issue???