Apple watchOS Update Older Apple Watch Models: What the 2025 Bug Revealed

When Apple shipped watchOS 11.3 alongside iOS 18.3 on January 27, 2025, a server-side misconfiguration briefly locked owners of Apple Watch Series 4, Series 5, and the first-generation SE out of watchOS 10.6.1, the most recent version of watchOS 10. Some of those watches lost the ability to pair with an iPhone entirely. Apple fixed it, but the incident made something concrete that usually stays abstract: on older Apple Watch hardware, missing your last available update doesn’t just leave you behind. It can make the watch stop functioning as a connected device.

What went wrong with the watchOS 10.6.1 install on older Apple Watch models

The failure traced back to a single compatibility value. When Apple pushed watchOS 11.3, it bumped a value that over-the-air updates use to confirm device eligibility from 22 to 24, a number associated with late watchOS 11 builds, according to a researcher cited by MacRumors. For devices running watchOS 11, nothing changed. For Series 4, Series 5, and first-gen SE watches capped at watchOS 10, the update server stopped recognizing them as eligible to receive watchOS 10.6.1.

The problem only hit devices that couldn’t install the newest update to begin with, as Macworld noted. Any watch already running watchOS 10.6.1 before January 27 was fine. Anyone trying to install it for the first time was locked out.

Apple addressed the misconfiguration after reports surfaced, per MacRumors. No new software shipped; the fix was server-side. But the window was real, and the pairing failures that came with it showed exactly what a permanent lock-out looks like in practice.

Which Apple Watch models were affected by the watchOS update issue

The problem applied to Apple Watch models limited to watchOS 10, and only to those not already running watchOS 10.6.1 when watchOS 11.3 shipped, according to MacRumors. Specifically:

Apple Watch Series 4
Apple Watch Series 5
Apple Watch SE, first generation

Owners of these models who were already on watchOS 10.6.1 before January 27 were unaffected. The update stayed installed and functional. It was anyone still on an earlier watchOS 10 build who found themselves stranded.

Models capable of running watchOS 11, which requires at minimum a Series 6 or second-generation SE, per Macworld, were unaffected entirely. For those devices, the compatibility value change was expected and caused no disruption.

What actually breaks when an older Apple Watch can’t update

The pairing failure is the bluntest outcome. Some Series 4, Series 5, and first-gen SE watches running earlier watchOS 10 builds lost the ability to pair with an iPhone during the January 2025 window, according to both Macworld and MacRumors. Local apps still worked. Workout tracking still ran. But anything requiring Apple’s servers became inaccessible.

Pairing failure doesn’t mean the watch stops ticking. It means the watch stops working as an Apple Watch. FaceTime from the wrist, iMessage, activation on a new iPhone: all depend on Apple’s infrastructure confirming the device is legitimate before completing a connection. A watch that can’t clear that check gets cut off silently, without a useful error message.

The January 2025 incident was temporary. Apple’s fix restored access quickly. But the scenario it demonstrated, an older watch stuck on a pre-10.6.1 build, unable to update and unable to pair, is structurally identical to what a permanent service cutoff would look like. The mechanism is the same. The only variable is whether Apple reverses the decision.

Why the final update matters more than it seems

watchOS 10.6.1 shipped on August 19, 2024, per Macworld. For Series 4, Series 5, and first-gen SE owners, it’s the last update these models will receive. Not a milestone to acknowledge and move past, but the fixed point everything depends on.

Apple’s servers aren’t static. Compatibility values change. Certificate requirements shift. Infrastructure that supported older software gets updated or retired, usually without any communication directed at owners of legacy devices. Most of the time that process is invisible. The January 2025 incident was the exception that showed what the routine depends on.

The specific mechanism matters here. A researcher identified that Apple bumped a compatibility value associated with late watchOS 11 builds, and that bump was enough to strand an entire tier of older hardware, according to MacRumors. Apple caught it and fixed it. But the fix required no announcement to Series 4 or Series 5 owners. Those owners learned about the problem, and its resolution, through third-party reporting.

For anyone still running an earlier watchOS 10 build: Apple did restore access after the incident, so watchOS 10.6.1 should be installable now. There’s no guarantee a similar configuration change won’t recur.

How to check and update your Apple Watch Series 4, Series 5, or SE

Confirming your software version takes less than a minute.

Find your model: Open the Watch app on the paired iPhone, go to General, then About. The model name is listed there. Apple’s support pages cross-reference which watchOS version each model supports.

Check your software version: In the Watch app, go to General > Software Update. Your current version appears at the top.

What you’re looking for:

Series 4, Series 5, first-gen SE: you want watchOS 10.6.1. Anything earlier, install now.
Series 6 and later, second-gen SE: these models support watchOS 11 and aren’t affected by this issue.

To install: Place the watch on its charger, keep Wi-Fi connected, and have the paired iPhone nearby. In the Watch app, go to General > Software Update and follow the prompts. Installation typically runs 20 to 30 minutes. If FaceTime or iMessage has already stopped working, installing the update is the right first move; service authentication generally re-establishes on the next server sync after the update completes.

The January 2025 incident showed that update availability on older models isn’t permanently guaranteed. Apple’s fix came through quickly that time. Installing watchOS 10.6.1 while it’s available removes any dependency on that staying true.

What this means for older Apple Watch hardware going forward

The January 2025 incident wasn’t a policy change. Apple didn’t decide to strand Series 4 and Series 5 owners; it made a configuration mistake and corrected it. But the episode illustrated, more clearly than any support document would, what the practical end of the line looks like for these devices.

Series 4, Series 5, and first-gen SE owners are running hardware Apple stopped developing for. watchOS 10.6.1 is the last update these watches will receive. When Apple’s infrastructure eventually requires changes that watchOS 10 can’t accommodate, service access for these models will end. No press release will mark the moment. FaceTime will stop connecting. Pairing with a new iPhone will fail. The watch will still tell time.

Getting to watchOS 10.6.1 now keeps these watches inside Apple’s ecosystem for as long as Apple’s servers allow. Staying on an older build means depending on Apple to never repeat the January 2025 configuration error, and getting it right every subsequent time. That’s a thinner margin than it might appear.