My connection is fine and works with 8 other devices, although none run Windows 10. I ran the troubleshooter and got the message 'one or more network protocols are missing on this computer'. The detail message says 'Windows sockets registry entries required for network connectivity are missing'.
Use Network Troubleshooter to Fix Network Protocol Missing in Windows 10 Error Go to Settings Find Updates & Security section Now click on Troubleshoot icon A troubleshoot wizard will start and ask for the problem Select internet Connections and one or more network protocols are missing on this. I have several users that are missing the VMWARE bridge protocol after their machines were upgraded to windows 10 1709. I have tried multiple versions of vmware workstation, including the latest release with the same result. I have noticed this has been happening to a lot of people, but i have not come across any fixes that corrected the problem. If you are using the same 'bitness' of Windows and Outlook (both are 32-bit or both are 64-bit): Outlook 2016/2019/365 Outlook 2013 Outlook 2010 Outlook 2007. Note: Outlook does not automatically recognize the Outlook protocol when you type a url containing it into the body of any item. However, the protocol works if you set it as a hyperlink. Simply updating your PC's Windows 10 operating system could also fix this issue and restore any missing default apps. Step 1: Hit the Windows logo + I short to launch the Windows Settings menu.
Summary
In Windows 10 Fall Creators Update and Windows Server, version 1709 (RS3) and later versions, the Server Message Block version 1 (SMBv1) network protocol is no longer installed by default. It was superseded by SMBv2 and later protocols starting in 2007. Microsoft publicly deprecated the SMBv1 protocol in 2014.
SMBv1 has the following behavior in Windows 10 and Windows Server starting in version 1709 (RS3):
SMBv1 now has both client and server sub-features that can be uninstalled separately.
Windows 10 Enterprise, Windows 10 Education, and Windows 10 Pro for Workstations no longer contain the SMBv1 client or server by default after a clean installation.
Windows Server 2016 no longer contains the SMBv1 client or server by default after a clean installation.
Windows 10 Home and Windows 10 Pro no longer contain the SMBv1 server by default after a clean installation.
Windows 10 Home and Windows 10 Pro still contain the SMBv1 client by default after a clean installation. If the SMBv1 client is not used for 15 days in total (excluding the computer being turned off), it automatically uninstalls itself.
In-place upgrades and Insider flights of Windows 10 Home and Windows 10 Pro do not automatically remove SMBv1 initially. If the SMBv1 client or server is not used for 15 days in total (excluding the time during which the computer is off), they each automatically uninstall themselves.
In-place upgrades and Insider flights of the Windows 10 Enterprise, Windows 10 Education, and Windows 10 Pro for Workstations editions do not automatically remove SMBv1. An administrator must decide to uninstall SMBv1 in these managed environments.
Automatic removal of SMBv1 after 15 days is a one-time operation. If an administrator re-installs SMBv1, no further attempts will be made to uninstall it.
The SMB version 2.02, 2.1, 3.0, 3.02, and 3.1.1 features are still fully supported and included by default as part of the SMBv2 binaries.
Because the Computer Browser service relies on SMBv1, the service is uninstalled if the SMBv1 client or server is uninstalled. This means that Explorer Network can no longer display Windows computers through the legacy NetBIOS datagram browsing method.
SMBv1 can still be reinstalled in all editions of Windows 10 and Windows Server 2016.
SMBv1 has the following additional behaviors in Windows 10 starting in version 1809 (RS5). All other behaviors from version 1709 still apply:
Windows 10 Pro no longer contains the SMBv1 client by default after a clean installation.
In Windows 10 Enterprise, Windows 10 Education, and Windows 10 Pro for Workstations an administrator can activate automatic removal of SMBv1 by turning on the 'SMB 1.0/CIFS Automatic Removal' feature.
Note
Windows 10, version 1803 (RS4) Pro handles SMBv1 in the same manner as Windows 10, version 1703 (RS2) and Windows 10, version 1607 (RS1). This issue was fixed in Windows 10, version 1809 (RS5). You can still uninstall SMBv1 manually. However, Windows will not automatically uninstall SMBv1 after 15 days in the following scenarios:
You do a clean install of Windows 10, version 1803.
You upgrade Windows 10, version 1607 or Windows 10, version 1703 to Windows 10, version 1803 directly without first upgrading to Windows 10, version 1709.
If you try to connect to devices that support only SMBv1, or if these devices try to connect to you, you may receive one of the following errors messages:
The following events appear when a remote server required an SMBv1 connection from this client, but SMBv1 is uninstalled or disabled on the client.
These devices are not likely running Windows. They are more likely running older versions of Linux, Samba, or other types of third-party software to provide SMB services. Often, these versions of Linux and Samba are, themselves, no longer supported.
Note
Windows 10, version 1709 is also known as 'Fall Creators Update.'
More Information
Repair Network Protocols Windows 10
To work around this issue, contact the manufacturer of the product that supports only SMBv1, and request a software or firmware update that support SMBv2.02 or a later version. For a current list of known vendors and their SMBv1 requirements, see the following Windows and Windows Server Storage Engineering Team Blog article:
Leasing mode
If SMBv1 is required to provide application compatibility for legacy software behavior, such as a requirement to disable oplocks, Windows provides a new SMB share flag that's known as Leasing mode. This flag specifies whether a share disables modern SMB semantics such as leases and oplocks.
You can specify a share without using oplocks or leasing to allow a legacy application to work with SMBv2 or a later version. To do this, use the New-SmbShare or Set-SmbShare PowerShell cmdlets together with the -LeasingMode None parameter.
Note
You should use this option only on shares that are required by a third-party application for legacy support if the vendor states that it is required. Do not specify Leasing mode on user data shares or CA shares that are used by Scale-Out File Servers. This is because the removal of oplocks and leases causes instability and data corruption in most applications. Leasing mode works only in Share mode. It can be used by any client operating system.
Explorer Network Browsing
The Computer Browser service relies on the SMBv1 protocol to populate the Windows Explorer Network node (also known as 'Network Neighborhood'). This legacy protocol is long deprecated, doesn't route, and has limited security. Because the service cannot function without SMBv1, it is removed at the same time.
However, if you still have to use the Explorer Network in home and small business workgroup environments to locate Windows-based computers, you can follow these steps on your Windows-based computers that no longer use SMBv1:
Start the 'Function Discovery Provider Host' and 'Function Discovery Resource Publication' services, and then set them to Automatic (Delayed Start).
When you open Explorer Network, enable network discovery when you are prompted.
All Windows devices within that subnet that have these settings will now appear in Network for browsing. This uses the WS-DISCOVERY protocol. Contact your other vendors and manufacturers if their devices still don't appear in this browse list after the Windows devices appear. It is possible they have this protocol disabled or that they support only SMBv1.
Note
We recommend that you map drives and printers instead of enabling this feature, which still requires searching and browsing for their devices. Mapped resources are easier to locate, require less training, and are safer to use. This is especially true if these resources are provided automatically through Group Policy. An administrator can configure printers for location by methods other than the legacy Computer Browser service by using IP addresses, Active Directory Domain Services (AD DS), Bonjour, mDNS, uPnP, and so on.
If you cannot use any of these workarounds, or if the application manufacturer cannot provide supported versions of SMB, you can re-enable SMBv1 manually by following the steps in How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows.
Important
We strongly recommend that you don't reinstall SMBv1. This is because this older protocol has known security issues regarding ransomware and other malware.
Windows Server best practices analyzer messaging
Windows Server 2012 and later server operation systems contain a best practices analyzer (BPA) for file servers. If you have followed the correct online guidance to uninstall SMB1, running this BPA will return a contradictory warning message:
You should ignore this specific BPA rule's guidance, it's deprecated. We repeat: don't enable SMB 1.0.
Additional references
How To Fix 'Network Protocol Missing' Problem On Windows 10
The word protocol is derived from the Greek 'protocollon', meaning a leaf of paper glued to a manuscript volume that describes the contents. Network protocols are something we use via computer systems every day, maybe every minute, even if we are not sure exactly what they are. Network protocols are procedures and formats that define communication between two or more devices over a network. They include mechanisms for devices to identify and make connections with each other, specifying how data is packaged into messages sent and received. Network protocols must be confirmed and installed by both sender and receiver to ensure network or data communication. There are many protocols in use extensively in networking, and they are often implemented in different layers. Without network protocols, instant messages would not be delivered to your friends, emails would not reach their destinations, and websites would not appear on your screen.
When a network protocol (or more that one protocol) is missing from your computer, an error such as 'One or more network protocols are missing on this computer' error occurs when running Windows Network Diagnostics. This appears when your system cannot connect to the Internet and you click the 'Diagnose' button. This might be a fault of your Internet Service Provider, but if other devices on the same network are working properly (and connecting to the Internet), then it is probably an issue with your computer. If a network protocol is missing, you will probably be unable to share files or data between network computers, or unable to access the Internet at all. In this article we show how you can recover your Internet connection.
Table of Contents:
It is recommended to run a free scan with Malwarebytes - a tool to detect malware and fix computer errors. You will need to purchase the full version to remove infections and eliminate computer errors. Free trial available.
Restore Default Settings
One option is to reset network protocols to their default settings by resetting the TCP/IP stack. The TCP/IP stack is a complete set of networking protocols. To reset it, use commands within Command Prompt. Firstly, to open Command Prompt, type 'command prompt' in Search and right-click on the result. Select 'Run as administrator' from the drop-down menu to run it with administrator privileges.
Now, type these two commands (pressing Enter after each): 'netsh int ip set dns' and 'netsh winsock reset'. Then, exit Command Prompt by typing 'exit' and pressing Enter, or simply close the Command Prompt window and check if this has helped to solve the problem.
Reinstall Your Network Adapter Driver
You may get the 'Network protocol is missing' error due to a faulty network driver. You can try to uninstall the network adapter driver and then let your Windows 10 operating system reinstall it automatically the next time you start Windows. To uninstall your network adapter driver, to go to Device Manager. Type 'device manager' in Search and click the 'Device Manager' result.
In the Device Manager window, find 'Network adapters', expand it, right-click on your network device, and then choose 'Uninstall' from the drop-down menu.
You will be asked to confirm the uninstallation. Click 'OK'. Mark the 'Delete the driver software for this device' checkbox if you see one.
You will need to restart your PC for the changes to take effect. Restart your computer and see if this has helped to solve the problem.
Restore Network Components
This may be the easiest way to fix the 'Network protocol is missing' problem by executing commands in Command Prompt. First, open Command Prompt by typing 'command prompt' in Search and right-click on 'Command Prompt'. Select 'Run as administrator' to run it with administrator privileges. In the Command Prompt window, type 'ipconfig /release' and press Enter to execute. Then, type 'ipconfig /flushdns' and 'ipconfig /renew' commands, pressing Enter after each.
Then, exit Command Prompt by typing 'exit' and pressing Enter or simply close the Command Prompt window. Check if this has helped to solve the problem.
Disable NetBIOS
NetBIOS is an acronym for Network Basic Input/Output System. It provides services related to the session layer of the OSI model, allowing applications on separate computers to communicate over a Local Area Network (LAN). It is possible that disabling NetBIOS will fix the 'Network protocol is missing' issue on your computer. First, open Control Panel by typing 'control panel' in Search.
In the Control Panel window, click 'Network and Internet'.
Once you are in the Network and Internet window, select 'Network and Sharing Center'.
Internet Protocol Windows 10
You will see your Internet access type and connection near the top-right corner. Click on it.
You will see your connection status window. Click on 'Properties'.
In the network connection Properties window, find 'Internet Protocol Version 4 (TCP/IPv4)'. Select (highlight) it and click 'Properties'.
In the Internet Protocol Version 4 (TCP/IPv4) Properties window, click 'Advanced'.
In the Advanced TCP/IP Settings window, click 'WINS' tab and select 'Disable NetBIOS over TCP/IP'. Click 'OK' to save these changes and check if the problem is solved.
You can also attempt to resolve the 'Network protocol is missing' problem by choosing to obtain IP addresses automatically, rather than using a static IP address. You can manage this following identical steps. In the Internet Protocol Version 4 (TCP/IPv4) Properties window, select the 'Obtain and IP address automatically' option if it is not already set to this.
Import Winsock Keys
For this solution, you must use a computer that does not have the same connectivity problem. If you are using Windows 10 on a computer with a network problem, you do not need to have Windows 10 on the other machine (it can be earlier versions of Windows such as Windows 8 or Windows 7).
This solution includes modifying the system registry. The Microsoft Registry Editor (regedit.exe) enables you to view, search for, and change settings in your system registry, which contains information about how your computer runs. Follow these steps carefully to avoid damaging your operating system. Open Registry Editor on the computer that does not have the 'Network protocol missing' error. To open Registry Editor, type 'run' in Search.
In the Run dialog box type 'regedit' and click OK to open Registry Editor.
Once Registry Editor is opened, follow this path: 'HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/', expand Services catalog to find 'Winsock' and 'Winsock 2', and right-click on both to export them by selecting 'Export' from the drop-down menu. Name the registry files and locate where you wish to save them. Then, copy or move them onto your USB drive.
When registry files are copied into your USB drive, access the computer that has network issues. Uninstall the network driver from, open Registry Editor again, and then look for 'Winsock' and 'Winsock2' catalogs under 'Service' catalog using the same path as we mentioned before ('HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/'). Delete these two catalogs by right-clicking on both and selecting 'Delete' from the drop-down menu. In case you need these original registry keys, back them up by exporting. Restart your computer when finished.
When your operating system is restarted, go to the 'HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/' location and import the keys stored on your USB drive into this location, and then close Registry Editor. Open Command Prompt by typing 'command prompt' in Search and right-click on the 'Command Prompt' result. Select 'Run as administrator' to run it with administrator privileges.
In the Command Prompt window, type in the following command: 'netsh winsock reset' and press Enter on your keyboard to execute it. Close Command Prompt and restart your computer. Check if this has helped to solve the 'Network protocol missing' problem.
Restart Your Router
In none of the above steps help you to solve the problem, try restarting your router. Simply turn it off, and then on again. You can also try resetting your router - this will restore your router to the factory settings. Use the 'Reset' button on your router to do this (usually on the back).
We hope that these methods resolved your network problem and you are now able to access the Internet.
Video Showing How To Fix Network Protocol Missing Problem: