Windows 11 wrong location when my I.P. is correct

Restarting Geolocation Service did not correct the issue (wrong location despite well known ISP location).

This is annoying because time zone is set automatically from location.

There should be a way to set the location based on IP address.

There should be a way to set the location manually.

Thanks for sharing these details.

Yes, the IP Address is correct. I completely understand about resetting the router and laptop.

That's why I am suggesting to try it with a different internet connection. Sometimes, because of a particular internet provider, such a problem occurs. Using a different WiFi network will help you find out. You can use a friend's internet, any public WiFi, or a nearby restaurant/cafe.

If it still doesn't work, there might be a different cause. To troubleshoot, you can restart the Windows Geolocation service.

1). Press the Windows key + R on your keyboard.

2). Type “services.msc” in the box.

3). Search for Geolocation Service.

4). Right-click on the service and select Automatic as the Startup type.

5). Click on Apply, then OK.

6). Restart the service.

Hi. I have responses posted in multiple threads. So... in as much as a change in the time server "seemed' to fix my tablet, my desktop (like you - in the same place) decided to have time zone issues after a Windows update. Changing the time server on it is not working along with the other usual suggestions.

A recent response on another time zone thread read as follows (a bit much for me though):

Take a look in the Recent Activity page in the Security section of your Microsoft account to see which type of IP address is being used to identify your login location for each device.

My bet is that since Microsoft had enabled the ability for their servers to support the newer IPv6 addressing sometime last year, that more and more individual computers, especially those supporting the newer drivers and technologies provided with Windows 11, are likely ending up with IPv6 addresses, leading to those being used by devices for the first time in many cases.

What this means is that though the old IPv4 addresses have been around forever and the locations associated with them have been adjusted at least to some extent long ago, in many cases the new IPv6 addresses have been used far less often and so in some cases may not yet contain valid location information.

Since that information is the responsibly of both Regional Internet Registries and for the morre3 detailed location information, the Internet Service Providers, this isn't something that Microsoft itself has any control over. Though people have become accustomed to quite accurate information relating to their personal smartphones, they forget that these actually contain a geolocation device using the GPS satellite location services, while at worst they can typically be roughly located using the cell phone tower(s) they're using, while the typically PC or tablet doesn't usually have these abilities and is more often located using its IP address.

Here's an article discussing these issues relating to IPv6 and Geolocation.

Understanding IPv6 Geolocation: Challenges and Tools

So if you determine your device is being attached to Microsoft servers using IPv6, it's most likely IPv6 involved and even if this isn't true, it's still highly likely it's your ISP or other network provider that's responsible for the inaccurate location information, since that's not something that Microsoft would handle other than for its own server or other internet facing network locations it's directly responsible for.

Rob

Same problem for the last 3 weeks. Windows 11 Pro (24H2) 'thinks' my PC is located in Manitou Springs, Colorado. In fact, I am located in Littleton Maine and Spectrums' head-end is in Presque Isle Maine and my external IP address confirms it. No VPN involved.

I REALLY do not want to reload Windows to fix this.

Eventually completely did a full refresh on the device. It seemed to work. But I did have to work a lot on it and lost some local files. I'll leave this thread but I hope someone else finds a better solution.

I did a full reset and it still didn't fix the problem.