All Computers Not Showing in Windows 10

If all computers are missing in Windows 10 File Explorer, start with discovery, then name resolution, then share access. If Network Discovery and File and printer sharing are already on, the usual culprits are a blocked firewall rule, a stopped service, or a path that opens by IP but fails by name. Begin with the network profile, because a Public profile can sometimes hide machines before other steps matter.

What the missing computers symptom means

Missing PCs in File Explorer can point to a few different causes. The network can fail to discover devices at all, it can discover them but fail to resolve their names, or it can find the host and still deny access to the share. Those are separate layers, and each one needs a different fix.

For example, if a laptop opens a share by IP address but not by host name, that points to name resolution, not discovery. If a PC appears in Network and then asks for credentials or denies access, that points to share permissions or password-protected sharing, not a discovery problem.

Troubleshooting matrix

Is the network set to Private?

A Public profile can block discovery even when the PC is online. Private is commonly the right choice for finding nearby computers in File Explorer, and Network Discovery should be enabled for that active profile. If the PC is on Public, switch it first.

1. Open Settings > Network & Internet > Status.
2. Select Change connection properties.
3. Set Network profile to Private.
4. Open Control Panel > Network and Sharing Center > Change advanced sharing settings.
5. Under Private, turn on Network discovery and File and printer sharing.
6. Return to File Explorer and refresh Network.

Also review Password protected sharing. Leave it on if you want sign-in required access. Turn it off only if you want open access for that network. Public folder sharing is optional and should stay untouched unless you actually use shared Public folders.

Why is my Windows 10 network discovery not working?

When discovery fails, check the sharing settings, the discovery services, and the firewall in that order. Network Discovery controls whether computers appear in File Explorer, and it may need a firewall rule before the browse list updates.

1. Go to Control Panel > Network and Sharing Center > Change advanced sharing settings.
2. Under the active profile, turn on Network discovery and File and printer sharing.
3. Open Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall.
4. Allow the Network Discovery rule group on the current network type.
5. Open Services, then restart Function Discovery Resource Publication and Function Discovery Provider Host.
6. If discovery still fails, set FDResPub to Automatic and check that fdPHost is not disabled.

Trigger settings can matter for FDResPub. If the service starts only on demand, browse results can lag or vanish after a reboot. Reopen File Explorer after the restart and check again.

Why does net view show System error 6118?

net view lists computers that Windows can discover on the network. If it returns System error 6118, the browse list is not being built correctly, usually because discovery is blocked or the discovery services are not publishing the machine.

1. Open Command Prompt and check whether the browse list appears.
2. Open Services and restart Function Discovery Resource Publication.
3. Set Function Discovery Resource Publication to Automatic if it is disabled or manual.
4. Check Function Discovery Provider Host and set it to Automatic if needed.
5. Review Windows Defender Firewall and allow the Network Discovery rule group.
6. Try a known host by name to confirm whether the target answers by name.

If the same command fails on one PC but not another, repeat the checks on both the client and the target. Discovery must work in both directions for the browse list to be reliable.

Why can I access a PC by IP but not see it in Network?

That is usually a name-resolution problem, not a discovery failure. If a share opens by IP address but not by host name, the host is reachable. Windows is failing to map the name to the address, or the network browse list is stale.

1. In File Explorer, enter the share by IP address.
2. If that works, try the same share by host name next.
3. Check whether the name matches the device exactly, including the local hostname.
4. Open Control Panel > Network and Sharing Center > Change advanced sharing settings and confirm discovery is on in the current profile.
5. Restart FDResPub and fdPHost.

If the IP path works but the name path fails after the restart, focus on naming and discovery publication instead of changing share permissions. Those permissions are not the bottleneck until the host appears and then rejects access.

What if discovery works but access is denied?

If the PC appears in Network and then asks for credentials or refuses the share, move to permissions. The machine is discoverable, so the issue is no longer network visibility. Check Password protected sharing, share permissions, and the NTFS permissions on the folder.

