The group policy prompts the management unit initialization failure in an authorized solution

The problem in this article is very simple, but I can see my solution and exploration process from here. I will write as detailed as possible to show you my ideas for solving the problem. In particular, the majority of beginners actually have many problems for you. there is no need to try to solve the problem as soon as you find it.

Today, I saw a brother asking about the Registry ban on the School Forum :)
I compress a script for unblocking the Registry to him, and consider that he is an operating system above NT and can be unbanned through the Group Policy. So I want to use my machine to capture a picture for him. he looks at the specific location...
The pictures I imagined were as follows:
Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233109477.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61UI0-0.gif "width = 564 onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
It depends on you to see how beautiful I think... so I ran gpedit. msc on the system.
Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233118227.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61Q3Z-1.gif "onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
As a result, such a scene exists...

Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233118472.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61W354-2.gif "onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
After you click OK, the Group Policy you enter is like this and there is no way to use it ....
Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233118830.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61Q217-3.gif "width = 564 onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
This is all the symptoms of the problem. I have already described how the above picture was taken again? Haha, I was in a hurry to answer my friend's questions, so I caught the figure under the virtual machine... now let's go back and study our own questions...
I have said that no matter when a computer goes wrong, it may give you a piece of feedback. Sometimes it may sound a little subtle, even a sound, but it should be good at capturing details when dealing with problems... let's see what clues the system has given us :)
When a problem occurs, we obtain the following information:
First, the computer tells us that the Group Policy failed to run and the CLSID in the registry is related to 8fc0b734-a0e1-11d1-a7d3-109f87571e3.
Second, the cause of the failure is that the management unit initialization failed.
Third, the system says that the cause of the creation failure is probably that it is not correctly installed.

Now, many of my friends think that the system is not properly installed? Hey, I have never used Group Policy since I installed the operating system) so I don't know when the problem occurs. I can't confirm whether it is an installation problem. However, I also reinstalled it a few days ago, and I was the most lonely. I just re-installed it a few weeks ago.
Now let's analyze the information provided by the system. What do we know?
Article 1: We can go to the Registry-related project in the system based on the CLISD value to see if something went wrong. Fortunately, XP in my virtual machine can be used for comparison.
Article 2: Management Unit initialization failure may be caused by some loaded dll Problems
Article 3: The dll may not be correctly installed, which means it may need to be re-registered. It may be wrong for some reason.

Then let's take a look at the materials we have mastered.
First, we know that the Group Policy Name in English is Group Policy. This is good for us to go to a foreign site to find information on microsoft official website.
Second, we know how to register and uninstall the dll file regsvr32 command is our core assistant.
Third, many dll management and file management in Windows are related to html "target = _ blank> filemgmt. dll. This file plays an important role in this file, especially in group policies.
Fourth, we know that gpedit. dll is called by gpedit. msc.

Now let's start solving the problem...
First, we suspect that the Registry is damaged because I often perform registry modification tests on EvilOctal, and it is not affected by the alpha Beta software of fengze...
So I came to the registry project and found that there were no problems... later, I checked the system environment variables and found that the default paths were normal. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233118994.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61VO0-4.gif "width = 564 onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
Slide to c: windowssystem32. The next check shows that gpedit. dll is also there and there are no signs of damage. It is estimated that the problem is not caused by file corruption or registry.
Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233119126.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61U437-5.gif "width = 564 onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
One of the clues is broken: (now we can only suspect that the dll file has been registered, so let's register it again. So I entered
Regsvr32 gpedit. dll to re-register the dll
Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233119221.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61S329-6.gif "onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
The error message "cannot be registered" is displayed ...:(
Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233119206.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61WQ0-7.gif "onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
Is it true that my EvilOctal has a bad character? Although I often do a lot of bad things from scratch, I am always better than dahubaobao and ice blood. If both of them don't have a problem, I don't believe it, so I am failing the second method. ..
Analyzed the reason why the registration fails.
Since gpedit. dll is normal and under system32, it should be okay. Is it necessary to clarify the filemgmt. dll Directory? So I directly registered filemgmt. dll. It was successful and then registered gpedit. dll or failed...

Instead, I thought of copying a gpedit. msc from another machine. Isn't that okay? (Later I learned that many people will not be able to copy the method sometimes )... so I put gpedit from the virtual machine. msc copies a copy to overwrite the original one in the system...
Running... still failed! The prompt is exactly the same as the original one...
Here we come to the conclusion that gpedit. msc is good. That is to say, this method on the evil baboons technical forum can be ruled out.
Http://www.eviloctal.com/forum/read.php? Tid = 12379
Because msc itself is normal, there is no problem of re-establishing msc... since the file is intact, it must be the problem of calling other files. Therefore, we should finally determine whether to solve the problem by hitting register gpedit. if the dll is successfully registered, the problem may be solved!

Suddenly, when registering gpedit. dll, the system prompts that the specified module could not be found. So the search system looked for filemgmt. dll and found that filemgmt. dll was not found in the system32 directory. No wonder that it could not be found :(
In fact, I guess that the Group Policy may need to call this file in the same directory... there is no way to test it in the last line...
So we copied filemgmt. dll from the searched location to system32 and registered filemgmt. dll and gpedit. dll...
Screen. width-461) window. open (http://up.2cto.com/ OS /200507/20050712233119186.gif); "src =" http://www.bkjia.com/uploads/allimg/131204/1Q61V096-8.gif "onload =" if (this. width> screen. width-460) this. width = screen. width-460 "border = 0>
Once again, the running group policy is restored to a normal state. Everything is in good condition ....
Later found that such problems network solution explosion, such as http://www.tryboy.nethttp: // www.bkjia.com/computer/ OS /200504/492.html
But since I have no problem, I don't want to study it. It's really good. I forgot to hurt myself ....

Postscript
Everyone must be confused about this article. filemgmt. dll is a bit strange. Isn't filemgmt short for file management? For more information, see the question of "Evil gossip information security team :)
Http://www.eviloctal.com/forum/read.php? Tid = 12380