Fix PCs no longer recognized in network after Windows 10 version 1803 upgrade
If you run the new version of Windows 10 already, for instance on a PC with an Insider Build installation of the new operating system version, you may have had issues with the detection of PCs and devices in the local area network.
While there are plenty of possible explanations for PCs not showing up anymore when you try to access them, chance is high that a change in the Spring Creators Update version of Windows 10 is responsible for the issue.
Microsoft removed the Homegroup functionality from Windows 10 version 1803; the issue, however, may affect non-Homegroup PCs and PCs that used the Homegroup functionality that Windows provided.
Usually, you should be able to access devices in the network through their IP address or name, but this may not work properly anymore in Windows 10 version 1803.
Solution for network connectivity issues in Windows 10 version 1803
You need to check and change the status of a networking related service in the new version of Windows 10.
Function Discovery Resource Publication is a networking service that ensures that devices are discovered in a local computer network.
Publishes this computer and resources attached to this computer so they can be discovered over the network. If this service is stopped, network resources will no longer be published and they will not be discovered by other computers on the network.
The service is set to manual both in Windows 10 version 1709 and Windows 10 version 1803, but it may not be started by the system anymore in Windows 10 version 1803. What you may want to do therefore is to change the startup type of the service to automatic.
Here is what you need to do to correct the issue (or at least try it to see if it resolves the network discovery issue on your network):
- Tap on the Windows-key to open the Start Menu, or click on the Start Menu icon.
- Type services.msc and double-click on the result. This opens the Services Manager on the computer.
- Locate the service Function Discovery Resource Publication. Its status should be blank which means that is not running.
- Double-click on the service to open its properties.
- Click in the "Startup type" menu and switch startup to automatic.
- Restart the PC after you have clicked on the ok button to apply the changes.
Update: Microsoft acknowledged the issue recently. The company's workaround for the issue suggests to make sure that the following services are set to Automatic (Delayed Start):
- Computer Browser (Browser)
- Function Discovery Provider Host (FDPHost)
- Function Discovery Resource Publication (FDResPub)
- Network Connections (NetMan)
- UPnP Device Host (UPnPHost)
- Peer Name Resolution Protocol (PNRPSvc)
- Peer Networking Grouping (P2PSvc)
- Peer Networking Identity Manager (P2PIMSvc)
If you upgrade a PC from an earlier version of Windows, e.g. Windows 7 or Windows 10 version 1703, you may run into network related discovery issues caused by the disabling of SMB 1.0. Microsoft disabled the application-layer network protocol Server Message Block 1.0 in the Fall Creators Update.