Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows 8.1 Enterprise Windows 8.1 Pro Windows 8.1 Windows RT 8.1 More…Less
Symptoms
When you are in a GPS-only scenario (for example: no cellular or Wi-Fi), some location apps, such as Bing Maps and Google Maps that call the GeoLocation API to get GPS location information can’t retrieve the correct GPS data from the GPS sensor in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. The apps show the user in last location they were at instead of their current location.
Cause
This issue occurs because the GNSS location sensor takes longer to get a reading than the cellular or Wi-Fi sensor. The original API doesn’t wait long enough for this GNSS-only scenario.
Resolution
To fix this issue, install the May 2016 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (KB3156418).
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
Registry information
After you install this update, you must add the following registry entry:
-
In Registry Editor, locate and then select the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Location
-
Press and hold (or right-click) Location, point to New, and then click DWORD (32-bit) Value.
-
Name the new registry entry as WaitLongerForGPS.
-
Double-click the WaitLongerForGPS registry entry.
-
In the Edit DWORD Value dialog box, enter 1 in the Value data field, and then click OK.
-
Exit Registry Editor.
References
Learn about the terminology that Microsoft uses to describe software updates.
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
I have been googleing a lot. As far as I can tell it will require a lot of work to get the internal GPS chip in my lenovo helix working with any kind of map software. The new stuff is that in windows 8 the internal GPS is a sensor, and not available via the COM port interface. Most software uses the old COM port stuff. The new software from the app store in windows 8 uses the windows location service, which seems to be ignoring the internal chip all together. None of the apps in metro can get accurate coordinates. Just Geo locate by city using IP. This is so bad. Is the GPS functionality useless? Who is at fault, Lenovo or Microsoft?
Edit: I think I fixed it, part of it at least. Under device manager, all you have to do is de-activate and re-activate. Then it will work. It stops working after a couple of minutes. But now at least antenna malfunction is out of the question! Yey!
It does it automatically, based on best-signal
When is GPS data provided to the Location API?
As in Windows 7, the Location API is built on the Sensors API, and the
information in location reports comes from location sensors. The
Location API determines the most accurate location sensor for a given
report type. This simplifies programming because the Location API will
only provide one report of a particular type, even when there are
multiple location sensors available. When the Windows Location
Provider and GPS both exist on the system and are providing data, the
Location API will use the sensor with the most accurate data. In most
cases when both WiFi and GPS are available, the GPS will be more
accurate and its data will be passed to the application.
source
- Remove From My Forums
-
Question
-
We, like many thousands of other seafarers have successfully run our navigation software on Windows platforms — until Windows 8 came along. Now our ability to input GPS data to our software via virtual port creation software such as Xport or Franson GPS
Gate has ended. These programs which detect GPS data on bluetooth or a USB port and distribute it to several programs via virtual ports simply will not function on Windows 8. Franson say that they have no solution so we are forced to stay with Windows 7. Unfortunately
the newer Windows 8 laptops will not allow you to install Windows 7, and so in our case we had to return a new Toshiba Ultrabook and scrounge around for an older model supplied with Windows 7. This has solved our problem in the short term, but with Windows
8 being forced upon us both in marketing and hardware terms, what of the future? Where do we go when the current hardware fails? Why have Microsoft not included support for this feature which has worked well for decades?Does anyone have a solution?
Ian Shepherd s/y Crusader
Answers
-
-
Marked as answer by
Sunday, December 23, 2012 2:09 AM
-
Marked as answer by
-
Hi Peter,
The Surface Pro does not have an internal GPS. While we have verified basic connectivity with an external Garmin still
works on Windows 8 pro, we have not verified it with AutoRoute 2013. The optional external GPS that comes bundled with AutoRoute 2013 also has a location provider (http://msdn.microsoft.com/en-US/library/windows/hardware/ff545919(v=vs.85).aspx).While we do not expect end-consumers to have to know about the Windows Location Platform, IHVs/ISVs should
refer to the links in my earlier response to fully integrate with Windows Store Apps.Thanks,
Janet
This posting is provided «AS IS» with no warranties, and confers no rights.
-
Proposed as answer by
Janet Schneider [MSFT]
Monday, February 25, 2013 4:20 PM -
Marked as answer by
Doron Holan [MSFT]
Monday, February 25, 2013 6:12 PM -
Edited by
Janet Schneider [MSFT]
Monday, February 25, 2013 7:12 PM
clarification
-
Proposed as answer by
I’m looking for a way to gather internal GPS data from a powershell script using Windows Location API, as the Windows Location Platform is no longer able to satisfy the need. Previously, there was a com object to use.
Is there a way for this to be accomplished in Windows 10?
asked Sep 18, 2017 at 20:34
1
An example of using the System.Device.Location method, this should be what you’re looking for.
Add-Type -AssemblyName System.Device #Required to access System.Device.Location namespace
$GeoWatcher = New-Object System.Device.Location.GeoCoordinateWatcher #Create the required object
$GeoWatcher.Start() #Begin resolving current locaton
while (($GeoWatcher.Status -ne 'Ready') -and ($GeoWatcher.Permission -ne 'Denied')) {
Start-Sleep -Milliseconds 100 #Wait for discovery.
}
if ($GeoWatcher.Permission -eq 'Denied'){
Write-Error 'Access Denied for Location Information'
} else {
$GeoWatcher.Position.Location | Select Latitude,Longitude #Select the relevent results.
}
answered Sep 18, 2017 at 20:41
colswcolsw
3,2161 gold badge14 silver badges28 bronze badges
1
Make sure location is set on. Ohterwise it outputs ‘Access Denied for Location Information’
answered Nov 20, 2021 at 13:16
LouisLouis
32 bronze badges
1
gpsthinkpadwindows 8
I have been googleing a lot. As far as I can tell it will require a lot of work to get the internal GPS chip in my lenovo helix working with any kind of map software. The new stuff is that in windows 8 the internal GPS is a sensor, and not available via the COM port interface. Most software uses the old COM port stuff. The new software from the app store in windows 8 uses the windows location service, which seems to be ignoring the internal chip all together. None of the apps in metro can get accurate coordinates. Just Geo locate by city using IP. This is so bad. Is the GPS functionality useless? Who is at fault, Lenovo or Microsoft?
Edit: I think I fixed it, part of it at least. Under device manager, all you have to do is de-activate and re-activate. Then it will work. It stops working after a couple of minutes. But now at least antenna malfunction is out of the question! Yey!
Related Question