Perfectly solves the problem of MMC. EXE error caused by viewing application logs in Event Viewer

Today I am tossing again. Just a few days after reinstalling the system, I accidentally found that when I used the "Event Viewer" managed by my computer, I only needed to select the "ApplicationProgram"This branch, MMC. exe will crash immediately ,:

 

 

So I made another mistake. Even if I don't think there are 90% or 70% Windows users don't even know that there is "Event Viewer" in windows, but as long as it falls on my host, then it's uncomfortable ...... After five minutes of being uncomfortable and making sure that the crash reproduction rate is 100%, I started to get involved again ......

The following are the tricks I have used:

1. Clear application logs and open the event viewer. Useless.
2. Copy the application log file from another normal win2003 SP1 ent to overwrite the original file. Useless.
3. Copy an MMC. EXE file from another host to overwrite the original file. Useless.
4. The modules with errors found in the error report are NTDLL. dll and kernel32.dll. Copy from another host to overwrite it. Useless.
5. Run the regsvr32 command to register all DLL files in the System32 directory. Useless.
6. Use the SFC/scannow command to repair system files. Useless.
7. Install service pack1 again (though it is already integrated with SP1 ). Useless.
8. Make the ultimate effort! Ghost resumes the newly installed system ...... It's useless to enter the system in 5 minutes !! I collapsed completely.

 

After N's hard work was in vain, I once again offered the ultimate Bi killing technology-Google + Baidu. This time, I still had some BS Baidu to help me a lot, I found a post on a website describing the same problem as me, but no one answered it. However, I was lucky to find that this post was transferred from csdn, so I quickly arrived at csdn.CommunitySearch in it. Two of the posts are about the same problem as me. One is not followed, but very lucky is ...... The author of another post found a solution by himself. In fact, the cause of this problem is very fainting ......
......
......
Because I installed SERVER-U 6.3 in Chinese !!

The error is not in the SERVER-U, the original version is no problem, but after the Chinese patch is installed, this problem occurs. In uninstall the English version of the SERVER-U, and then installed an English version, all the perfect solution!

So my system became perfect again !!

Finally, I would like to thank Baidu, csdn, the smart landlord (in fact, he uninstalled the software one by one), and CCTV, MTV, and channel [v]. let me have another feel fresh! In addition, I once again deeply realized the principle that primary school teachers have always taught us, that is, how important is perseverance !! (Voiceover: Why does another obsessive-compulsive disorder come out? It's strange, why do we say "you" nees ......)