What Causes Network Discovery to Stop Working on Windows 10?
There are several distinct causes of this problem. Each cause is tightly related to one of the methods you should use to resolve the problem so make sure you check out this list below: If Network Discovery is not working on Windows 10, it can be caused by various things reported by users. Some users have also proposed methods that can be used to resolve the problem and we decided to include them in our article. Make sure you check it out below and hopefully resolve the problem.
Solution 1: Make Sure Certain Services Start Automatically
Network Discovery is dependent on several services in order to run properly. A recent Windows Update or a change in your computer’s setup may have changed something about the startup of these services. Make sure you set them to run automatically and the problem should be resolved. You may receive the following error message when you click on Start: If this happens, follow the instructions below to fix it.
Solution 2: Turn on SMB 1.0/CIFS File Sharing Support
It seems that a recent Windows 10 update has disabled the SMB feature which is responsible for file sharing and it has definitely surprised users who started receiving this annoying error. Luckily, the problem can be fixed as easily as turning on SMB 1.0 in the Windows Features window. Follow the steps below in order to do so!
Solution 3: Enable Network Discovery through Command Prompt
If you are actively using Windows Defender Firewall, you will need to include Network Discovery in order to allow it through. Windows Firewall settings may have been reset during an update or you might have just started using it. Anyway, the problem can be resolved via a simple command in Command Prompt: If it still does, execute the following command:
Solution 4: Perform a Network Reset
There is a Network Reset option in the Network & Internet section in Windows 10 Settings which was useful to plenty of people trying to resolve the problem. It will basically reinstall all network-related drivers and reboot your system. However, the problem should be resolved afterward!
