New Fenix 9 Pro Watches Wouldn't Pair // The Error Was on Garmin's Server, Not in the Box

November 18, 2026

New Fenix 9 Pro Watches Wouldn't Pair // The Error Was on Garmin's Server, Not in the Box

A brand new Garmin Fenix 9 Pro that will not pair is a horrible first hour with a very expensive watch. For several owners this week, that hour turned into several days.

The reports started on Garmin's own Fenix 9 forum on November 14. A buyer who took delivery of a Fenix 9 Pro 47mm in Autumn Orange, the non-inReach version ordered directly from Garmin, could not get through initial setup on any device. Garmin Connect found nothing on two Samsung phones. On an iPad the watch appeared over Bluetooth but pairing failed, and Garmin Connect pushed a support link about blocked inReach connections. On Windows, Garmin Express saw the watch over USB, identified it correctly, and then refused to register it.

That last failure was the useful one, because Garmin Express writes logs.

The actual error

The owner, who is also a Connect IQ developer, went through those logs line by line. Signing in worked. Pulling the account profile worked. Retrieving the country setting worked.

Registration did not. Garmin's endpoint at connectapi.garmin.com returned HTTP 400 Bad Request with this message:

Cannot find Application for Part Number [006-B4953-00]

That part number is not a mystery. It is the Fenix 9 Pro 47mm, and it appears in Garmin's own Connect IQ SDK 9.3 device definitions under the device ID fenix9pro47mm. The watch was reporting product SKU 010-04336-06 and firmware 5.31 out of the box.

So Garmin's device identification service knew exactly what the watch was. The registration service acting on that identity did not. That is a mismatch between two Garmin systems, not a broken watch.

Bluetooth was fine too. The owner paired the watch with a generic BLE tool on Android without any trouble, which rules out a radio problem and points straight back at the server.

It was not one unlucky unit

The first reply came from a UK owner with the same model, also bought direct from Garmin UK, and with a worse story: the watch failed, they returned it, and the replacement failed identically. Two units, same failure, from a 950-pound purchase.

They also noticed something odd. Garmin Connect sometimes identified the watch as the inReach version and sometimes as the standard Pro, and pairing failed either way. That detail fits the error message. If the registration service cannot resolve which application belongs to a part number, it can land on the wrong one.

More owners joined through the week:

  • A Fenix 9 Pro 51mm on a Pixel 10 XL, with several Samsung phones tried as well
  • A buyer whose watch arrived the next day and hit the same wall
  • Others on Reddit and in Garmin Facebook groups, per owners in the thread

Different sizes, different phones, different continents. Reinstalling Garmin Connect, rolling back to older Connect versions, factory resets and fresh Windows installs changed nothing.

What Garmin told people

Support responses were inconsistent, which is normal in the first days of a backend fault.

A Netherlands support agent told one owner it was an individual problem with their watch and to return it. A UK owner was told on Tuesday that the issue had been escalated because multiple people were reporting it and returning watches, and that Garmin's US team was working on it, with no estimate for a fix.

Garmin itself stayed quiet. No staff post appeared in the thread at any point. If you want the official version, there still isn't one.

The fix, as far as anyone can tell

By Wednesday morning, owners were pairing again.

A UK owner who had been stuck for days got through with this sequence: complete the watch setup without connecting to a phone, try pairing in Garmin Connect (which failed again), force-close the app, reopen it a few minutes later, accept the prompt to add the device and retry, and pair. The registration email arrived, and the watch immediately updated to firmware 6.74.

Another owner on Reddit reported the same steps working, according to Garmin Rumors and Gadgets & Wearables. Garmin support had told one buyer that engineering made "a few backend changes."

Hold that loosely. Owners in the thread were still reporting failures as recently as Wednesday morning, so this looks like a partial recovery rolling out rather than a clean all-clear. If your watch will not pair today, it is worth retrying before you box it up, and it is still worth trying tomorrow.

Why the firmware detail matters

The affected watches shipped on 5.31. The current Fenix 9 stable is 6.74, with 7.19 in beta.

You cannot install either one until the watch is registered, because registration is what links the device to your account and pulls the update. So owners stuck at registration were also stuck on software that shipped months ago, without the shutdown fixes in 6.73 or the bug list progress since. That is the part that turns an annoying setup failure into a genuinely bad out-of-box experience.

It also may be part of the cause. The Connect IQ SDK entry for this watch points at firmware 6.48, and 5.31 is well behind it. A registration service that maps firmware part numbers to applications could plausibly choke on a build it has never seen. That is a hypothesis from an owner reading logs, not a Garmin statement, and nobody outside Garmin can confirm it.

What to do if yours will not register

  1. Set the watch up on its own first, without pairing.
  2. Try Garmin Connect. If it fails, force-close the app and wait a few minutes.
  3. Reopen Connect and accept the retry prompt if it appears.
  4. If that still fails, try Garmin Express on a computer, then contact support and quote the error: Cannot find Application for Part Number, with your model and size.
  5. Do not return the watch before trying again. Two owners replaced good hardware for a server fault.

If you are buying a Fenix 9 Pro now, assume a day of patience rather than a dead unit. The Fenix 9 range on Amazon and the 47mm Pro listings here are where most of these are moving right now.

Bottom line

A registration error that rejects a valid part number is the kind of bug that should be caught before a flagship ships, and the fact that two replacement watches failed the same way makes the whole thing look worse than it is. Nothing was wrong with the hardware.

The telling detail is the inconsistency inside Garmin: one team's service knew the watch, another team's service would not accept it, and support was still telling people to return good watches while engineering quietly patched the backend.

We have covered the Fenix 9's software problems before, including the Bluetooth dropouts that survived 6.48 and the bug list passing 90 entries. This one is different in an important way. It is not the watch misbehaving. It is Garmin's own systems failing to recognise the watch it built.

Sources: Garmin Forums thread 448104, Cannot pair or register new Fenix 9 Pro, Gadgets & Wearables, Garmin News, Garmin support FAQ on blocked inReach connections.

Buy:

Here's what we're seeing available on Amazon:

Buy on Amazon