The computer is on which MMC appears that the snap in cannot be created

It is a framework program of the system management program, and the full name is Microsoft Management

Console, which provides a platform for hypervisors with the MSC extension to run, such as Group Policy, System Inventory, Task Manager, as well as print management, local security policies, etc., as well as this process.

1. Right-click on the "My Computer" icon and select "Properties" to switch to the "Advanced" tab in the system properties window that opens, and click to open the environment variable in the Advanced tab.

2. In the pop-up environment variable window, pull the drop-down box, find and click to select the path variable name, and then click (n) to set it.

3. In the pop-up system variable window, copy the variable value and modify it to: %systemroot% system32; %systemroot%;%systemroot%\system32 wbem.

Start running the input "regsvr32

loadlibrary (failed, the specified module could not be found that.)

Copy the file from the C: Windows System32 WBEM directory to the C: Windows System32 directory, and re-register it to open it.

Preparation materials: computer, Windows 10

1. On the Windows 10 system desktop, click the "Start Windows System Control Panel" menu item in turn.

2. Next, we open the control panel window of Windows 10 and click on the "System" icon here.

3. In the system window that opens, we click on the "Advanced System Settings" shortcut link on the left sidebar.

4. Next, we will open the advanced settings window in the system properties, and click the "Environment Variables" button here.

5. In the opening environment variable setting window, we select the "path" setting item below, and then click the "" button.

6. In the window that opens, we make sure that there are the following three items in **%systemroot% system32,%systemroot%,%systemroot% system32 wbem, and finally click the OK button to solve it.

Summary. Win7 Group Policy Prompt MMC Unable to Initialize Snap-in Workaround.

The management module MMC cannot initialize the snap-in.

Win7Win7 Group Policy Prompts MMC Unable to Initialize Workaround for snap-in.

Method 1: 1. Open the "Start" menu, enter "cmd" in the search box, then right-click the icon and select "Run as administrator"; 2. Enter the following instructions separately and press the enter key to execute. regsvr32 If you can't register, add "C:."

Copy the files in the Windows System32 WBEM directory to the C: Windows System32 directory and repeat the above steps.

Method 2: Use the "sfc scannow" command in the cmd command prompt to repair the system. Method 3:

Open "Run" in the Start menu, type in "regsvr32 C: Windows System32 and press Enter." Method 4:

1. Enter the "C: Windows System32" directory and find the three files. 2. Right-click", select "Properties--Security", modify the owner to what you are using, and perform the same operation for the other 2 files. 3. Then delete these three files, and copy the three files to "C: Windows System32" on other win7 system computers to your own computer;

4. Restore the "System Protection Permissions" of the above three files, right-click one of the files, and select "Properties--Security--Advanced"; 5. Change the permission, check the checkbox at the bottom (do not select), prompt the deletion permission, and confirm the deletion; 6. At this time, the permission is empty, find a dll file in the "C: Windows System32" directory, refer to its permissions, and add "administrators, users, system" and other permission parameters; 7. When the trustedinstaller permission is added, the object name should be entered"nt service\trustedinstaller

MMC's inability to create snap-ins is an uncommon problem, and it is usually a problem of uninstalling system components and software conflicts, and we can try to re-register them with the registry or modify the corresponding environment variables to solve them.

Method 1:

1. Click ".RunFailed - The specified module could not be found, the file was copied from the Windows System32 WBEM directory to the Windows System32 directory, and then re-registered to open itFinish.

3. Or you can go to another computer to copy the file - put it in the systemc:\windows\system32directory.

Method 2:

But Tan Liang laughs can be".Environment variables"Caused.

1. Right-clickMy computer, and then clickattributes

2. In ".Advanced system settingstab, clickEnvironment variables

3. In ".System variables"Down, double-click" scumbag pantspath environment variable

4. Variable value input:%systemroot%\system32;%systemroot%;%systemroot%\system32\wbem

Note: If other system variables appear, please do not delete, please do not delete, use ".(semicolon) with other variables.

5. Click ".OK, and then clickOK"In fact, the environment variables in the path are determined according to the installation location of the software, and they are used between different environment variables.""If you need it, you can put the environment variables in front of you!

PS: If you accidentally omit an environment variable, it may cause some programs to not work properly.

If you want to change some settings on your computer for Windows 10 users, you can just open the policy group. However, recently, some friends have reported that they can't set the group policy in the win10 system, prompting Huai: MMC can't create an administrative unit, and the administrative unit may not be installed with a forehand.

What to do? Actually, this problem is caused by an error in the environment variables. Below, I will share with you the specific solution.

Recommended:

The steps are as follows:

1. Click the right Bibi key in the start menu and click "System";

2. Click "Advanced System Settings" on the left side of the property;

3. Click [Environment Variables] at the bottom;

4. Double-click "Path" in the above box, modify the variable value to: %UserProfile% AppData Local Microsoft WindowsApps, and click OK;

5. Double-click to open the "path" in the box below;

6. Make sure there is a box in:

SystemRoot% System32, %SystemRoot%, %SystemRoot% System32 WBEM, %SystemRoot% System32 WindowsPowerShell, if any value is missing, we just click "New" and then copy and paste the missing values and delete the other redundant values.

That's it for Windows 10 to prompt MMC that it can't create snap-ins. If you are in need, you may wish to follow the above steps to have a look.

If you get the error message "MMC could not create snap-in" on Windows 10, you can try the following solutions:

1.Check User Account Control (UAC) settings: Make sure UAC is set to the default level. Open the Control Panel, search for and click on "User Account Control Settings". Adjust the slider to the default level and click "OK" to save your changes.

2.To repair system files, open a command prompt (run as administrator), type in the command "sfc scannow" and press enter. The system will scan and repair any corrupted system files.

3.To reset MMC settings: Open a command prompt (run as administrator), enter the command "mmc resetuserdata" and press enter. This will reset the user data for MMC.

4.To re-register the MMC component: Open a command prompt (run as administrator), enter the following command and press enter:

regsvr32

regsvr32

regsvr32

regsvr32

regsvr32

5.To create a new snap-in: Open a command prompt (run as administrator), enter the command "mmc" and press enter. Then, click on the File menu, select Add Remove snap-in, and select the desired snap-in to do so.

If the above methods still do not solve the problem, it is recommended that you try to update the Windows operating system or contact Microsoft Support for further assistance.

Group Policy is one of the main tools that Win7 users often use in the process of operating and using computers. However, when using Group Policy, sometimes there are some failures that users don't know how to solve, such asNotebook win7 systemUsers reported that the error message "MMC could not create snap-in" was displayed when opening Group Policy. This error may be caused by a user modifying an environment variable on the computer, or an environment variable on the computer being maliciously modified.

So what should we do in this situation? Let's take you to understand the specific solution!

Workaround:

1. Right-click the "computer" icon on the desktop of win7 system and select the "properties" option;

2. Switch to the "Advanced" tab in the system properties window opened by the branch;

3. Click the Open Environment Variable button in the Advanced tab;

4. In the pop-up environment variable window, pull the drop-down box, find and click to select the path variable name;

5. Click the twist to set;

6. In the pop-up window of the system variable fierce branch quarrel, copy the variable value and modify it to: %systemroot% system32; %systemroot%;%systemroot%/system32/wbem；

7. Press the OK button.

The above is the notebook win7 system to solve the group policy prompt mmc can not create the way of the snap-in, if the user encounters the above fault problems, you may wish to follow the above method to set up.