Fix in CMD
net stop lfsvc
rd /s /q "%ProgramData%\Microsoft\Windows\LfSvc\Cache"
net start lfsvc
Windows 11 24H2 (Build 26200.8973) - Geolocation Service stuck on UK location until LfSvc cache deleted
![](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(96, 34%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Brent
0
Reputation points
My Windows PC suddenly thought it was in Ulverston, UK. Automatic time zone switched to GMT, and every app using Windows geolocation (Google Maps, Chrome Geolocation API, etc.) received the same incorrect coordinates. My public IP correctly resolved to Melbourne, Australia, there was no VPN, and the issue occurred on multiple networks.
Restarting the Geolocation Service did not help. The fix was:
After deleting the LfSvc\Cache folder, Windows immediately rediscovered the correct location and automatically corrected the time zone.
Has anyone else seen the Geolocation Service cache become permanently stuck on an old/incorrect location??
Windows for home | Windows 11 | Settings
Answer recommended by moderator
1 additional answer
Sort by: Most helpful
-
![](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(246.4, 15%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Alex-L 10,190 Reputation points Microsoft External Staff Moderator2026-08-05T14:07:04.31+00:00 Hi Brent
Glad to hear clearing the LfSvc cache resolved the issue. I'll go ahead and recommend your answer for better visibility, so that those who may run into the same thing as you can find this much needed solution.
This appears to have been a stale or corrupted Windows Geolocation Service cache causing Windows to persist an incorrect UK location despite the correct IP-based location. Since deleting the cache immediately restored accurate location detection and time zone settings, your findings could help others experiencing similar issues on Windows 11 Insider Build 26200.8973.
If the problem does not return, it was likely a one-time cache corruption. Consider submitting feedback through Feedback Hub so Microsoft can investigate whether this affects other Insider users.