"Smart Gene" is a domestic *. In addition to having the functions of ordinary *s, the most terrifying thing is that it permanently hides the remote host drive. If the control end selects this function, then the controlled end will be in a miserable state. Want to retrieve the drive? Hehe, it's not that easy! Server-side files use the HTM file icon. If your system is set to not display the file extension, then you will think this is an HTM file, which is easy to be fooled.Hot Network
"Smart Gene" is a file-related *, and a double-related *! Why do you say so? You will know after reading the following content.
After the "Smart Gene" server program is run, three files will be generated, namely:
C:\WINDOWS\
C:\WINDOWS\
C:\WINDOWS\system\
These three files use the HTM file icon, don't think they are HTM files! If your system is set to display the extensions of all files, you will find that they all have a ".exe" tail, which means they are executables!
What role do these three documents play? The file is used to load and run at startup. It is a daemon (for *s, if the client makes a connection request to a specific port on the server, the corresponding program on the server will automatically run to answer the client's request. We call this program daemon. For "smart genes", this specific port is 7511)! What does he do? Haha, they are used to associate with HLP files and TXT files respectively. If you find and delete it, it won't really clear it. Once you open the help file or text file, and will be activated! It will generate the daemon again! This is why it is difficult to remove the "smart gene" once you get it! Who would have thought it would associate two file types? ! I was fooled when I first ran the * research. After deleting and recovering the TXT file, I thought it had been completely cleaned up. But after I ran the help file one day, I was surprised to find that the "smart gene" was back! Only then did I realize that the "smart gene" is also associated with the HLP file!
"Smart Gene" clearance method:
1. Delete the file
First delete the files under C:\WINDOWS, and then delete the files under C:\WINDOWS\system. If the server is already running, you have to use process management software to terminate the process and delete it under Windows. Of course, you can also delete these files under pure DOS.
2. Delete the * self-start file in the registry
Here we delete:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"MainBroad BackManager"="C:\\WINDOWS\\"
3. Recover TXT file associations
Use Notepad to copy the following content and name it as a REG file with any name:
REGEDIT4
[HKEY_CLASSES_ROOT\txtfile\shell\open\command]
@="Notepad %1"
[HKEY_LOCAL_MACHINE\Software\CLASSES\txtfile\shell\open\command]
@="Notepad %1"
Double-click the REG file above and click "OK" in the pop-up dialog box to import these contents into the registry, thereby restoring the TXT file association.
4. Recover HLP file associations.
Use Notepad to copy the following content and name it as a REG file with any name:
REGEDIT4
[HKEY_CLASSES_ROOT\hlpfile\shell\open\command]
@="C:\\WINDOWS\\ %1"
[HKEY_LOCAL_MACHINE\Software\CLASSES\hlpfile\shell\open\command]
@="C:\\WINDOWS\\ %1"
Double-click the REG file above and click "OK" in the pop-up dialog box to import these contents into the registry, thereby restoring the HLP file association. Okay, you can talk to Smart Genes about BYEBYE!Hot Network
It should be noted that when you compiling REG files, "REGEDIT4" must be capitalized, and there must be an empty line after it. In addition, there must be no space between "4" and "T" in "REGEDIT4", otherwise all previous efforts will be wasted! The reason why many friends fail to write registry files is because they don’t notice what is mentioned above, so they should pay attention this time. Please note that if you are a Win2000 or WinXP user, please change "REGEDIT4" to Windows Registry Editor Version 5.00.
Finally, if you want to save trouble, you can download the * nemesis, which is the best deal with domestic *s.