Solution to communication port initialization failure in Windows 7

Today, I slept a little late. After washing, I quickly left the dormitory to catch the bus. Once the company turned on the computer, 360 of the software jumped out and checked whether the XX process was to be blocked. The problem is that no matter if you open QQ or IE, as long as the software is related to the network, double-click the software to bring up the frustrating prompt "Windows communication port initialization failed ". At this time, I felt like pulling the cold and pulling the cold. Was the virus-infected USB flash drive inserted yesterday (then the USB flash drive was properly handled ). I thought that 360 was blocked. It should be able to recover the block, but a terrible thing happened. Once 360 was opened, it was automatically closed in a few seconds. It was amazing and incredible! It is estimated that it is also the reason for the communication port. I found it online and found that it may be a problem with Windows Socket. I have to fix it. Repair tools that can be provided on the network cannot be used because they are old and run on win7. Of course, some of them are acceptable. Super Rabbit and master optimization will certainly provide Windows Socket repair tools or LSP tools (not very familiar with the role of this job, but only know that it is used to repair XX items ), but you cannot always install these things for one fix. Later, we should think that Windows should also provide tools of the type, at least the CMD command and other restoration methods. Later, I found a method under XP and entered regsvr32 Winsock. dll in the running process. But it is useless. Later, Google + Baidu, Huang Tian, had no worries, and finally found a method, but it is also a method under XP, but it also seems to be applicable to win7. At least I can access the Internet now... the method is found on the Internet. The following is a reference for everyone. I hope that friends who encounter such problems will be able to avoid detours and return to the Internet smoothly.

 

Solution:

Method 1. Use LSP 360 to fix the vulnerability. If you are prompted that "LSP is not abnormal and you do not need to fix it", but you still cannot get on the network, run the ping command and the IP address appears (?), You cannot ping the internet. Then you can use the "Restore Winsock LSP to initial state" function of 360.

Method 2: it is a common method that everyone is familiar with. Use the lspfix tool to fix it when the network is disconnected.

Method 3. There are two newly added netsh commands in Windows XP Service Pack 2.

"Netsh Winsock reset catalog this command resets the Winsock directory to the default configuration. This command is useful if an incorrect LSP is installed that may cause network connection loss. Although you can use this command to restore the network connection, you should use it with caution, because previously installed LSP will need to be re-installed.

"Netsh Winsock show catalog this command will display the Winsock LSP list installed on the computer.

Therefore, we can use the netsh Winsock reset command to reset Winsock without any auxiliary tools.

 

LSP introduction:

 

Winsock LSP stands for Windows Socket Layered Service Provider (hierarchical service provider), which is the door for socker communication in the underlying Windows network. Some rogue software can add itself to intercept, access, and modify network data packets, add advertisements at will, and get your browsing habits. here the trojan is added, and the consequences can be imagined. Because the LSP works at the underlying layer, No matter what browser you use, you cannot escape it. When the DLL file in LSP is deleted, it will become unable to access the Internet.

Location of the LSP service in the Registry: HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/Winsock/parameters/namespace_catalog5/catalog_entries. DLL) and NTDs components (winrnr. DLL), their items are 000000000001 and 000000000002, which indicate priority. If a malicious program wants to hijack, you only need to change its items to 000000000001, after the system items are pushed back in sequence, malicious programs can be prioritized.