Snap-in failed to initialize (XP Pro)

Topic

New Reply

If you don’t have any luck here, try Diskeeper support. I’ve found them very helpful, if a little tardy (probably the timezone differences).

Reply | Quote

Replies

Hi, Cowboy ~

I haven’t installed PD just yet, but the snap-in issue I wanted to know how to fix.

Reply | Quote

I recently uninstalled Diskeeper. When I attempt to run the native XP defragment utility, I get the message below. If I try to run ‘dfrg.msc’ from ‘Run’, same deal. If I go to MMC, there is nothing in the Console Root. Shouldn’t this be populated? Apparently the path for this snap-in is hardcoded and when a third-party app is installed and there is a modification that is not reversed upon uninstallation, correct? Any suggestions as to the proper method of reinstalling/reactivating the defragment snap-in?

Reply | Quote

Bruce–
____________________________________________________________________________

“If I go to MMC, there is nothing in the Console Root. Shouldn’t this be populated?”
_____________________________________________________________________________
XP comes with several preconfigured MMC consoles like Group Policy Editor (snap-in) and the Computer Management (snap-in)–that’s what you mean by populated I believe–you’re opening a blank MMCwhen you type that into the run box–it’s a scaffolding (not “populated” for you to customize with your own snap-ins). This blank MMC is a slate for you to put in snap-ins you want to give it functionality.
______________________________________________________________________________

2 things you can try:

1) Install diskeeper lite from Diskeeper Downloads. Uninstall it and you might fix it. The reason I said Lite–I know you uninstalled 7.0 is because Lite is built and coded more similarly to the native defrag in XP than 7.0. You could reinstall your 7 and uninstall again, but I’m betting you’ve done that. It has worked for some.

2) Find the *dfrg*.dll file. There should be three entries:
regsvr32.exe c:windowssystem32dfrgres.dll
regsvr32.exe c:windowssystem32dfrgsnap.dll
regsvr32.exe c:windowssystem32dfrgui.dll

Next right-click on the dfrg.inf file to make sure the registry settings are ok and this may fix you.

Not sure why you would want to run the watered down native defrag when you have the more versatile, robust 7.0, but hopefully one of these will work; they worked for others.

People trying to fix this with a chkdsk /r (even from the Recovery Console) or to pull the file from the CD running SFC /scannow or SFC /scanonce which might seem logical have not had much luck.

SMBP

Reply | Quote

Hi, Frag ~

You are correct, I wouldn’t want to use the watered down XP defrag utility. I uninstalled Diskeeper Full to make room for the latest Pefect Disk. In between, I was concerned about the snap-in as it should have replaced itself and thought it best I learn how to handle that properly.

Unfortunately, your post was after I finally moved to install PD, but I will save this advice in the event I am not satisfied with PD and switch back to DK.

Reply | Quote

Bruce —

Wasn’t an easy search. These were the two that have worked. The Diskeeper people say they don’t hear it that often–but suggested putting in Lite because of its similarity to XP’s and then uninstalling if you want it off–could not tell me why that worked. This has fixed that error for them before. The error is not that uncommon on groups– those two supposed to work and would fix the snap-in, the snap-in being the native defrag.

The other I found on the web. MS has that error listed for a few servers, but not specifically for Win XP in KB’s so you can see. In Pefect Disk goes in fine and you like it then you’re set.

Think of that blank MMC as a toolbox or a collecting place for tools with no tools (snap-ins) so people can make up their own.

SMBP

Reply | Quote