A month after the Fenix 9 went on sale, the most useful document about it is not the spec sheet. It is a bug list that owners have been building in public on Garmin's own forum, and it is still growing.
A running tally compiled from Garmin's forums, Reddit threads and the major published reviews now runs past 90 entries. That figure is not Garmin's. It is a community count, and it should be read with the caveats below. What follows is what we could verify against Garmin's own forum threads.
The Shape of the List
The numbers behind the total are worth seeing, because they change what the number means:
- 7 are fixed, in software 6.48
- Roughly 30 are widely reported, meaning three or more separate owners or several reviewers
- Roughly 15 have two reports each
- Roughly 40 are single reports
That last group is where the honest caveats live. A single report can be a faulty unit, a settings problem or a user error rather than a software fault. At Fenix 9 prices, roughly GBP 1,000 or $1,100 for the Pro models and more with inReach, owners are not inclined to be forgiving about any of it.
What 6.48 Fixed
Garmin shipped software 6.48 on September 15, the first stable update for the platform, and it contained seven fixes:
- Garmin Locate displaying confusing locations and times
- Microphone not working if Voice Assistant is interrupted by an incoming call
- Potential battery drain for Pro devices with activated inReach plans
- Watchface translation and layout issues
- Voice alerts coming through when in Silent Mode
- Volume increment and decrement
It was a real list. It was also almost entirely housekeeping, and it left every headline complaint untouched.
What Broke After the Fix
New reports are still arriving, and several of them are against 6.48 specifically.
A Fenix 9 owner reported a reproducible crash on 6.48 where pressing the upper-right START button from the main screen causes the watch to crash and reboot immediately, before the Apps and Activities list appears. That is the button you press to begin a workout.
A separate Fenix 9 Pro Solar owner reported that changing settings inside Sleep Focus produces a restart. The same owner tested it on a Fenix 9 Pro AMOLED and found the AMOLED was unaffected, so this one appears to be Solar-specific.
And the Bluetooth complaints have not gone anywhere. One Fenix 9 Pro 51mm inReach owner documented six AirPods disconnects during a single 15km run on 6.48, each requiring him to open music settings mid-run, disconnect the headphones and reconnect. On several reconnections, the music restarted at maximum volume in his ears. He also reported his Garmin HRM 600 chest strap losing connection, which did not happen with the same strap on a Tactix 8.
We covered the Bluetooth situation in detail when 6.48 shipped, and it has not improved.
Performance Is Its Own Category
Several of the most consistent complaints are not bugs in the crash sense at all. They are the watch not feeling like a flagship.
One owner coming from a Forerunner 965 described the Fenix interface as "a lot slower, with many lags, frame drops and crashes," and reported that pressing START/STOP or LAP mid-run takes one to two seconds before the timer responds. For interval work that is not a cosmetic issue. His GPS, he said, was not on the same level as the Forerunner 965 even with all accuracy settings maxed out.
Navigation drew similar criticism from another owner: route calculation can take several minutes after selecting a destination, and going off-route triggers a recalculation that takes so long the watch may simply keep recalculating. On a device sold for adventure use, that is the wrong thing to be slow.
The Satellite Bug Developers Found
One of the more technical entries surfaced in Garmin's Connect IQ developer bug reports, which is a different and more revealing place to find a problem.
The report states that all Fenix 9 models fail to support the GNSS configuration options except for SatIQ, meaning watch faces and data fields that previously let users choose a specific satellite mode cannot do so on the Fenix 9.
Garmin's developer account responded directly, confirming the Fenix 9 series "only supports SatIQ and won't allow you to set select configurations like you've been able to in the past," and previewing an upcoming SDK release with new mode constants for SatIQ Normal, Extended Battery, Max Battery and Max Accuracy.
That is a confirmed regression against every earlier Garmin watch, acknowledged by Garmin on the record.
Garmin Is Responding, Carefully
It would be unfair to say Garmin is ignoring this. A staff account has been replying in the threads.
On the owner-compiled bug list thread, Garmin's representative addressed the entries one at a time. On the NRST shortcut that owners reported doing nothing, the response was that NRST is for nearest airport on aviation devices and therefore "would not have an effect" on the Fenix 9, followed by an acknowledgement that if that is the case, the shortcut should not be listed on a non-aviation watch.
On Bluetooth dropouts, Garmin pointed owners to its troubleshooting FAQs and asked for details by email. The company also confirmed that 6.48 was initially released to 20 percent of devices, the staged rollout Garmin uses before a full push.
That is engagement. It is not a fix.
How to Read the Number
Three things are true at once, and all of them matter.
The total is inflated by its methodology. A bug list compiled from forums, Reddit and reviews counts complaints, and people with a working watch do not post. A watch sold in the tens of thousands will accumulate a long thread from a small, motivated minority. Roughly 40 single reports at the bottom of the list are exactly the entries most likely to be faulty hardware or user error.
The total is also understated in one way. Many entries are one person's post standing in for a problem affecting far more owners who never report it. Garmin's own staged rollout to 20 percent suggests the company knows it needs to watch for volume.
And the pattern matters more than the count. The complaints are not spread thin across obscure features. They cluster on Bluetooth audio, optical heart rate, crash-on-launch, GPS accuracy and navigation speed. Those are the core functions people buy the watch for, and they are the functions that were still generating new reports this weekend.
Bottom Line
A month after launch, a community-compiled tally of Fenix 9 problems has passed 90 entries, with seven fixed in software 6.48 on September 15 and roughly 30 widely reported by three or more owners. The list includes crashes when opening Apps and Activities on the current firmware, a Solar-specific Sleep Focus restart, six AirPods disconnects in a single 15km run, a one-to-two second lag on the start and lap buttons, route recalculation measured in minutes, and a Garmin-confirmed regression that removes GNSS configuration choice from every Fenix 9 model except SatIQ.
Garmin is responding in the threads and has confirmed a staged rollout, but the fixes so far address housekeeping rather than the features owners are complaining about. Treat the total as a signal about how rough the launch has been, not as 90 proven defects.
If you own one, report what you find on Garmin's forum. That is what produced this list in the first place.
Sources: Garmin's official Fenix 9 Family System Software 6.48 release post and changelog of September 15, 2026, including the seven documented fixes; Garmin forum threads in the fenix 9 Series section including "F9 Bug List 6.38," "Fenix 9 crashes and reboots when opening Apps & Activities," "Fenix 9 Pro 51 mm inReach - 6 AirPods disconnects during a 15 km run after update 6.48," "BUG - Changing settings in Sleep Focus on Fenix 9 Pro Solar Results in Restart," and "Fenix 9 running SW 6.38 - few bugs so far," with replies from Garmin staff accounts and affected owners; Garmin's Connect IQ developer bug report "Fenix 9 Position.CONFIGURATION_GPS_xxxxx not supported" and the official Garmin developer response confirming SatIQ-only support and previewing upcoming SDK constants; Garmin's published Fenix 9 series pricing across base, Pro and Pro inReach configurations; and coverage of the 6.48 release by Notebookcheck and Garmin-focused outlets confirming the seven-fix count.