1. We find the “command prompt” in the attachment in the start menu bar, then right-click and select “Run as administrator”.
2. From the command line, we type: “NETSH WINSOCK RESET CATALOG”.
3. After hitting enter, the interface as shown in the figure will appear. You are prompted to reset the WinSock directory successfully. You need to restart the computer to complete the reset.
4. After restarting the computer, you will find that your QQ, other software and network can work normally.
2. From the command line, we type: “NETSH WINSOCK RESET CATALOG”.
3. After hitting enter, the interface as shown in the figure will appear. You are prompted to reset the WinSock directory successfully. You need to restart the computer to complete the reset.
4. After restarting the computer, you will find that your QQ, other software and network can work normally.
Read More:
- OSD deployment failure code (0x00000001) 0x80004005
- Solution of OpenGL initialization failure after upgrading motherboard and CPU
- Solution to the failure of ROS noetic initialization (rosdep init)
- CMDTUX_CAT:1685: ERROR: Application initialization failure
- 1067 – Invalid default value for ‘sex‘1366 – Incorrect string value: ‘\xE6\x8A\x80\xE6\x9C\xAF…‘ f
- error:X11 initialization Failed solutions
- RuntimeError: Expected hidden[0] size (x, x, x), got(x, x, x)
- QQ browser open automatically appear two web page solution
- Solution of visdom startup failure in Windows 10
- VirtualBox for macOS NS_ ERROR_ Failure (0x80004005) problem solving record
- VirtualBox NS_ERROR_FAILURE (0x80004005)
- Resolve nginx startup failure
- C / C + + error handling (document): unhandled exception: 0xc0000005: access violation while reading location 0x00000000
- windows update error 0x8024401c
- net core HTTP Error 502.5 – ANCM Out-Of-Process Startup Failure
- C++ error: jump to case label crosses initialization
- PLSQL Startup Error: Initialization error [How to Solve]
- Record of solving the failure of installing ie11 (9c59) under 64 bit Windows 7 system
- [Solved] emulator: glteximage2d: got err pre 🙁 0x502 internal 0x1908 format 0x1908 type 0x1401
- Solve the startup error “something Wen wrong” of NVIDIA geforce experience