Windows geolocation services showing the wrong location (just like Eric Krellner 7/13/2026)

Reset the Windows Geolocation Service (lfsvc) cache from an elevated Command Prompt, because the closest matching Windows 11 case—wrong coordinates across applications and networks while IP location remained correct—was resolved by deleting that cache.^1^

Reset the geolocation cache

This removes only the Geolocation Service cache; Windows recreates it when the service starts.

1. Select Start, type Command Prompt, and choose Run as administrator.
2. Run:

net stop lfsvc
rd /s /q "%ProgramData%\Microsoft\Windows\LfSvc\Cache"
net start lfsvc

3. Wait approximately one minute, then request a fresh location from the PowerShell test or BrowserLeaks.
4. Confirm whether:
   • the coordinates change to New Hampshire;
   • the reported accuracy changes; and
   • Google Maps receives the corrected position after reopening the browser.

This is a moderator-recommended Q&A workaround rather than a documented fix for build 26300.9711 specifically. The Windows 11 26H2 release-health page does not list former-address geolocation as a known issue for that build.^2^

If the old coordinates return

Clear the last-known location associated with the Microsoft account:

1. Open the Microsoft account privacy dashboard and sign in with the account used in Windows.
2. Find Location activity.
3. Select Clear location activity and then Clear.
4. Restart Windows and test again.

Windows removed local location-history controls in March 2025, but when a Microsoft account and Location Services are used, the last-known location may be saved in the cloud.^3^

Do not repeat SFC, DISM, the repair installation, browser resets, sensor-driver toggling, or network switching; the consistent result from Windows APIs and multiple browsers already places the problem below those application-specific layers.

If cache and cloud clearing do not change it

The 150–200-meter accuracy is consistent with Wi-Fi-resolution location rather than IP-level location: Microsoft describes approximately 10–500 meters as generally Wi-Fi-derived, while IP-derived results are commonly broader than one kilometer.^4^

Windows can determine location from GPS, nearby Wi-Fi access points and routers, cellular towers, IP address, or a configured default location. Microsoft’s location database can contain wireless access-point MAC addresses, and location data may be shared with Microsoft’s location-service provider partners.^3^ Therefore, an unchanged result after rebuilding LfSvc\Cache would point away from a repairable Windows installation problem and toward location data being returned to Windows from an account or provider-side source.

Use these next steps:

1. Temporary workaround:
   Go to Settings → Privacy & security → Location → Default location → Set default, enter the current New Hampshire location, and save it. A default is used when Windows cannot determine a more exact location, so it might not override the erroneous 150–200-meter result.^3^
2. Submit a reproducible Windows report:
   Open Feedback Hub → Report a problem → Devices and Drivers → Location Services. Microsoft explicitly identifies that category for location-service reports.^5^ Include:
   • Windows 11 26H2 build 26300.9711;
   • the wrong coordinates and 150–200-meter accuracy;
   • correct IP-geolocation result;
   • results from both Wi-Fi and mobile hotspot;
   • identical Windows API, Edge, Chrome, and BrowserLeaks results;
   • confirmation that deleting LfSvc\Cache and clearing cloud location activity either corrected the issue or made no difference;
   • a link to the matching prior report.^6^

Avoid publishing the exact former-residence coordinates or address in the public Feedback Hub description; attach diagnostic data privately if the tool offers that option.

References

1. Windows 11 24H2 (Build 26200.8973) - Geolocation Service stuck on UK location until LfSvc cache deleted - Microsoft Q&A
2. Windows 11, version 26H2 known issues and notifications
3. Windows 11
4. Guidelines for location-aware apps
5. Changes to API behavior for Wi-Fi access and location
6. Windows geolocation services showing the wrong location