When your Garmin watch suddenly takes 10 minutes or more to lock onto GPS—even under an open sky—the culprit is usually an expired or corrupted CPE.bin satellite file. This tiny file tells your watch where GPS satellites are located before you step outside. Deleting the broken file and syncing a fresh copy through Garmin Express or Garmin Connect usually brings fast locks back immediately.
Quick Answer
Check Settings > System > About on your watch to see if CPE says Expired or Missing. Sync with Garmin Express on a computer or Garmin Connect on your phone; if it still says Expired, connect via USB, delete
CPE.binfrom\GARMIN\RemoteSW\, safely eject, and sync again.
Device and Signal Snapshot
- Affected Devices: Garmin Forerunner, Fenix, Epix, Venu, Instinct, and Enduro watches (older models use
EPO.bininstead ofCPE.bin) - Affected Function: Initial GPS/GNSS satellite acquisition speed and early-mile route accuracy
- Severity: Low to moderate—the watch still tracks once locked, but workouts start late or show wild drift at the beginning
- Data Risk: Very low—deleting
CPE.binremoves only temporary satellite prediction data, not your activities or personal settings
What Is Actually Happening?
GPS satellites move continuously across the sky. Without a cheat sheet, your Garmin watch has to perform a “cold start”: it slowly listens to the raw radio broadcast from overhead satellites to figure out where each one is in orbit, which can easily take several minutes—especially if you are moving.
To avoid that wait, Garmin downloads a small predictive orbit file called CPE.bin (Connected Predictive Ephemeris) into your watch’s storage. That file maps where satellites will be for the next few days so your watch locks onto them within seconds.
If a Bluetooth or Wi-Fi transfer drops halfway through, CPE.bin can become unreadable or stuck on an old date. Your watch either ignores it or tries to parse bad coordinates, forcing a slow cold start every time you head out for a run. If you start running before the watch finishes that slow search, you will also run into The “Cold Start” GPS Problem: Why Your First Mile is Always Inaccurate.
How to Check If Your CPE.bin File Is Bad
You do not have to guess whether your satellite file is broken—your watch tells you directly:
- Hold the Up / Menu button (or open Settings on touchscreen models).
- Scroll to System > About.
- Press Down through the software and unit ID pages until you see the CPE status line.
Here is what those labels mean:
- CPE: Current: The file is up to date. If GPS still takes 10 minutes to lock, the issue is heavy tree cover, tall buildings, or a frozen activity screen rather than
CPE.bin. - CPE: Expired or Missing: Your watch has no valid satellite prediction data. Even if you synced your phone this morning, a stuck or corrupted file is blocking the refresh.
What Can Cause CPE.bin Corruption
- Interrupted phone syncs: Closing the Garmin Connect app or walking out of Bluetooth range while background files are transferring.
- Long gaps between syncs: Going a week or two without opening Garmin Connect or syncing over Wi-Fi lets the prediction window expire.
- Bad cached firmware or Wi-Fi errors: Failed over-the-air updates or router timeouts can leave a half-written
CPE.binfile sitting in theRemoteSWfolder. - Large location jumps: Flying hundreds or thousands of miles means your watch’s old sky map no longer matches the satellites overhead until it syncs or completes a fresh outdoor lock.
What to Do First
Start with the wireless refresh before plugging into a computer:
1. Force a Fresh Sync in Garmin Connect or Over Wi-Fi
- Make sure your phone has an active internet connection.
- Open the Garmin Connect app and tap the sync icon in the top-right corner, letting it finish completely.
- On Wi-Fi-enabled watches, trigger a manual Wi-Fi Sync from the watch’s controls menu or Settings > Connectivity > Wi-Fi.
- Re-check Settings > System > About on the watch to see if CPE switched back to Current.
If Wi-Fi sync itself throws a failure code while trying to pull satellite data, follow Garmin Error 103: How to Resolve WiFi Sync Communication Failures.
2. Perform an Outdoor GPS Soak
If CPE still shows Expired or you just traveled far from home, step outside into an open yard or parking lot, open an outdoor Run profile without pressing Start, and let the watch sit completely still for two to five minutes after the GPS ring turns green. Staying stationary lets the receiver download clean almanac data straight from the sky. You can make this a quick habit before key workouts using “GPS Soaking”: The 2-Minute Pre-Run Ritual for Medical-Grade Tracking.
What to Check If That Doesn’t Work: Delete CPE.bin Over USB
When wireless syncs leave CPE: Expired stuck in your About menu, the watch usually refuses to overwrite a corrupted file on its own. Removing the file manually over USB forces a clean replacement:
- Plug your Garmin watch into a Windows PC or Mac using a genuine Garmin data cable. (Note: On Mac, modern MTP watches require a free MTP file-transfer app such as OpenMTP so the watch folders appear.)
- Open the watch storage drive and navigate to
GARMIN > RemoteSW. - Look for
CPE.bin(orEPO.bininsideGARMIN > EPOon older Garmin models) and delete it. Do not delete other folders. - Safely eject the watch from your computer, or open Garmin Express on the computer and run a full Sync.
- Unplug the watch, restart it by powering off and back on, sync once more with Garmin Connect or Garmin Express, and confirm Settings > System > About now reads CPE: Current.
If your computer refuses to show the watch drive or Garmin Express stalls during the transfer, check Garmin Express “Error Transferring Files”: The USB-C Data Cable Check. For model-specific folder differences between older EPO and newer CPE watches, see How to Manually Update “Satellite Data” (EPO/CPE Files) on Garmin.
When It’s Actually a Different Problem
If CPE reads Current and you deleted/rebuilt the file cleanly, yet the watch still freezes on the startup screen or loses all responsiveness while searching for satellites, move to Garmin Forerunner “Wait for GPS” Freeze: The Satellite Pre-Cache Fix.
True hardware failure is rare, but contact Garmin Support if the watch still cannot lock onto any satellites after 15 minutes in a wide-open outdoor field with a verified CPE: Current status and updated firmware—that points to a damaged internal GNSS antenna or receiver chip.
Bottom Line: Check Settings > System > About first; if CPE is stuck on Expired or Missing after a phone sync, deleting CPE.bin from \GARMIN\RemoteSW\ over USB and syncing with Garmin Express clears the corruption in minutes.