A Guide to Rectifying MMC Snap-In Failures

The “MMC could not create the snap-in” error has been around for some time and still seem to bug some users now and then. The error occurs when you try to open an administrative tool such as an Event Viewer, Task Scheduler, and so forth.

Sometimes, the error may also pop up after a Blue Screen of Death (BSOD), causing one or more apps to crash. This error often occurs if the registry configuration of the snap-in is malfunctioning. Here we show a few ways to fix to help you resolve the “MMC could not create the snap-in” error and restore administrative tools access in Windows.

1. Fix the Broken Registry Configuration for the Snap-In

If the registry configuration for the affected snap-in is broken, it may trigger the “MMC could not create the snap-in” error. To fix the issue, you’ll need to delete the corrupt registry entry associated with the snap-in. Here’s how to do it.

Making incorrect modifications to the Windows Registry involves risk and may cause your system to malfunction. We recommend you create a restore point and make a registry backup to be on the safe side.

1. Press Win + R to open Run.

2. Type regedit and click OK.

3. In the Registry Editor, navigate to the following location:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns

4. The SnapIns key consists of multiple sub-keys. You need to locate the sub-key identical to the CLSID shown in the error message.

5. For example, if the error occurs when opening Event Viewer, you’ll likely see CLSID: c7b8fb06-bfe1-4c2e-9217-7a69a95bbac4, and so on. So, note down the CLSID shown in the error screen.

6. In the Registry Editor, select the sub-key folder with the same name as the error CLSID.

7. Next, right-click on the same sub-key folder and select Delete.

8. Click Yes to confirm the action.

9. Close the Registry Editor and restart your computer.

10. After the restart, open the administrative tool snap-in to see if the error is resolved.

SwifDoo PDF Perpetual (1 PC) Free upgrade. No monthly fees ever.

2. Enable .NET Framework

You can also fix this error by enabling .NET Framework 3.5. The idea is that one of the snap-ins on your PC may need .NET Framework 3.5 to work. So, if the feature is disabled, you may encounter an error.

Fortunately, you can easily enable the .NET Framework feature using the Turn Windows features on or off dialog. Here’s how to do it.

To enable .NET Framework 3.5:

1. Press the Win key and type Windows features and click on Turn Windows features on or off from the search results.
2. In the Windows Features dialog, select the .NET Framework 3.5 (include .NET 2.0 and 3.0).
3. Next, click the Plus icon to expand the section and select the options ‘Windows Communications Foundation HTTP Activation’ and ‘Windows Communications Foundation Non-HTTP Activation’.
4. Next, click to Apply the changes and install the feature.
5. Once installed, you’ll be prompted to restart the computer. Restart your system, and the MMC snap-in should work now.

3. Check for and Repair Corrupt System Files

Screensaver Factory, Create stunning professional screensavers within minutes. Create screensavers for yourself, for marketing or unlimited royalty-free commercial distribution. Make screensavers from images, video and swf flash, add background music and smooth sprite and transition effects. Screensaver Factory is very easy to use, and it enables you to make self-installing screensaver files and CDs for easy setup and distribution. Screensaver Factory is the most advanced software of its kind.

If you have one or more corrupt system files, it may cause issues with the system apps. You can run the System File Checker tool to determine if the problem is due to system file issues. It will scan and check the integrity of systems files and automatically repair them to fix the problem.

Microsoft recommends running its built-in Windows image check and repair utility, Deployment Image Servicing and Management (DISM), before running the System File Checker utility.

If you’re not sure how to run either of these tools, we cover both in our guide on how to repair corrupt Windows files with Windows’ built-in tools .

4. Remove and Reinstall the Microsoft Visual C++ Redistributable

If the issue persists, try to fix and repair issues with the Visual C++ Redistributable package. If there are any issues with the package, it can cause the MMC snap-ins to stop working.

To repair the Visual C++ Redistributable package:

1. Press Win + R to open Run.
2. Type “control” and click OK to open Control Panel.
3. In Control Panel, click on Uninstall a program under Programs.
4. Locate and select the Microsoft Visual C++ Redistributable entry and click Uninstall.
5. In the Modify Setup dialog, click Repair. The repair process may take a few minutes to complete.
6. Once done, restart your computer and check for any improvements.

If the issue persists, reinstalling the Visual C++ Redistributable package may be required. To reinstall the package:

1. Select the Microsoft Visual C++ package in Control Panel and click on Uninstall.
2. Click Uninstall in the Modify Setup dialog.
3. Click Finish to complete uninstallation. Repeat the process for all the Visual C++ Redistributable packages.
4. Once done, head over to the Microsoft Visual C++ Redistributable package page .
5. Download the latest version of the package available on your computer. Depending on your system compatibility, you can select from ARM64, X86, and X64 architecture versions.
6. Run the executable file to install the package and follow the on-screen instructions.
7. Once installed, restart your computer and check if MMC snap-ins are now working.

Fix the MMC Snap-In and Restore Your Administrative Tools on Windows

This error is triggered when a snap-in malfunctions, which is often a case of broken registry configuration. To fix the issue, you can delete the broken registry sub-key for the affected snap-in. Additionally, enable/re-enable the .NET Framework 3.5. If not, scan the system for file integrity issues with the DISM and System File Checker utility.

Alternatively, you can use the Remote Server Administration Tools (RSAT), which has additional features. RSAT is only available on the Pro and Enterprise edition of the Windows OS. However, you can run a PowerShell script to install it on the Windows Home version easily.

Sometimes, the error may also pop up after a Blue Screen of Death (BSOD), causing one or more apps to crash. This error often occurs if the registry configuration of the snap-in is malfunctioning. Here we show a few ways to fix to help you resolve the “MMC could not create the snap-in” error and restore administrative tools access in Windows.