Shared computers do not appear under Network in File Explorer

Troubleshooting guideSources checked: 2026-09-05FaultNote editorial team

What to do first

Shared computers do not appear under Network in File Explorer. The network profile may be Public, network discovery may be disabled, or Function Discovery services may be stopped. Record the current state before changing it, use only the supported Windows path described below, and verify the same operation again after any required restart.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product: Windows network discovery
Versions and conditions: Windows 11 (confirm the edition and hardware requirements for the feature)
Error codes and identifiers: SMB

Symptoms

Shared computers do not appear under Network in File Explorer.
The same condition can persist after a retry or restart.

Causes and conditions

The network profile may be Public, network discovery may be disabled, or Function Discovery services may be stopped.

Before you start

Save open documents and allow time for a Windows restart if required.
Run administrative actions only on a personally managed PC or with administrator approval.
Save the diagnostic command output so the before and after states can be compared.

Precautions

Do not bulk-delete registry entries, system folders, credentials, or storage metadata.
Do not run unofficial scripts or unknown drivers with administrator rights.

Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

01
Separate discovery from share access
#
Enter a known UNC path in File Explorer. If the share opens, SMB access works and the steps below concern discovery in the Network list. If it does not open, check the path, network and credentials first.
02
Check the state with Get-NetConnectionProfile
#
Confirm that this is a trusted LAN and check whether the active network profile is Private rather than Public.
Command or path
```
Get-NetConnectionProfile
```
03
Repair through the supported path
#
Open Settings > Network & internet > Advanced network settings > Advanced sharing settings and enable Network discovery for Private networks. Check Function Discovery Provider Host and Function Discovery Resource Publication if discovery still fails.
Command or path
```
Get-Service FDResPub,FDPHost
```
04
Check discovery on a trusted LAN
#
If the connection is Public, confirm it is your trusted home or managed LAN before changing its profile to Private in Settings. Do not change public Wi-Fi to Private. After enabling discovery, reopen File Explorer and check the Network list and UNC access separately.
05
Verify under the same conditions
#
Replace SERVER_NAME with the actual value for your system before using this example.
Run Test-NetConnection <server> -Port 445 and repeat the original operation once under the same conditions. If it succeeds, verify again after a restart and record the setting that changed.
Check that no new critical event with the same timestamp and component appears in Event Viewer.
Command or path
```
Test-NetConnection SERVER_NAME -Port 445
```

Check the result

The feature starts, connects, or completes without the original error.
The verification command reports the expected enabled, healthy, or connected state.
The result remains correct after a Windows restart and no new matching critical event appears.

If the problem continues

If the same code persists, provide the full message, Windows build, command output, and occurrence time to the PC administrator or Microsoft Support.
If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.

Scope of this guide

Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.

Frequently asked questions

Should I enable discovery on a Public network?

No. It increases device exposure. Enable it only after confirming that a trusted LAN uses the Private profile.

UNC access works although the device is absent. Is SMB broken?

No. Discovery and SMB connectivity are separate; use the correct UNC path if the share itself works.

Official sources and dates

File sharing over a network in Windows ↗

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

← Search English guides