1. Open the target PC and go to Control Panel > Network and Sharing Center > Change advanced sharing settings.
2. Review Password protected sharing and keep it on if users must sign in.
3. Right-click the shared folder, open Properties > Sharing > Advanced Sharing, and confirm the share exists.
4. Open the folder’s Security tab and verify NTFS permissions.
5. Try the hostname path again after confirming the share exists.

Only use SMB 1.0/CIFS File Sharing Support if a legacy device requires it. It is a fallback for old hardware and old NAS boxes, and it carries a security tradeoff. Do not turn it on just to make modern PCs show up.

Should I turn on SMB 1.0 to see network computers?

Usually no. SMB 1.0/CIFS File Sharing Support is a compatibility fallback for older devices that cannot speak newer SMB versions. It should not be the first fix for Windows 10 browsing problems, and it is not the right answer when modern PCs fail to appear by name.

1. Try the share by IP address first.
2. If only an old printer, NAS, or Windows 7-era device is missing, test whether it needs SMB 1.0/CIFS.
3. Open Windows Features and enable SMB 1.0/CIFS File Sharing Support only if that legacy device requires it.
4. Restart the PC after changing the feature.
5. Remove SMB 1.0 again if it did not fix the legacy device.

For modern Windows 10 systems, the better path is still Private profile, discovery services, and firewall rules.

Why are network computers not showing in Windows 10?

Start at the top of the stack. Set the network to Private, turn on Network discovery and File and printer sharing, then make sure FDResPub and fdPHost are running. If a machine opens by IP, skip discovery changes and focus on name resolution or access rules instead.

Keep the same Workgroup name across devices when you are troubleshooting mixed home or small-office networks. A mismatched workgroup can hide PCs from casual browsing. It is not always required for every network, but it is worth checking when several PCs disappear together.

On Windows domains with more than 80 computers, Windows Explorer does not enumerate all computers in the domain. In that case, install update rollup 2975719 or install the hotfix that is described in this article on systems running Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows Server 2012 Datacenter, or Windows Server 2012. The affected computers in the domain are running Windows 8.1, Windows Server 2012 R2, Windows 8, or Windows Server 2012.

Still not working?

If discovery settings, services, and permissions all look correct, move to a later repair step. Network Reset is a valid last resort when discovery settings fail, because it clears and reapplies network components that can get stuck. Afterward, reapply Private, Network discovery, and File and printer sharing.

1. Go to Settings > Network & Internet > Status.
2. Select Network reset.
3. Restart the PC.
4. Return to Change advanced sharing settings and turn on the sharing options again.
5. Test the browse list and then try the host name again.

A common mistake is updating the router settings but leaving the Windows 10 network discovery option turned off on the other computers. If one computer still cannot see another, check both ends: the browsing PC and the share host. When both are clean and the problem persists, the next step is vendor support or a network administrator who can inspect policy, routing, or firewall management.

Frequently asked questions

How do I fix all computers not showing in Windows 10?

Put the network on Private, turn on Network discovery and File and printer sharing, then restart FDResPub and fdPHost. If the share opens by IP address but not by host name, treat it as name resolution and test the hostname path after the IP path.

How do I make other computers show up in File Explorer?

Open Control Panel > Network and Sharing Center > Change advanced sharing settings, then enable discovery under the active profile. After that, allow the Network Discovery firewall rules and refresh Network in File Explorer. If the network is Public, switch it to Private first.

How do I fix Function Discovery Resource Publication in Windows 10?

Open Services, restart Function Discovery Resource Publication, and set its startup type to Automatic. Then check Function Discovery Provider Host and do the same if needed. If browse results still lag, review the trigger settings and relaunch File Explorer.

How do I change my network profile to Private in Windows 10?

Go to Settings > Network & Internet > Status > Change connection properties and select Private. Then open Change advanced sharing settings and turn on discovery for that profile. Reopen File Explorer afterward so the browse list refreshes.