Windows determines location from several sources: GPS (if available), nearby Wi‑Fi and routers, cell towers, IP address, and the configured default location. If a device keeps showing an old or incorrect location even after basic steps, focus on these areas that are specifically supported in the context:
- Verify device and app location settings
- Go to Start > Settings > Privacy & security > Location.
- Ensure Location services is On.
- Under Allow apps to access your location / Let apps access your location, make sure it is On, and that the specific app being checked (for example, Maps or Teams) is allowed under Choose which apps can access your precise location.
- Check default location
- In Settings > Privacy & security > Location, under Default location, select Set default.
- In Windows 11, this opens the Maps experience. Select the correct point on the map or type the correct address, then select Save.
- If the device should not fall back to an old default, clear the address box and select Save so apps cannot use an outdated default location.
- Clear device and cloud location history
- On the device: go to Start > Settings > Privacy & security > Location and under Location history, select Clear. Then restart the device.
- In the cloud (if signed in with a Microsoft account and Location services is enabled):
- Go to account.microsoft.com while signed in.
- Select Clear location activity, then Clear.
- For other Microsoft apps that store location (for example, consumer Microsoft apps on mobile or web), location data can also be cleared from the Microsoft privacy dashboard by selecting My activity, filtering by Locations, and choosing Clear activity.
- Check for geofencing or app-specific behavior
- In Settings > Privacy & security > Location, if One or more of your apps are currently using geofencing is shown, an app may be reacting to entry/exit of a defined area rather than current precise position. Confirm that the app has precise location access and that geofencing rules are still valid for the current region.
- Cloud PC / Remote Desktop scenarios (Allow location override)
- If the device is a Cloud PC or is accessed via Remote Desktop/virtual desktop and shows the location of the remote host instead of the physical client, use Allow location override:
- On the local (client) device:
- Go to Start > Settings > Privacy & security > Location.
- Turn Location services On.
- Ensure the remote connection app (for example, Remote Desktop client) is allowed to use location.
- On the remote (host) device:
- Go to Start > Settings > Privacy & security > Location.
- Turn Location services On.
- Turn Allow location override On.
- On the local (client) device:
- This lets apps on the remote device use the location of the local device instead of the server’s location, which often appears as a persistent, incorrect city or region.
- If the device is a Cloud PC or is accessed via Remote Desktop/virtual desktop and shows the location of the remote host instead of the physical client, use Allow location override:
- Teams emergency location (if issue is in Teams)
- On Windows 11 Version 24H2 or higher, ensure:
- Location services is On.
- Let apps access your location is On.
- Microsoft Teams is enabled in the list of apps allowed to access location.
- In Teams, go to Calls and use Emergency location > Edit to add or correct the address that Teams uses for emergency calling. This is independent of the OS default location and can appear “stuck” if not updated.
- On Windows 11 Version 24H2 or higher, ensure:
- Organization-managed devices
- If Some settings are managed by your organization appears at the top of the Location settings page, location behavior may be controlled by policy. In that case, contact the organization’s IT administrator to review device and app location policies that might be forcing a static or old location.
If, after confirming these settings, the device still reports the same old location in all apps, focus on whether the scenario involves Remote Desktop/Cloud PC (use Allow location override) or an app with its own stored/emergency address (for example, Teams Calls) and correct the app-specific location there.
References: