Tagged: Network Protocol, Windows 10
- This topic has 0 replies, 1 voice, and was last updated 11 months, 3 weeks ago by
Tobi.
- AuthorPosts
- January 24, 2020 at 4:53 pm #84557Participant@tobi
The Windows 10 Operating System is one that has steadily remained a favorite for every PC user. Although this is the case, the OS has its fair share of annoying issues. In this article, we will be discussing a network problem on Windows 10 that indicates when Network Protocols are missing.
This issue is network-based and has its own variety of possible solutions like other Windows 10 errors. We will discuss some of the best solutions that are available to fix this issue.
How you can fix Network Protocol missing error in Windows 10
The Network protocol missing error on Windows 10 has some usual suspects that might cause the issue. Some examples of these are:
“Could not add the requested feature”
“One or more network protocols are missing on this computer WiFi”
“Windows sockets registry entries required for network connectivity are missing”
“Network protocols missing error Windows 10“
“One or more network protocols are missing on this computer”Therefore, regardless of the error code, you can use one of the solutions we have provided in this article.
1. Disable your antivirus software temporarily
Disabling your antivirus software is never the best idea in many scenarios. However, troubleshooting seems to be an exception. Some users have reportedly fixed the issue by disabling their antivirus. Specifically, Kaspersky Internet Security 2016 users have had their issues resolved.
For Kaspersky Internet Security 2016 users, temporarily disable your antivirus or try using different antivirus software. If you are not up for a new program, reinstalling the antivirus might also do the trick.
2. Restore your network protocols to their default settings
If that solution didn’t work, you can try resetting the network protocols to their default settings. For this, you’ll have to reset the TCP/IP stack. Follow our instructions to learn how:
1. Press the Windows Key and search for “cmd”, right-click on the top result and Run as administrator.
2. Once you’ve opened Command Prompt, enter these lines:
netsh int ip set dns
netsh winsock reset
3. Close the Command Prompt and check if the issue is resolved.
3. Disable NetBIOS
1. Open the Control Panel, go to Network and Internet, select Network Connections.
2. Right-click on the network adapter and choose Properties.
3. Highlight the IP v4 (TCP/IP) and select Properties.
4. Click on Advanced.
5. Go to the WINS tab, in the NetBIOS settings, choose the option to Disable NetBIOS over TCP/IP.
6. Click on OK to save your new settings.
Lots of users have suggested that this issue can be resolved by obtaining your IP address automatically rather than through a static IP. To do this, follow the three steps from this solution.
Once you open IPv4(TCP/IP) Properties, you’ll have the option to select between an Automatic IP address and a static IP.
4. Use the Command Prompt
1. Press the Windows Key and search for “Command Prompt”, right-click on the app and select Run as administrator.
2. Type in this command and press Enter to run it:
netcfg -d
3. It might take a while, so wait for the process to complete. Once its completed, restart your computer and your issue should be resolved.
Additionally, users have suggested using this command:
netsh int ipv4
Start the Command Prompt as an administrator and type the command. Press the Enter key.
Restart your computer and check if the issue persists.
5. Use the Command Prompt with sc.exe
This isn’t exactly a permanent fix. You might need to revert your changes from this step if the problem starts after a Windows 10 update. Follow this quick guide:
1. Run Command Prompt as an administrator.
2. Type these lines in Command Prompt and press Enter to run them:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Once you’ve entered the lines in Command Prompt, the issue might be resolved. When the issue comes back after a Windows 10 update, you have to restore your changes to the default settings. Follow these instructions to do so:
1. Run Command Prompt as an administrator.
2. Enter the following lines below and press Enter to run them:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto
6. Import Winsock keys from another computer
This solution is quite advanced and requires some care. If you’re not careful with the way you modify the registry, it’s best to avoid this method. If you make a mistake, you might damage your operating system.
For this, you’ll a computer without the Network Protocols issue. It does not have to be a Windows 10 computer and you can use Windows 8 or Windows 7 computers. This is what you should do:
1. On the Windows Registry Editor, find following keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
2. Export the keys to an external USB driveFor the next step, do the following:
a. Switch to the computer with the Network Protocols issue.
b. Uninstall the network driver.
c. On the Windows Registry Editor, find following keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
d. Export them in case of a backup. Once you’ve done this, delete the keys.
e. Restart the computer.
f. When you’ve restarted your PC, insert the USB drive with the Winsock keys from another computer.
g. Switch to the Registry Editor again.
h. Open the location where the keys were.
(HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services)
i. If the Winsock2 key returns, delete it again.
j. Import these keys from your USB:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
k. Close the Registry Editor.
l. Open Command Prompt as an administrator and run this command:
netsh winsock reset
m. Restart your computer.7. Restore your network router and check the cable
If the steps detailed above did not solve the problem, resetting your router might do the trick. Turn it off for a few minutes, then switch it on.
Also, try changing the LAN cable used for connections from your router to your computer.
Lastly, reset your router to its factory settings by pressing a small button at the back (some routers may differ in configuration, so have your manual ready as a guide.)
8. Reinstall the Network Adapter
After you’ve tried the steps above, reinstalling your Network Adapter might be the solution.
Follow these steps to know how:
1. Hold your Windows Key and press R to open the Run box.
2. Type this “hdwwiz.cpl” in the input field and click on Ok.
3. Expand the Network Adapters drop-down list, right-click on your Ethernet card and Uninstall the device.
4. Click on Uninstall when you see the confirmation dialog.
5. Reinstall the network adapter by using the driver that comes with the hardware.
9. Use the Network Troubleshooter
If you’ve installed any version of Windows since the Creators Update, there is a new troubleshooting tool available. The tool is designed to handle a variety of issues with the Windows OS. This includes many regular network errors.
Follow these instructions to run the troubleshooter:
1. Open the Settings page.
2. Click on Updates & Security, then select Troubleshoot.
3. Choose Internet Connections.
4. Follow the sequence of instructions as they appear on your screen and let the process complete.
5. Restart your PC.If you are still experiencing the problem, try this with the Network Adapter option, rather than Internet Connections.
10. Restore network components
Try resetting these network components:
1. Run the Command Prompt as an administrator.
2. Once Command Prompt is running, enter these commands and press the Enter key:IPconfig /release
IPconfig /flushdns
IPconfig /renew
11. Update your BIOS
Some users have also reported that updating the BIOS can be a valid solution for the problem. Before you do this, changing things in your BIOS can be risky and a wrong move can cause irreversible damage to your motherboard. So, try this step with caution.
- AuthorPosts
- You must be logged in to reply to this topic.