Thank Microsoft, too much service he provided for us, then I am sorry it pirated software. First for himself 
.
In viruses, Trojans madness raging today, our small Cai Cai who suffer, when we look for help of those who defected to the anti-virus software Niubi smelling, desire it can give us a sense of security, but their performance The total wishful difficult neighbor. These small Cai Cai we go from here? Are these viruses became Trojans circulating on our baby machine? No, use our wisdom, Gates uncle use to provide our services, (and then for himself 
) combined with anti-virus software to create their own security firewall.
Now infected .exe files .exe files are associated with the most commonly used method, is more insidious way is to modify some key .exe, none of what kind of operation once the .exe there is a problem, we You may have to reinstall the system. Now we have to eliminate the occurrence of the above actions, how to handle it? Define its own type (my own definition is the file type is: .zxt), and make your own defined types, like .exe file types can be run directly. As follows:
In the "run" and enter: cmd, and press Enter. In its cmd window input: assoc .zxt = exefile can, then you will find the modified .exe file is .zxt file, double-click it is still operational. This safe? No deal after the first two can also deal with one kind does not. what can we do about it? And follow me. In the cmd window, enter: regdit. Open the Registry window press ctrl + f In the dialog box, enter exefile, configuration options: Select "item" in view only, and playing in the Match whole word bait. Exefile find this folder, select it. Click on the menu bar of the "Registry" select Export Registry. Saved as * .reg file. Then edit the * .reg file. This is the key under the window 2000 Professional Edition:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\exefile]
@="应用程序"
"EditFlags"=hex:38,07,00,00
"InfoTip"="prop:FileDescription;Company;FileVersion;Create;Size"
"TileInfo"="prop:FileDescription;Company;FileVersion"
[HKEY_CLASSES_ROOT\exefile\DefaultIcon]
@="%1"
[HKEY_CLASSES_ROOT\exefile\shell]
[HKEY_CLASSES_ROOT\exefile\shell\open]
"EditFlags"=hex:00,00,00,00
[HKEY_CLASSES_ROOT\exefile\shell\open\command]
@="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefile\shell\runas]
"Extended"=""
[HKEY_CLASSES_ROOT\exefile\shell\runas\command]
@="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefile\shell\View Dependencies]
[HKEY_CLASSES_ROOT\exefile\shell\View Dependencies\command]
@="D:\\PROGRA~1\\MICROS~3\\Common\\Tools\\DEPENDS.EXE /dde"
[HKEY_CLASSES_ROOT\exefile\shell\View Dependencies\ddeexec]
@="[open(\"%1\")]"
[HKEY_CLASSES_ROOT\exefile\shell\View Dependencies\ddeexec\Application]
@="DEPENDS"
[HKEY_CLASSES_ROOT\exefile\shellex]
[HKEY_CLASSES_ROOT\exefile\shellex\DropHandler]
@="{86C86720-42A0-1069-A2E8-08002B30309D}"
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers]
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\PifProps]
@="{86F19A00-42A0-1069-A2E9-08002B30309D}"
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\{B41DB860-8EE4-11D2-9906-E49FADC173CA}]
@=""
Then they amended as follows:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\exefileback]
@="应用程序"
"EditFlags"=hex:38,07,00,00
"InfoTip"="prop:FileDescription;Company;FileVersion;Create;Size"
"TileInfo"="prop:FileDescription;Company;FileVersion"
[HKEY_CLASSES_ROOT\exefileback\DefaultIcon]
@="%1"
[HKEY_CLASSES_ROOT\exefileback\shell]
[HKEY_CLASSES_ROOT\exefileback\shell\open]
"EditFlags"=hex:00,00,00,00
[HKEY_CLASSES_ROOT\exefileback\shell\open\command]
@="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefileback\shell\runas]
"Extended"=""
[HKEY_CLASSES_ROOT\exefileback\shell\runas\command]
@="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefileback\shell\View Dependencies]
[HKEY_CLASSES_ROOT\exefileback\shell\View Dependencies\command]
@="D:\\PROGRA~1\\MICROS~3\\Common\\Tools\\DEPENDS.EXE /dde"
[HKEY_CLASSES_ROOT\exefileback\shell\View Dependencies\ddeexec]
@="[open(\"%1\")]"
[HKEY_CLASSES_ROOT\exefileback\shell\View Dependencies\ddeexec\Application]
@="DEPENDS"
[HKEY_CLASSES_ROOT\exefileback\shellex]
[HKEY_CLASSES_ROOT\exefileback\shellex\DropHandler]
@="{86C86720-42A0-1069-A2E8-08002B30309D}"
[HKEY_CLASSES_ROOT\exefileback\shellex\PropertySheetHandlers]
[HKEY_CLASSES_ROOT\exefileback\shellex\PropertySheetHandlers\PifProps]
@="{86F19A00-42A0-1069-A2E9-08002B30309D}"
[HKEY_CLASSES_ROOT\exefileback\shellex\PropertySheetHandlers\{B41DB860-8EE4-11D2-9906-E49FADC173CA}]
@=""
Exefile that is modified in order exefileback, save and import the file, then you will find the addition of a file at the registry of a .exefileback .exefile this folder. Then under cmd input window: assoc .zxt = exefileback. Now, all .zxt .exe file and the same, then you can modify .zxt the .exe. As long as the system is abnormal. We can put our .exe file to modify .zxt. This ensures that our anti-virus software, our tools can be used. Another powerful virus will not infect a file type does not know it. Haha. . . . .
Why do not we enter the next note cmd window: .exe = exefileback it? As long as the virus is now modify the file association will easily modified .exe = virus files, so this method is not desirable.