Windows location service persistently reports weird incorrect location

The problem kinda "cleared itself" after a couple of weeks, but I came back if its full original glory in the middle of September. As of today, it still persists.

---

Also, I notice that my Edge browser on my Android phone is displaying some strange weather information. (I'm referring to that little temperature display in the top left corner of an empty start page.) When I click on that display the MSN Weather page that opens reveals that it displays the weather information for "Saint Louis Park". Which is essentially the same location near Minneapolis. (???)

The phone does have full geolocation capability (all enabled). Moreover, when I open the list of recent locations on that MSN Weather page, it does correctly list my current city and places a marker next to it, basically saying that it knows where I'm actually located. But it still insists on using "Saint Louis Park" as default location for weather in Edge for Android. I don't see any feature that would allow me to change it.

Of course, all apps (e.g. Google Maps) on my phone have no issue locating me correctly. Bing Maps launched inside that Edge browser also locates me correctly. Only that weather info feature in Edge is acting up... but it is kinda strange that it places me into the same Minneapolis location as my Windows machines.

So, does anyone have any idea about what's going on? What's so special about that spot near Minneapolis?

Same here. Now my location in jumping between my real location and a San Mateo, CA. It has been almost 1 month since I noticed that issue at my home.

I upgraded my DSL to AT&T fiber, All 3rd-party geolocation services I can find show the correct location of my IP (IPV4 is static, IPV6 is dynamic at AT&T but all of IPs I record are in correct place). Windows Location API is the only one has issue, and it made all maps services running in browser broken because browser uses location API)

"Hi Andrey, thanks for the update. Since both your Windows 11 and Windows 10 machines on the same LAN are reporting the same incorrect location, this strongly suggests that Microsoft’s location database has associated your public IP address or your router's gateway with that specific coordinate in Minneapolis.

Since you've already verified that IP-based geolocation sites work correctly, it confirms that your ISP is providing the correct location, but Windows Location Service is pulling from a stale or incorrect database entry. I agree with henry_collins that resetting the local cache is a good first step, but you might also want to try power-cycling your router to see if your ISP assigns you a different IP, which might force a re-update in Microsoft's database. If that fails, using the Feedback Hub is indeed the best way to flag this 'bad data' to Microsoft's geolocation team."

A correction: The aforementioned Windows 10 Pro x64 machine located on the same LAN also suffers from the same problem. It also places me at the same location in Minneapolis. 

Since the PC has no GPS or WiFi, Windows is likely using Microsoft's geolocation database and getting bad data. The fact that IP-based sites correctly show California while Windows Location reports Minneapolis strongly suggests a Windows Location Service issue, not a network problem.

Try clearing Location History, resetting Location Services, and checking for VPNs or recent updates. If it persists, reporting it through Feedback Hub may be the only way to get the location data corrected