mmc.exe class not registered error

Haven't had this error since Win 2000, but after installing a clean copy of Windows 7 on my workstation, and a number of programs, when I try to run mmc from the run prompt I get a Class Not Registered Error, which is causing havoc on all my software installations.

Any ideas on how to fix or re-register?

Thanks,
Tom

I checked the search against my laptop (which doesn't experience this issue and went to Win 7 w/o issue) and the mmc.exe files are either System\32 or SysWOW64; thre are also files in C:\Windows\winsxs\amd64_microsoft-windows-m..-management_console and \winsxs\x86 as above, all same size. Doesn't seem to be the issue.

The sf scan shows mmcndmgr.dll version 6.1.7600.16835 (which seems to be a version that shows up a lot in the missing category). Error is either file is missing or hash mismatch. Same files/dates etc are on the laptop, didn't run the sfscan on it.

Ran a full virus scan with NOD32 v4 x64 - no issues.

Ah well. I'll repartition and reformat both hard-disks this time around and reinstall spic-and-span.

Never had much luck with the a win2003 domain account and the fix you suggest.

Hopefully I remember what I'm doing this time.

Thanks,
Tom

Apparently it's memory. I have 4x2gb Corsair chips and they apparently have never been supported in that configuration (just 2x2gb). I occasionally had BOSDs until I changed the memory timings to 2.1v and that fixed things. But now it's back and Windows 7 doesn't like it, no matter the voltage settings. What a pain.

oisin53 said:

Apparently it's memory. I have 4x2gb Corsair chips and they apparently have never been supported in that configuration (just 2x2gb). I occasionally had BOSDs until I changed the memory timings to 2.1v and that fixed things. But now it's back and Windows 7 doesn't like it, no matter the voltage settings. What a pain.

It would be somewhat strange for the "class not registered" error to be caused by bad or mismatched memory. Certainly possible, but unlikely.

If you're still experiencing the symptom, try this from an elevated (run as admin) CMD prompt:

regsvr32 mmcndmgr.dll

That should re-register the DLL's COM componentry.

If you use "registry cleaners" (*shudder*), your machine probably got pwned by some unqualified developer's notion of which registry entries are necessary and which are not.

Thanks for the suggestion and, no, I don't use registry cleaners, which always create more problems than their worth. I also as a rule don't install antivirus software until I'm at the end of my installation routine.

I reinstalled again, from scratch. Backing up as I go. Seems to be more stable. I pulled 2 of the mem sticks from the PC, booted up at full 1066 speed in dual ganged mode (which it did not do before with the 4 sticks). And overall feels more responsive. With less memory. Go figure.

What's odd is that I've been using Windows 7 RC for about 6 months w/o so much as a hiccup, and I used same system for Vista Ult 64 installs, too, w/o prob. I noticed this time around many install failures reading/expanding files (including the Windows 7 install DVD). And decided it was time to really dig down and find out why the BSODs and errors. This Asus mboard, M2N-SLI Deluxe, can work with up to 4 sticks, but the Crucial ones I had were only rated for 2, not 4.

Anyone need some memory?


Thanks,
Tom

The memory to my mind was behind the issues. When I was installing Win7 the second go-around, I got intermittent disk read errors (CD/DVD Installs), and unpacking errors, which probably resulted in the corrupted installation of certain large software installs, like Adobe CS4 and Bus Objects Enterprise Xi 3.1

Be aware that some memory manufs do not "ok" installation of 8gb of memory (2x4 sticks) with various mboards, even though the mboard manuf (in my case, Asus) okayed the memory for this board. Crucial specified that their memory for this board was only tested in the 4gb (2x sticks) configuration. After I removed the 2 sticks, went back to 800mhz, reinstalled Windows 7 and software, I have not had one instance of blue screen since.

This thread came up in a search, I have the same problem, and I KNOW it is not any of the things you cite here. I tried:

regsvr32 mmcndmgr.dll

But I am still getting "mmc.exe class not resistered"

I cannot do an In Place Install

I cannot run SFC -scannow

I have D7, I may attach this drive to another system, and scan the windows folder "offline"

But I wanted to know, are there any other DLLs related to the MMC that need to be re-registered?