Windows 11 Nearby Sharing not working can mean that the receiving PC never appears, the other device does not show an acceptance prompt, or a file transfer freezes after it begins. Those symptoms have different causes. Nearby Sharing uses a supported Windows PC-to-PC experience with Bluetooth discovery and, where supported, Wi-Fi transfer. This guide explains the official requirements and shows how to isolate the problem without deleting files, disabling protection or confusing the feature with Android Quick Share.
Quick Answer: On both Windows PCs, open Settings > System > Nearby sharing and enable it with a visibility option suited to the devices. Ensure Bluetooth is enabled, the hardware meets the requirements, and both PCs are nearby and awake. For supported faster transfers, connect them to the same trusted private Wi-Fi network. Send a small test file, and check the receiver’s Notification Center if no acceptance banner appears. Do not disable the firewall or reset network settings as a first-line fix.
Know Which Nearby Sharing Feature You Are Using
Windows Nearby Sharing is designed for sharing files, links and certain other content with compatible nearby Windows PCs. It is not the same service as Google’s Quick Share for Android devices, even though the names and wireless concepts are similar. Start by identifying the sending and receiving devices. If one is an Android phone, follow the relevant Quick Share for Android troubleshooting guide instead of assuming Windows Nearby Sharing will display the phone. Microsoft’s Nearby Sharing instructions describe the PC-to-PC workflow. Correctly identifying the feature avoids spending time on settings that the chosen application does not use.
Understand Discovery Versus Actual File Transfer
The first stage is discovery: the sender needs to find an available nearby receiver. The next stage is acceptance, when the other computer receives a request or notification. Finally, the file or link is transferred through an available supported connection. A device missing from the share menu is a different problem from a transfer that starts but stalls. Record exactly where the process stops and which error, if any, is shown. Avoid resetting network adapters or signing out of Microsoft accounts before the basic discovery conditions are checked. This separation makes troubleshooting faster and helps preserve unrelated network settings.
Check The Requirements On Both Windows PCs
Microsoft’s Nearby Sharing troubleshooting guide lists compatible Windows versions and Bluetooth capabilities among the requirements. Both computers must have functioning supported Bluetooth hardware, and some transfer paths can use Wi-Fi for better performance. Verify the operating system version and check the actual adapter capabilities instead of assuming that every desktop PC with a USB dongle qualifies. Some business devices may also have organizational restrictions. If a computer has no Bluetooth adapter or its wireless hardware is disabled in firmware, changing the Share menu cannot create that capability. Determine compatibility before making repeated pairing attempts.
Turn On Nearby Sharing On Both Devices
On each Windows 11 computer, open Settings, System, Nearby sharing and enable the feature. Review the available visibility choices, commonly My devices only and Everyone nearby. The wording and layout can vary between Windows builds. Microsoft documents this under its sharing instructions. Enabling the feature on the sender alone is insufficient because the receiving PC must be able to advertise its availability. After both computers are configured, keep them awake and close enough for Bluetooth discovery. Perform one simple test with a non-sensitive file, then observe whether the receiving device is listed. Do not copy confidential documents during initial troubleshooting.
Choose My Devices Only Or Everyone Nearby Deliberately
My devices only can be useful when both PCs are connected to the same Microsoft account as supported by Windows. Everyone nearby permits broader discovery by compatible nearby Windows devices. Microsoft’s troubleshooting documentation notes that account identity matters for the more restrictive option. If a second PC is not visible, temporarily compare the supported visibility setting only in a private, trusted environment. Do not leave permissive discovery enabled in public places simply to avoid troubleshooting. Keep the receiving device within sight and verify its identity before accepting anything. After the test, restore your preferred privacy choice. The visibility setting should reflect who you actually intend to share with.
Confirm Bluetooth Is Enabled On Each Computer
Open Settings, Bluetooth and devices, and confirm Bluetooth is turned on at both ends. If a toggle is missing, the adapter may be absent, disabled or failing. Microsoft’s missing Bluetooth guidance explains the broader issue. If other Bluetooth devices also fail, troubleshoot the radio before treating Nearby Sharing as a unique problem. Our Windows Bluetooth won’t turn on guide addresses that condition. If Bluetooth works normally, do not delete every paired accessory as a precaution. Nearby discovery requirements deserve their own test; unrelated headphones and keyboards should remain untouched.
Check Bluetooth Low Energy Support
Microsoft says Nearby Sharing requires supported Bluetooth Low Energy capability, and its official troubleshooting page provides a Device Manager property check for the adapter. Expand Bluetooth, open the radio’s properties and inspect the relevant Bluetooth Low Energy support property when available. The exact property name and interface may vary by adapter or Windows version. If the system does not expose the expected capability, look up the device manufacturer’s official specification rather than installing a random driver. Ordinary Bluetooth audio compatibility does not by itself prove every Nearby Sharing requirement. If the adapter lacks needed support, a setting change cannot overcome the hardware limitation.
Keep The PCs Close Together For Initial Discovery
Place the computers in the same room or a short distance apart to reduce radio uncertainty while testing. Microsoft’s guidance uses roughly 30 feet or 10 meters as a practical discovery range, but walls and interference can alter actual results. Avoid putting the receiving laptop to sleep during the test. If devices appear when side by side but disappear at the normal desk locations, investigate signal, obstacles and the wireless environment. Do not infer that a particular wall is the sole culprit from one observation. A close-range success is evidence that the basic feature can work; it narrows the problem to location-dependent conditions.
Check Wi-Fi For Faster Transfers
Nearby Sharing can use Bluetooth for discovery and may use Wi-Fi for the actual file transfer when the supported conditions are met. On modern Windows 11, a compatible private Wi-Fi network can enable faster transfer behavior. Microsoft’s Nearby Sharing support page explains the current supported sharing setup. Turn on Wi-Fi on both computers and connect to the same trusted network for the comparison. Do not assume that Bluetooth being available guarantees high throughput. If transfer is successful but slow, verify Wi-Fi and signal quality before changing file sharing policies or disabling security tools.
Confirm The Network Is Appropriate And Trusted
For supported Wi-Fi-based Nearby Sharing behavior, Microsoft’s documentation references a private network profile. Windows labels networks Public or Private to control certain discovery and sharing behaviors. Change a network to Private only if it is genuinely trustworthy, such as your secured home network. Do not mark a café hotspot or unknown shared network as Private solely to make an experiment work. If you use an organization-managed PC, ask IT before changing network classification. Check the selected Wi-Fi name and whether both computers are connected to the same intended network. A safe test uses a trusted home network and a harmless file before broader settings are touched.
Open The Windows Share Menu Correctly
In File Explorer, select a small ordinary document or image, open its sharing command and choose Nearby sharing when offered. Windows may display a Share menu with several destinations; the exact UI depends on the build. Microsoft describes the sender and receiver flow in its official sharing guide. If the Nearby Sharing choice is missing or grayed out, first verify settings and compatible Bluetooth hardware rather than repeatedly clicking the same file. A test file should be small, not locked by another application and not restricted by workplace policy. Do not use sensitive data to determine whether an unknown nearby device is actually your second PC.
Verify The Receiver Is Visible In The Share Panel
With both PCs awake and Nearby Sharing enabled, the sender should search for eligible receiving devices. If the receiver does not appear, check that it is not set to a visibility mode that excludes the sender. Also verify Bluetooth status and proximity. Do not assume that sharing visibility is the same as standard Bluetooth pairing or network discovery in File Explorer. Microsoft distinguishes these settings in its Nearby Sharing help pages. If several devices are listed, identify the correct PC name before sending. When testing in a shared office, use a distinctive approved device name rather than sending confidential information to the first item that appears.
Accept The Transfer On The Receiving Computer
Depending on the destination and supported Windows configuration, the receiver may receive a notification offering Save, Save and open or another relevant action. Keep the receiving computer unlocked and visible during the test. If the sender remains stuck on Waiting to receive, inspect Windows notifications on the receiver instead of restarting the sender immediately. Microsoft’s troubleshooting guidance notes that notices may appear in Notification Center even when no pop-up banner is visible. If an acceptance prompt appears, confirm that the sending device and file are expected. Do not approve unsolicited transfers in public environments. A missing prompt and a failed data transfer require different next steps.
Check Windows Notifications And Do Not Disturb
Windows notification settings can prevent a transfer request from showing prominently on the screen. Open Settings, System, Notifications and review how sharing-related alerts are delivered. Check Do Not Disturb and other focus settings, then inspect Notification Center for a request. Microsoft’s Nearby Sharing troubleshooting page specifically notes that a notification can be available without a visible pop-up. Do not disable all Windows notifications indefinitely; make the smallest change necessary to test whether the receiver can see the prompt. If the transfer works when you manually open Notification Center, you have isolated a delivery or presentation issue rather than a discovery failure.
Distinguish Waiting To Receive From Transfer In Progress
Waiting to receive often means the sender has not completed the receiver acknowledgment step. A progress bar that has started moving indicates a later stage and suggests the devices have at least begun to exchange data. For the first condition, check visibility, awake status, notification access and acceptance. For a transfer that starts but stalls, focus on Wi-Fi, radio strength, available storage and power interruptions. Avoid a full network reset while a transfer is active because it can disrupt other work. Cancel the specific unsuccessful attempt normally and use a smaller test file to establish whether the problem is related to file size or sustained connection quality.
Understand Why A Transfer Can Be Very Slow
When a file transfer proceeds over a slower wireless path, throughput may be far below what the home internet plan advertises. Nearby Sharing is a local exchange; the rate can depend on Bluetooth and Wi-Fi capability rather than the speed-test number from an internet provider. Compare a tiny test file with a larger non-sensitive file. If the small transfer succeeds but the larger one is slow, inspect supported Wi-Fi conditions and power settings. Our Wi-Fi bottleneck guide explains why wireless performance may differ from a wired benchmark. A faster broadband subscription cannot repair an unreliable local radio link.
Check Whether Wi-Fi Itself Is Missing Or Unstable
If one Windows computer has lost Wi-Fi entirely, Nearby Sharing may fall back to a slower supported path or fail in a setup that expects Wi-Fi. Verify that the intended network appears and normal connectivity works. Microsoft’s Wi-Fi troubleshooting guidance provides supported diagnostic checks. Our missing Wi-Fi network guide addresses discovery and adapter issues separately. Do not randomly reset the entire router or alter its security settings just because two laptops cannot find each other. Test the basic Wi-Fi connection first, then return to the Nearby Sharing feature.
Consider VPN And Corporate Network Restrictions
VPNs, managed firewalls and device policies can affect local network behavior or restrict sharing in an organization. If Nearby Sharing works on a trusted home network but not under a managed connection, ask the network administrator before changing any protections. A work device may intentionally block sharing to personal computers for data-loss prevention. Do not attempt to bypass an enterprise policy or disable endpoint security to force file transfer. A controlled comparison under approved conditions is more informative than changing a dozen unrelated settings. Record whether both devices are personally owned or managed, because the supported next action differs. Respect data policies even when the technical feature is available.
Restart Bluetooth Before Resetting The Network
If discovery has worked previously but now fails intermittently, turn Bluetooth off and on through the supported Settings control on both computers, then retry with the devices close together. Microsoft’s Nearby Sharing guidance lists this as a troubleshooting step. This is narrower than deleting adapters, running network reset or modifying the registry. If other Bluetooth devices are in use, warn their users because toggling the radio will interrupt those sessions. After turning Bluetooth back on, check that both computers are discoverable and try again. If the toggle is missing or will not respond, use Microsoft’s Bluetooth troubleshooting rather than repeatedly forcing the switch.
Restart Both PCs In An Orderly Way
When focused settings checks do not work, save open documents and restart the sending and receiving PCs normally. Wait for both desktops to load and their wireless adapters to connect, then repeat the sharing test with a small file. A normal restart can clear transient services and connection state without removing personal files. Keep the devices plugged into power if their batteries are low. If the problem returns after sleep or overnight, note that repeatable pattern. Do not conclude that the hardware is defective based on a single failed transfer. A documented recurrence helps identify whether updates, power management or signal changes trigger the issue.
Update Bluetooth And Wi-Fi Drivers From Trusted Sources
Drivers can affect discovery and transfer stability, but a driver change should follow symptom-specific checks. Use Windows Update and the computer or adapter manufacturer’s official driver channel. Microsoft’s Bluetooth driver update guidance explains supported options. Do not install generic driver packs, disable driver signature protections or force an unrelated driver version. Before updating, note the existing driver and create a normal recovery point if appropriate. If a recent driver update preceded the failure, consult official rollback instructions for your hardware. Test Nearby Sharing after each approved update rather than changing Bluetooth and Wi-Fi drivers simultaneously.
Check For Hardware With Limited Bluetooth Capabilities
Some desktop computers use inexpensive USB Bluetooth adapters that support basic audio or keyboards but have different feature support or driver quality. Check the official adapter specification and the relevant Bluetooth Low Energy capability described by Microsoft. If the adapter is disconnected, reseat it only when safe and use a different supported USB port for a test. A failed adapter may affect all Bluetooth devices, not only Nearby Sharing. Avoid treating an old wireless dongle as if it supports every contemporary Windows feature. If hardware replacement is necessary, verify documented compatibility first. Buying a faster internet router will not give a Bluetooth-only desktop the missing required radio hardware.
Check Available Storage And Destination Permissions
If device discovery and acceptance succeed but saving the transfer fails, inspect the receiving computer’s available disk space and the default save location. A nearly full drive or a location restricted by organization policy may prevent successful completion. Test a small file to a normal user-accessible folder rather than editing protected system directories. If the transfer reaches the receiver but the file seems missing, search the expected destination and inspect Windows notifications for the save message. Do not disable ransomware protection or other security controls simply to write into a restricted folder. Use an appropriate permitted folder and document the result.
Differentiate Nearby Sharing From Network Folder Sharing
Windows Nearby Sharing sends selected items directly between nearby devices through its supported user interface. It is not the same as configuring a shared network folder, SMB permissions or file discovery in File Explorer. Microsoft’s network file sharing guide describes a different workflow. A PC that does not appear under Network in File Explorer may still be usable with Nearby Sharing if the separate requirements are met. Do not enable passwordless file sharing or broadly open shared folders as an attempted fix for a Nearby Sharing visibility issue. Keep network permissions narrow and separate from wireless transfer diagnostics.
Do Not Disable The Firewall As A First-Line Fix
Some troubleshooting pages mention firewall checks, but disabling a firewall or security product can expose a computer and is not necessary for ordinary first-line Nearby Sharing tests. Prefer checking documented settings, radio availability, private trusted networks and correct notification delivery. On managed devices, firewall policy may be intentional and should be reviewed by authorized IT. Avoid making broad inbound exceptions or turning off antivirus protection based on one failed share. If an approved specialist identifies a specific blocked component, follow their narrowly scoped instructions with a rollback plan. Security controls are part of the system’s protection, not an obstacle to remove casually.
Use A Symptom-Based Troubleshooting Matrix
A device missing from the Nearby list calls for visibility and Bluetooth discovery checks. A waiting transfer suggests attention to the receiver notification and acceptance step. A transfer that starts but slows may benefit from a Wi-Fi comparison. A transfer that reaches the destination but cannot save should prompt a storage or permission check. The table below organizes these branches so you can make one reversible change at a time. No entry guarantees a particular root cause, because hardware and policy conditions vary. Record results of a small harmless transfer before changing multiple settings. The simplest successful test provides the clearest starting point.
Build A Five-Step Nearby Sharing Workflow
Use this sequence for a controlled test. First, enable Nearby Sharing on both PCs with an appropriate privacy setting. Second, check Bluetooth capability and turn on Wi-Fi where supported. Third, keep both computers close, awake and on a trusted network. Fourth, send a small non-sensitive file using Windows Share and accept it from the correct sender. Fifth, inspect Notification Center, transfer progress and the saved file before troubleshooting further. An original diagram below summarizes the path. This workflow distinguishes setup from delivery and avoids immediately deleting adapters or profiles. If the test succeeds, repeat with a normal-sized file and your preferred privacy settings.
| Symptom | First Area To Inspect | Reversible Test |
|---|---|---|
| Receiver Missing | Visibility And Bluetooth | Enable On Both And Move Closer |
| Waiting To Receive | Notification And Acceptance | Check Receiver Notification Center |
| Transfer Too Slow | Wi-Fi Path | Use Trusted Private Wi-Fi Where Supported |
| Save Failed | Storage And Permissions | Use A Small File In A Permitted Folder |
| Bluetooth Toggle Missing | Radio Or Driver | Follow Official Hardware Troubleshooting |
Handle Different Microsoft Accounts Carefully
If the computers use different Microsoft accounts, My devices only may not discover the other PC as intended. Microsoft’s Nearby Sharing troubleshooting guidance calls attention to using the same account when this mode is selected. In an appropriate trusted environment, you can consider Everyone nearby for a controlled exchange while verifying the receiver’s identity. Do not sign out of important Windows accounts or move personal files between profiles merely to solve a sharing problem. After the transfer, restore the stricter visibility option if that matches your privacy needs. A device identity or account restriction is not necessarily a Bluetooth hardware failure, so keep these layers separate.
Enable On Both PCs → Check Bluetooth And Wi-Fi → Choose Visibility → Send And Accept → Verify Saved File
Original Step Diagram: Start With A Non-Sensitive Test File
Test With Another Known-Working Windows PC
If an eligible second computer is available, compare one sender against two receivers or the problematic receiver against another sender. A device that fails to appear for all senders deserves inspection of its own visibility, Bluetooth hardware and system settings. If only one pair fails, the particular account, network or driver combination may matter. Make sure every comparison is authorized and uses harmless test files. Do not share sensitive data with a third-party device. An isolation test is not a laboratory certification, but it can narrow the next support step dramatically. Avoid changing the same settings on every device before you know which end is implicated.
Recognize When Repair Or Support Is Appropriate
When Nearby Sharing remains unavailable despite supported hardware, enabled settings, healthy Bluetooth and Wi-Fi, and controlled testing, collect the Windows build, device models, wireless adapter details and exact failure stage. Explain whether another Bluetooth feature works and whether the receiver ever appears. Use Microsoft’s official support resources or the computer manufacturer’s support channel. If a managed policy appears to prevent sharing, involve the IT administrator. Avoid experimental registry changes, unofficial drivers or commands that disable security. Record which settings you changed so they can be restored. A clear reproducible case is more valuable to support than a long list of unverified repair attempts.
Keep Future Transfers Secure And Reliable
Once sharing works, choose the least permissive visibility setting that meets your needs, confirm the receiving device name and avoid accepting unexpected content. Keep operating-system and driver updates current through trusted channels. If you frequently move files between Windows and Android, remember to use the correct Android-compatible solution rather than confusing it with Windows Nearby Sharing. When a future transfer stalls, identify whether the failure is discovery, acceptance or data transfer before changing settings. A reliable small-file test can often reproduce a problem without risking a large confidential document. The objective is safe, predictable transfers rather than maximum exposure to nearby devices.
Frequently Asked Questions
Why Is The Other PC Not Showing In Nearby Sharing?
Verify that Nearby Sharing is enabled on both compatible Windows PCs, Bluetooth is available, both computers are awake and visibility allows the intended connection. My devices only may require the appropriate account identity.
Does Nearby Sharing Need Bluetooth Or Wi-Fi?
Microsoft lists Bluetooth Low Energy support among its requirements. Compatible configurations can also use Wi-Fi for faster transfers. Check both devices and the supported Windows documentation rather than assuming one radio alone handles every stage.
Is Windows Nearby Sharing The Same As Android Quick Share?
No, Windows Nearby Sharing and Google’s Quick Share for Android are distinct experiences. Use the correct application and troubleshooting workflow for the devices involved.
Why Is Nearby Sharing Stuck On Waiting To Receive?
Check whether the receiver shows the request in Notification Center, confirm both PCs remain discoverable and awake, and verify the appropriate visibility or account setting. Restart Bluetooth or the PCs only after these checks.
Can Do Not Disturb Hide The Transfer Prompt?
Yes, Windows notification settings may prevent a banner from appearing prominently while a notification remains available in Notification Center. Inspect the receiver’s notifications before assuming discovery failed.
Why Is A Nearby Sharing Transfer Slow?
The actual path may be limited by Bluetooth or local Wi-Fi conditions. Where supported, connect both PCs to the same trusted private Wi-Fi network and compare the transfer. Internet plan speed does not guarantee local wireless throughput.
Should I Turn Off The Firewall To Make Sharing Work?
No, not as a routine fix. Begin with official feature settings, hardware compatibility, visibility and notification checks. Managed firewall restrictions should be reviewed by authorized IT personnel.
Does My Devices Only Work Across Different Microsoft Accounts?
Microsoft’s guidance indicates that the correct same-account relationship matters in the My devices only mode. For other devices in a trusted environment, review the supported Everyone nearby setting and verify the receiver identity.
Will Resetting My Network Remove The Problem?
Not necessarily, and a network reset can disrupt saved connections and other configurations. Use narrower supported checks first, then consider broader repairs only when there is evidence of an actual adapter or system-level issue.
How Do I Check Whether A Transfer Really Worked?
Send a small harmless file, accept it on the intended receiving PC, confirm the completion message and open the file from the saved location. That verifies more than merely seeing the receiver listed in the Share menu.
Editorial Verification: Instructions are grounded in Microsoft support documentation. Windows build, adapter and network-policy differences may alter available settings. The article does not claim hands-on testing across all hardware.



