Your desktop has no GPS — it verifies through Wi-Fi, which is probably off.
DraftKings Geolocation Not Working on Desktop: Plugin, Wi-Fi and Browser Fixes

The short answer
Desktop geolocation fails for a different reason than mobile: a computer has no GPS chip, so GeoComply triangulates from Wi-Fi networks around you. If Wi-Fi is off (common on desktops with Ethernet), the check can't verify you. Fix: turn Wi-Fi on, install or reinstall the GeoComply browser plugin when prompted, grant the browser location permission, kill any VPN, and switch from incognito to a normal window.
In this article
The desktop version of DraftKings verifies location through GeoComply the same way mobile does, but with one handicap: laptops and desktops lack GPS receivers. The check instead triangulates your position from the Wi-Fi networks your machine can see — the same databases phones build. That means the single most common desktop failure is simply having Wi-Fi disabled.
The checklist
- Turn Wi-Fi on. On a desktop connected by Ethernet, enable the Wi-Fi adapter anyway — you don't need to connect to a network, the adapter just needs to be able to see nearby networks. On a laptop, make sure Airplane Mode is off.
- Install the GeoComply plugin if prompted. Sportsbooks on desktop typically require a small browser plugin or a companion app (GeoComply's Player Location Check). Download it only from the prompt inside DraftKings — third-party downloads are a security risk.
- Grant the browser's own location permission: the lock icon in the address bar > Site settings > Location > Allow.
- Disable VPN, proxy, and relay-style extensions (ad-blockers with VPN features, iCloud Private Relay on Safari for Mac).
- Use a normal browsing window — incognito/private mode blocks the plugin and the permission the check needs.
- Restart the browser after installing or reinstalling the plugin, then log in again.
When the plugin installs but still fails
Two scenarios cover most stubborn cases. Corporate or school machines: managed devices often run enforced proxies and block plugin installs entirely — there's no fix except a personal device. Remote-desktop software: if AnyDesk, TeamViewer, Chrome Remote Desktop or a VM is running, GeoComply flags the session as remotely controlled and refuses it. Close the remote software fully — not just the window — and retry.
Antivirus web-filtering features (Avast/Kaspersky/Bitdefender secure browsing) can also intercept the plugin's connection; temporarily disabling the web shield is a valid test to isolate the cause.


