Location is on. Maps works. But one app insists it cannot see your location — or keeps showing somewhere you have never been. That is almost never the master switch; it is that app's own permission, or the browser standing in between. This guide peels the layers in order.
Windows location is a chain of three permissions, and the chain breaks at its weakest link. If the main switches are healthy, walk this page top to bottom: the per-app switch, the separate switch classic programs use, the browser's own permission, and the registry store underneath it all. The greyed out master-switch repair — a different problem — is shown in the video above.
Let apps access your location [ On ]
Maps [ On ] Weather [ On ] Your app [ Off ]
The master switches are healthy — the problem is one line further down. Each app has its own location permission.
Windows location has three layers, and an app needs all three:
If the first two are on but your app still says "location is off" or shows a generic position, layer three is where to look. This guide assumes the master switches already work — if they are greyed out instead, that is the main repair, linked at the end.
For desktop (non-Store) programs there is one extra line on the same page: Allow desktop apps to access your location. Browsers and classic .exe programs use that switch, not the per-app list, because Windows cannot reliably tie a location request to one classic program.
Websites do not get your location from Windows directly — they ask the browser, and the browser asks Windows. So a site can be blocked in two places:
If Maps in the browser shows the wrong place while the Maps app is right, the browser's own permission or its cached position is the cause — clear that site's permission and let it ask again.
Rare, but real: the Settings page shows Allow while the underlying permission store disagrees — usually after privacy tools have edited permissions directly. The store lives here:
regedit and go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\locationValue entry should read Allow. If it says Deny, double-click and change it to Allow.Treat this as the last step, not the first — the Settings page fixes 95% of per-app cases without the registry.
The master switch repair plus the permission layers — the whole location system fixed in one walkthrough.
▶️ Watch Full VideoOnly Store-style (packaged) apps appear individually. Classic desktop programs share one switch — Allow desktop apps to access your location — because Windows cannot attribute a location request to a specific classic program. If that switch is on and the program still fails, the block is inside the program or its own settings.
Because the website asks your browser, not Windows. The browser needs the desktop apps location switch on in Windows, and the site needs its own Allow permission in the browser's site settings. Either one set to Block produces exactly this message.
It stops it getting location through Windows, which is the honest scope of the switch. An app can still guess a rough position from your internet connection (IP address) — that is true of any device, and a VPN changes what that guess says.