Use Franson GPSGate on a Microsoft Surface Pro 11 (Surface Pro with 5G) running Windows 11

If Settings → System → About → System type shows an ARM-based processor, GpsGate can create a virtual COM port only if its virtual-serial driver is a native, properly signed ARM64 driver; Windows can emulate x86/x64 applications but cannot emulate their drivers.^1^

Most likely resolution

1. Open Settings → System → About and check System type.
2. If it says ARM64 or ARM-based processor, ask GpsGate support whether your exact GpsGate version includes a:
   • Native ARM64 virtual COM-port driver
   • Driver signed for current Windows 11
   • Driver compatible with Memory Integrity/HVCI
3. Do not rely only on the application being able to start. Windows 11 on Arm can emulate x86/x64 application code, but apps dependent on drivers require compatible Arm drivers.^2^
4. If GpsGate cannot provide that driver, Surface firmware or Windows settings cannot convert its x86/x64 driver to ARM64. The practical options are:
   • Use software that reads the Windows Location API and supports ARM64.
   • Use an external GNSS receiver with a vendor-supported ARM64 driver.
   • Run GpsGate on an Intel/AMD Windows computer if a legacy COM port is mandatory.

GpsGate documents virtual COM-port creation as a Splitter feature, but its public material does not establish ARM64 driver support.^3^

Rule out a COM5 conflict and identify the driver failure

The Surface supports third-party virtual COM ports in principle; support depends on the third-party driver, not on a Surface-specific prohibition.

1. Open Device Manager → View → Show hidden devices.
2. Expand Ports (COM & LPT), if present.
3. Check whether COM5 is already assigned, including to a faded/hidden device.
4. Retry with another unassigned number. This only addresses a port-number collision; it will not correct an incompatible or blocked driver.
5. Look under Ports, Software devices, and Other devices for a GpsGate or unknown device.
6. Open Properties → General and record the device status/error code. A signing failure can appear as Code 52.^4^
7. Open Event Viewer → Applications and Services Logs → Microsoft → Windows → CodeIntegrity → Operational and look for an event naming the GpsGate driver at the time port creation failed.

Windows requires kernel drivers to satisfy its signing policy; an unsigned or inadequately signed legacy virtual-port driver can be blocked.^5^

Memory Integrity: test only when Windows identifies the driver

Check Windows Security → Device security → Core isolation details. If Windows explicitly reports the GpsGate driver as incompatible or says that it cannot load:

1. First obtain an updated ARM64/HVCI-compatible driver from GpsGate.
2. If none is available and a controlled diagnostic test is acceptable, turn Memory integrity off.
3. Restart Windows and test port creation once.
4. Turn Memory Integrity back on and restart after the test.

Disabling Memory Integrity reduces protection and takes a Secured-core PC out of its Secured-core state. If disabling it makes the driver work, the durable resolution is still an updated compatible driver—not leaving the protection disabled.^6^

This test cannot make an x86/x64 driver work on ARM64; it applies only when Windows has specifically identified an otherwise architecture-compatible driver as blocked.

Surface GNSS, firmware, and Device Manager

The Surface Pro 11 Wi-Fi + 5G specification includes GNSS L1 with GPS, Galileo, BeiDou, QZSS, and NavIC.^7^

Install applicable updates through:

1. Surface app → Help & support → Check for updates
2. Settings → Windows Update → Check for updates
3. Restart after installation.

For manual deployment, Microsoft provides a Surface Pro 11th Edition Snapdragon driver/firmware package; select the package matching the installed Windows build.^8^

For the cellular hardware, Device Manager should show Surface 5G Mobile Broadband under Network adapters. The Surface update history also lists that component and associated mobile-broadband firmware.^9^

A separate Ports (COM & LPT) entry is not required for the internal GNSS to function. The integrated receiver is normally consumed through the Windows location/GNSS stack rather than exposed as a serial device.

Internal GNSS versus NMEA COM output

Windows GNSS drivers feed the Windows location service, and the internal GNSS interface is reserved for location-platform components rather than being a third-party serial COM interface.^10^ NMEA reporting is optional for a Windows GNSS implementation, so GNSS capability does not guarantee an NMEA stream.^11^

There is no documented Microsoft-provided facility that converts the Surface’s internal GNSS output into an NMEA virtual COM port. Microsoft’s supported application-facing path is Windows.Devices.Geolocation, with location permission enabled under Settings → Privacy & security → Location.^12^

Consequently, the legacy application must either support the Windows Location API, receive NMEA from an ARM64-compatible bridge supplied by a third party, or use an external serial GNSS receiver with compatible drivers.

References

1. Add Arm support to your Windows app
2. Using software and peripherals on Surface ARM-based devices | Microsoft Support
3. The original GPS signal splitter | GpsGate - GpsGate
4. Detecting Driver Load Errors
5. Driver signing
6. [Windows 11](https://support.microsoft.com/windows/hardware/drivers/a-driver-can-t-load-on-this-device)
7. Tech specs: Surface Pro for Business, Copilot+ PC, Snapdragon X Series processor, 11th Edition
8. Download drivers and firmware for Surface Pro | Microsoft Support
9. [Home](https://support.microsoft.com/surface/updates/surface-pro-11th-edition-update-history#improvements-and-fixes-in-the-updates)
10. Global Navigation Satellite System (GNSS) driver architecture
11. Global Navigation Satellite System (GNSS) driver requirements
12. Maps and location overview