![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 73%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZH%3C/text%3E%3C/svg%3E)
Windows location on a device is determined by Microsoft’s location service using a combination of GPS (if available), nearby Wi‑Fi access points and routers, cell towers, IP address, or a manually set default location. When location services are turned on, the device periodically sends de‑identified information about nearby wireless access points, routers, cellular towers, and IP address to Microsoft to improve the location service and its underlying databases.
Key points relevant to this scenario:
- If location services are turned off, Windows and apps will not have access to device location, and some apps may not be able to access Wi‑Fi network information.
- With location services turned on, apps can use coarse or precise location. Coarse location is approximate and obfuscated; precise location is the most accurate that can be determined.
- The location service may use Wi‑Fi and other signals that are mapped in Microsoft’s and its partners’ databases (currently HERE and Skyhook) to a specific place.
- De‑identified location and radio data from devices is used to improve these databases over time.
- Some third‑party apps and services can still infer location using other technologies (Bluetooth, IP address, cellular modem, etc.), even if Windows Location services are off.
From the available information, the following can be concluded and done within documented behavior:
- Forcing a refresh/rebuild of device geolocation mapping
There is no documented user‑exposed control to directly force Microsoft’s cloud geolocation database (Wi‑Fi positioning, cell tower mapping, etc.) to rebuild or immediately recalculate the mapping for a specific device or network. The service updates over time based on de‑identified data sent from devices when location services are enabled.
Locally, the main controls are:
- Turn Location services off and on again.
- Clear location history.
- Control which apps can access coarse vs precise location.
These affect how the device and apps use location, but do not provide a direct mechanism to reset or override the underlying network‑to‑location mapping.
- Manually reporting or correcting an incorrect entry in Microsoft’s location database
The documentation describes that de‑identified location data may be shared with location service provider partners (currently HERE and Skyhook) to improve their services, but it does not document a user workflow to manually submit or correct a specific Wi‑Fi or network geolocation entry in Microsoft’s own database.
Because the service relies on aggregated, de‑identified data, corrections typically come from ongoing use and data collection rather than per‑user manual edits.
- Relationship to Wi‑Fi positioning or stale mapping
The Windows location service can use:
- GPS
- Nearby wireless access points and routers
- Cell towers
- IP address
- Default (manually set) location
If a particular Wi‑Fi environment (SSID/BSSID set) has historically been observed at a specific place, the location service can associate that radio environment with that place. The documentation confirms that devices send location plus nearby Wi‑Fi/router/cell tower info (after removing identifying data) to Microsoft, and that this information is used to improve the service and may be shared with HERE and Skyhook.
This means a persistent, repeatable incorrect location can be consistent with a stale or incorrect mapping of the local Wi‑Fi environment in the underlying database. However, the documentation does not provide a supported way to directly inspect or edit that mapping from the client side.
- Clearing cached geolocation data or “device fingerprints”
On the device, the supported privacy controls are:
- Turn Location services off entirely. When off, Windows and apps will not have access to device location, and some apps may not be able to access Wi‑Fi network information.
- Turn off Let apps access your location so no apps receive location information, even if location services are on.
- Choose which apps can access precise location; others will only receive coarse location.
- Clear location history.
These steps clear or restrict local usage of location data, but they do not remove or reset the de‑identified radio/location observations already contributed to Microsoft’s service.
- Escalation or correction process
The provided documentation and Q&A content do not describe a specific escalation or correction workflow for individual incorrect geolocation mappings in Microsoft’s location database. They only describe:
- How the location service works and what signals it uses.
- That de‑identified data is used to improve Microsoft’s and partners’ services.
- That some apps (especially desktop apps) may not support per‑app precise location control.
- That third‑party apps might still infer location using other technologies and should respect Windows location settings when built with Microsoft tools.
If location is critical and the mapping appears wrong, the only documented levers are:
- Disable Windows location services or app access so affected apps cannot use the incorrect Windows‑provided location, forcing them to fall back to other methods (for example, IP‑based geolocation if the app supports it).
- Use only trusted apps and review their privacy policies, as some may use their own geolocation methods independent of Windows.
Within the scope of the available documentation, there is no published client‑side method to:
- Force an immediate rebuild of the network‑to‑location mapping.
- Manually correct a specific Wi‑Fi or network location entry.
- Fully clear any cloud‑side geolocation data associated with a particular network or device.
References: