Location Issue on my laptop with Windows 11

While much better than before the v126. Edge update I still notice an occasional wrong location as before but not as often. Better but not totally fixed IMO.

Awesome. I just updated Edge to the current referenced version on tablet. Will do so on Desktop. Shall I put the VPN proxy setting back to auto-detect? I had turned it off per article: Windows 11 Maps Shows Wrong Location: Fixed - NEXTOFWINDOWS.COM

New stable release of Edge v126.0.2592.56 arrived today. Seems to have fixed the geolocation issue many have reported here and elsewhere.

Ran a series of tests with MS maps app, Google and Bing maps as well as mylocation.org using browser geolocation. All reported the correct location for me. Let's hope it stays that way.

Yes, since yesterday, it now locates my correct town

New stable release of Edge v126.0.2592.56 arrived today. Seems to have fixed the geolocation issue many have reported here and elsewhere.

Ran a series of tests with MS maps app, Google and Bing maps as well as mylocation.org using browser geolocation. All reported the correct location for me. Let's hope it stays that way.

None of those I have chatted with or seen with the issue use the secure network features nor are they near that DC or use a vpn. This is a recurring issue over the years (based on reports) but for recent impacted users started within the past few weeks as did my issue.

Tom,

See my other message to you in that other thread, it explains portions of this.

The thing you are missing is that there really is a new issue entirely here as well, since the Secure Network feature is obvious involved in what's happening, even though as everyone seems to think including myself, we've got these specific features turned off when the issue is happening.

As JB-D-M here believes, this sounds like it might be a bug, and that's possible.

However, what I'm saying is that it's also possible that Microsoft has built something into Edge or even Windows itself that's watching for potential attackers trying to find your location and since the way most of us are testing this is to continually perform actions that trigger the location system, those might also be mis-triggering and forcing the Secure Network feature into a sort of 'protect' mode, where it continually blocks the remote site's ability to acquire your true location until some eventual timeout resets and returns it to providing the more accurate location again.

We don't know the true reason and apparently JB-D-M doesn't really care, but some of us do and would like to try and understand what may truly be causing this apparent failure to occur. That's why I'm providing all of this information, not to say it isn't happening, because it clearly is, I'm just not going to wait around complaining at Microsoft since I know that won't solve or speed up anything. I'll instead try to understand it better and see if there's a workaround to truly fix it for now.

Microsoft's own Support has been offering the same old solutions of clearing histories and some other related settings as you said, but the results of those have varied just as in the past as well, so they're really just running the same old playbook or online support scripts as they're trained to do, while I'm looking at what's actually changed for clues to what it may have triggered.

The reason it appears to have started recently is clearly due to a recent Edge browser update, which release every week or two from a separate system than Windows Update that few realize exists, though we've heard about it here in a few threads in the past. No great secret there, just something few realize even occurs other than due to the 'new features' web pages Edge typically displays when the browser next restarts.

Rob