The strangest Quick Share failures are the ones where nothing is broken: it worked at setup, and weeks later it quietly does not. Several parts of the system are designed to switch themselves off — this page lists them, so "it stopped working" becomes a two-minute check instead of a reinstall.
Quick Share's safety design is also its forgetfulness. Visibility expires, the Windows app only exists while it runs, notifications get muted by Windows features, and phones apply battery rules you never set. None of these are faults. All of them look exactly like faults at 9 pm when you just want one photo moved.
If you tested with Everyone mode during setup and it "stopped working" days later, nothing failed: the mode auto-reverts after 10 minutes by design. Your resting state should be Your devices on the phone, which never expires for your own signed-in devices. Set that once and the timer stops being your problem. The visibility page in this series explains all three modes properly.
Quick Share on Windows can only be found, and can only receive, while the app is running. Close it on Friday and the PC is invisible on Monday. In the app settings, turn on the option to run Quick Share when Windows starts. And after a Windows reinstall, remember the app itself is gone — reinstall it from Google's official Android site before troubleshooting anything else.
Windows updates and quiet-hours features can change how notifications behave, and a swallowed acceptance popup looks exactly like a failed transfer. Check Settings → System → Notifications: notifications from apps on, and Quick Share allowed in the sender list, with Focus Assist off while you test. Google calls this out in its own Windows help page because it happens so often.
A new router, a renamed SSID, or the PC deciding your home network is Public after an update — each quietly breaks the "same network" condition Quick Share depends on. Set the home network profile back to Private, confirm the phone is on the home SSID and not the guest one, and discovery returns. After any router change, treat Quick Share as needing a fresh first test, like everything else on the network.
Once a month, send one photo phone-to-PC and one file PC-to-phone. It takes two minutes, it proves every link in the chain while nothing urgent is waiting, and it turns the next real failure into a short story: "it worked on the first, so what changed since?" Configuration drift is found by drills, not by emergencies.
Revisit the original setup in the video with this checklist beside you — every readiness item maps to a step you see on screen.
▶️ Watch Full VideoTwo usual reasons: the Windows app was open after the restart but later closed, and it only receives while running — enable its run-at-startup option. Or the phone was in Everyone mode, which expires after 10 minutes by design; Your devices is the mode that stays.
Yes — that is what the mode is for. Only devices signed in with your own Google account can see and reach the phone, transfers between them are meant to be frictionless, and nothing is exposed to strangers nearby.
Mostly, yes. Phone and Windows updates can reset permissions, notification behaviour and network profiles, and Quick Share depends on all three. The monthly two-minute drill on this page exists precisely because drift is normal — catch it on a calm day, not during an urgent transfer.