Snap-in failed to initialize after software registry file corruption

[Ricky Gan]

after using a 1-year old backup of the software registry
and a parallel installation of w2k adv server on
c:\winnt2. I am now seeing the following error in the
original w2k system located in c:\winnt whenever I use
mmc snap-in for device manager, services, and computer
management:
'============================
snap-in failed to initialize
Name: xxxxxxxxxxxx
clsid: xxxxxxxxxxxxxxxxxxxxxx
'============================

Also I tried to use add/remove windows components in
control panel, and I got "cannot find certocm.inf ....0x2
at line xxxxxxxxxx" error.

Please help.

 

[Marin Marinov]

<snip>
Most likely a DLL was deregistered (in the good case, it could be
missing or damaged). Try running Adminpak.msi to install all the admin
tools and hopefully it'll re-register all the DLLs. Anyway, I strongly
suggest that you backup your data, wipe the disk and do a dual-boot
install on two *separate* partitions - having two Windows OSs on the
same partition is a veeery bad idea. A lot of system directories are
shared, you'll also probably get into issues with NTFS permissions.

HTH
--
Cheers,
Marin Marinov
MCT, MCSE 2003/2000/NT4.0,
MCSE:Security 2003/2000, MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Marin Marinov]

<snip>
Most likely a DLL was deregistered (in the good case, it could be
missing or damaged). Try running Adminpak.msi to install all the admin
tools and hopefully it'll re-register all the DLLs. Anyway, I strongly
suggest that you backup your data, wipe the disk and do a dual-boot
install on two *separate* partitions - having two Windows OSs on the
same partition is a veeery bad idea. A lot of system directories are
shared, you'll also probably get into issues with NTFS permissions.

HTH
--
Cheers,
Marin Marinov
MCT, MCSE 2003/2000/NT4.0,
MCSE:Security 2003/2000, MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no
rights.