Re: Snap-in failed to initialize after software registry file corruption
From: Marin Marinov (mlmarinov_at_askme.ca)
Date: 05/18/04
- Next message: Dave Patrick: "Re: snap-in failed to initialize after replacing a corrupted software registry file"
- Previous message: David Wood: "automate modify permissions of registry key"
- In reply to: Ricky Gan: "Snap-in failed to initialize after software registry file corruption"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 12:59:18 -0400
<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.
- Next message: Dave Patrick: "Re: snap-in failed to initialize after replacing a corrupted software registry file"
- Previous message: David Wood: "automate modify permissions of registry key"
- In reply to: Ricky Gan: "Snap-in failed to initialize after software registry file corruption"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
