Nearby Sharing Not Working in Windows 11? Isolate Discovery and Transfer

When Nearby Sharing fails, first identify the failure stage. A receiving computer that never appears is a different problem from a visible computer that rejects a file or transfers it slowly. Work through one stage at a time instead of changing every network setting at once.

Start with two awake Windows 11 PCs, Bluetooth and Wi-Fi enabled, and one small non-sensitive file. Confirm that both computers have Nearby Sharing enabled. This guide concerns Microsoft’s PC feature, rather than assuming that similarly named phone-sharing tools are interchangeable.

1. Make a repeatable starting test

Place the computers close together and keep them awake. Use a tiny text file with an obvious name, such as sharing-test.txt, rather than a large folder or private document. Write down which PC sends and which receives. Reverse those roles later to see whether the fault follows one device.

Microsoft’s Nearby Sharing troubleshooting instructions cover supported Bluetooth hardware, sharing settings and connection checks. Menu wording can vary with the Windows build and organization policy.

2. Check discovery before blaming speed

1. Open Settings → System → Nearby sharing on both PCs.
2. Confirm the selected visibility matches your test. For two personal PCs using different accounts, a tightly restricted “My devices only” choice can explain why the other computer is absent.
3. If appropriate in your own trusted environment, use “Everyone nearby” briefly to test discovery. Return to the preferred restricted setting afterward.
4. Open the file’s Share menu and look for the receiving PC.

If the device is still missing, check Bluetooth availability and supported hardware using Microsoft’s linked guidance. Do not install a random driver utility from an advertisement. Use Windows Update or the PC manufacturer’s support page for the exact model.

3. If the PC appears but the transfer stalls

Watch the receiving screen for a request. Check that there is enough space in the configured destination and that you know where successful transfers are saved. An unnoticed acceptance prompt or an unexpected folder can look like a network failure.

4. Check the network without changing its trust blindly

Microsoft’s guidance includes checking the network profile and using a private network for the feature. Apply that setting only to a network you actually trust, such as your own home network. Do not label an airport or café connection private just to make discovery easier.

A managed work computer may restrict sharing intentionally. If a policy controls the setting, ask the administrator for the approved transfer route. Avoid disabling a firewall or endpoint protection as a routine troubleshooting step.

5. Verify the result before sending real documents

After the small file succeeds, open it on the recipient. Send a representative larger file and compare the result. Record the location, direction and time if failures are intermittent. That record is more useful for support than “sharing sometimes breaks.”

For sensitive information, confirm the intended recipient and consider an approved access-controlled sharing method. Our online privacy guide covers that decision. If Wi-Fi itself is unstable, use the room-by-room Wi-Fi checklist before repeating a large transfer.