Apple Watch Series 6 fails to install watchOS updates, stuck on 7.5

Hi Filip,

Thank you — this is extremely useful.

I compared your crash report with mine, and I believe we can now confirm that we are experiencing exactly the same underlying issue.

Your Watch is Watch6,3, while mine is Watch6,4, so these are two separate Series 6 devices. However, both are running the same original system:

watchOS 7.5 (18T567)

More importantly, both crashes show:

Termination Description:
DYLD, missing lazy symbol called

and both are running exactly the same UpdateBrain binaries:

UpdateBrainService UUID:
2CB8AF1F-A1D0-31DC-86B9-009C942505A4

UpdateBrainLibrary.dylib UUID:
70C3EDEB-3C20-3F33-A3EC-40CC484F4785

Even the UpdateBrainLibrary crash offsets are identical:

UpdateBrainLibrary.dylib + 441312
UpdateBrainLibrary.dylib + 441184

followed by the same sequence of calls through UpdateBrainLibrary.

This is important because it makes hardware failure or corruption of my individual Watch much less likely. We now have at least two independent Apple Watch Series 6 devices, Watch6,3 and Watch6,4, both on watchOS 7.5 (18T567), deterministically crashing the same Apple UpdateBrainLibrary binary at exactly the same point.

My current theory is therefore that the UpdateBrain currently being served by Apple is no longer binary-compatible with the watchOS 7.5 userspace. It appears to call a lazy-linked symbol that does not exist in 7.5, and dyld aborts UpdateBrainService before the actual watchOS installation can begin.

I have also established that changing the target watchOS version does not solve the problem. I was able to make my Watch download watchOS 11.6.2 (22U95) instead of 26.6, but preparation still produced the same UpdateBrainService crash, using the same UpdateBrainLibrary UUID and the same crash offsets.

So at this point I would not erase your Watch unnecessarily. Your crash strongly suggests that the problem is not your particular iPhone or Watch hardware. Keeping it operational on 7.5 may be the safest state until Apple fixes the UpdateBrain asset or provides another supported upgrade/restore path.

Please keep your complete .ips file. Having a second independent crash report is extremely valuable if we can get this escalated to Apple/watchOS engineering.

I think we should both submit this through Apple Feedback/Support and reference the fact that there are now multiple Series 6 devices showing the identical deterministic UpdateBrain crash.

Thank you very much for posting the log — this is the strongest confirmation of the issue I have seen so far.

Hi Filip,

Thank you — the fact that your crash occurred specifically while trying to update from 7.5 to 8.8.2 actually makes this even more interesting.

Between the two of us we have now reproduced essentially the same failure while targeting:

• watchOS 8.8.2

• watchOS 11.6.2

• watchOS 26.6

and in all cases the starting system is watchOS 7.5 (18T567).

I would make one small distinction regarding the “missing piece in 7.5” theory. Based on the crash, I suspect 7.5 itself may not necessarily be damaged or incomplete. The problem may instead be that the UpdateBrain currently being delivered by Apple’s update infrastructure expects a symbol/API that does not exist in the watchOS 7.5 userspace.

The strongest evidence is that your Watch6,3 and my Watch6,4 received the exact same:

UpdateBrainLibrary.dylib UUID: 70C3EDEB-3C20-3F33-A3EC-40CC484F4785

and both crash with:

DYLD, missing lazy symbol called

at the same UpdateBrainLibrary offsets.

So the target watchOS version apparently does not matter — 8.8.2, 11.6.2 and 26.6 all fail before the actual OS installation starts because the UpdateBrain process itself crashes on 7.5.

That also explains why changing iPhones and iOS versions does not solve it.

Regarding a complete re-flash: yes, that is something I am also very interested in. Apple Watches do have service/recovery mechanisms beyond the normal consumer OTA process, but whether Apple or a central repair depot will actually perform a full firmware restore on a Series 6 rather than replacing/refusing service is another question.

If you contact Apple again, I would specifically ask them not to treat this as a normal “Unable to Update” case, but to escalate it with the crash report and point out that there are now at least two independent Series 6 devices on 7.5 producing the same UpdateBrainService crash.

Please let me know what Apple says. I will do the same from my side.

And definitely keep the Watch working on 7.5 for now — I would avoid unnecessary erase/unpair cycles until we know more.

Thanks again. Having your independent Watch6,3 crash report makes the case much stronger.

This sounds reminiscent of something reported here, Apple watches cannot be updated to watchO… - Apple Community, which is a different problem but it sounds familiar.

Your Series 6 watch can be updated to watchOS 26. In fact, when you do an update, that is the version it will download and update to (or try to update to).

You first tried with "iPhone 6s on iOS 14.8." That won't work because to update the watch to watchOS 26, your iPhone must be running iOS 26 or later (which I believe means an iPhone 11 or later).

You then tried it on a "newer iPhone running iOS 27.0.1" I think that should normally work but see the link above, some users have reported that when they have already updated the iPhone to 27.0.1, they report problems updating their watch if the watch is on something earlier than 26.6, since yours obviously is given that watchOS 26 is the latest it can run.

You will no doubt respond, "but this makes no sense," and I do agree ... it makes no sense. Yet what those users were reporting is that at least for their watches and iPhones, first the watch had to be brought to 26.6 paired to a watch that is on 26.6. If the watch was on an earlier watchOS (one person was on 26.3), then if the iPhone was already on iOS 27, updating the watch failed past 26.3.

This sounds a bit similar to your problem but certainly yours is a variant, not quite the same but different versions of that problem were reported in that thread. If you have access to an iPhone on 26.6, it might succeed in getting the watch to 26.6.

I think this is actually a bug or an oversight that Apple will need to fix because it does not seem right that an iPhone on iOS 27 cannot successfully update a watch that is on something earlier than 26.6. It ought to simply update the watch to the latest version that watch can take. But those failed updates are what was reported in that thread above, but also note that SOME (but not all) of the affected users were able to get past it with various different mitigations. So maybe review that thread and try some of the solutions that worked.

I reread your original post.

"I initially paired the watch with iPhone 6s on iOS 14.8. The watch paired and functioned normally."

That makes sense (to me). It matches expected behavior from what I have read online. (My watch Series 11 and iPhone 15 are both now on 27.0.1 so I don't have direct experience with your situation. My Series 11 is my first Apple watch ever.)

"To eliminate compatibility concerns, I also paired it with a newer iPhone running iOS 27.0.1 The result was exactly the same. The watch can see and download the latest available watchOS update (26.6), but the installation fails every time."

If you reread the link I sent earlier, one signature of the problem at least some readers were having is that once they had tried with an iPhone on iOS27 and the watch update to 26.6 failed, they were unable to reset or restore their watch at all. Multiple people complained, "it is now a brick." Or if it was not a brick, they could never update to 26.6 on the watch no matter what they did.

Aren't you experiencing this same issue, basically? No matter what, the 26.6 update does not complete?

Again, I think this is an anomaly that Apple needs to be made aware and then Apple needs to fix it. You (and everyone else) should report it here: Feedback - Watch - Apple . I would do that myself except my devices are all working fine on OS 27.

You could try going to the Apple Store and request service. I would try for a Genius Bar appointment so you can be there in person when they do or try something.

I have continued investigating this issue and now have more specific evidence that the failure is occurring inside Apple’s MobileSoftwareUpdate infrastructure on the Watch itself, rather than during download, pairing, Wi-Fi connectivity, or update discovery.

The Watch is still running watchOS 7.5 (18T567), but I was able to test a specifically selected watchOS 11.6.2 (22U95) OTA update. The update was successfully discovered and downloaded, but the preparation/installation phase failed again.

Immediately after the failure, the Watch generated a new crash report for:

com.apple.MobileSoftwareUpdate.UpdateBrainService

with:

Termination Description: DYLD, missing lazy symbol called

The crash occurs inside UpdateBrainLibrary.dylib.

More importantly, I compared this new crash with the UpdateBrainService crash from my previous update attempt. The binaries are identical:

UpdateBrainService UUID:
2CB8AF1F-A1D0-31DC-86B9-009C942505A4

UpdateBrainLibrary.dylib UUID:
70C3EDEB-3C20-3F33-A3EC-40CC484F4785

The UpdateBrainLibrary call-stack offsets are also the same between the failures, including:

UpdateBrainLibrary.dylib + 441312
UpdateBrainLibrary.dylib + 441184

The library is being executed from the dynamically staged XPC bundle:

/private/var/db/com.apple.xpc.roleaccountd.staging/com.apple.MobileSoftwareUpdate.UpdateBrainService...xpc/

This strongly suggests that the Watch successfully reaches the software-update preparation stage, but the staged UpdateBrain binary attempts to call a lazy-linked symbol that is unavailable in the watchOS 7.5 userspace, causing dyld to abort the UpdateBrainService before the actual OS update can proceed.

In other words, this does not appear to be a network/download issue. The update payload downloads successfully. The failure occurs locally on the Watch when Apple’s staged UpdateBrain code executes.

If anyone from Apple Software Update / watchOS engineering happens to see this: could you please check whether the currently served UpdateBrain is still binary-compatible with watchOS 7.5 (18T567) on Watch6,4?

I can provide the complete .ips crash reports, UUIDs, binary image list and additional diagnostics if useful.

I would especially appreciate any way to get this escalated beyond normal erase/re-pair troubleshooting, as those steps cannot resolve a deterministic dyld missing-symbol crash in UpdateBrainService.

Thank you.

crash log: com.apple.MobileSoftwareUpdate.UpdateBrainService-2026-10-24-053408

Hi,

did you get any further with this issue? I think i might have exactly the same problem as you.

Recently i got my hands on watch s6, long stored in my wifes drawer. It wasn't even paired so I tried with iPhone on IOS 26.6, it pairs, downloads watchOS 26.6, but fails at the verification stage with just ''Unable to update'' message.

From than I borrowed iPhones 7, XS and other &, each on different IOS version. On every IOS 15 or higher the upgrade fails exactly the same way. Only IOS 14.8 was I able to sucesfully pair the watch without upgrading watchOS and check which watchOS is installed. And ofcourse its 7.5.

Now trying to update the watch when it's at least working I thought could potentially work as I should be able to upgrade directly from watch bluetooth off and wifi on, however the watch is paired to IOS 14.8 and it will not prompt me any possible updates, only that I need to update the iPhone first.

I am a little hesitant to update to 15.8.8 IOS as in case erase on the watch needed, I will not have any iPhone to pair the watch with. It was already a nightmare finding out old enough iPhone in someone's drawer on 14.X ios.

I could help checking the logs too if there is someone willing to help me how to do it.

Thanks for posting this.

Hi again,

thank you for the reply. Yes, i believe this is the case too. The log I sent was actually when I tried to upgrade to watchOS 8.8.2. I am no developer by any means, only what Claude Ai explained to me it seems there is a missing piece in 7.5 to be able to update to ANY newer and signed watchOS, as 8.8.2 is the first Apple-signed release after 7.5, so it can work with old devices like iPhone 6s/7, which only get IOS 15.8.8.

As you confirmed watchOS 11.6.2, and we both did with watchOS 26.6.

I am a little sad as I don't believe Apple will ever pay attention to this.

I will keep the .ips file and I already submitted through Apple Feedback, I will make them know it is not alone case once they get back to me.

I wander if Apple is able to re-flash the watch completely in-house. I have zero fate in any authorized service center, as I already tried one before digging deeper myself, but asking them to send it to Central depot might help.

Thank you.

Thank you for the suggestion.

I also considered a version compatibility issue between older watchOS and newer iOS releases.

However, I found a crash log generated exactly when the update attempt fails. The crash originates from MobileSoftwareUpdate.UpdateBrainService, which makes me think the update subsystem itself may be failing rather than the installation being rejected because of version compatibility.

Unfortunately, I currently do not have access to an iPhone running iOS 26.6, but if I get a chance to test that scenario, I will report back.

Before testing with iOS 27.0.1, I also updated the iPhone 6s to iOS 15.8.8 specifically to test whether the watch would at least install watchOS 8.8.2.

The result was the same. The watch detected the update, and downloaded it, but watchOS 8.8.2 could not be installed.

Because the failure occurs across multiple iPhone and iOS versions, I am becoming less convinced that this is purely a compatibility issue between watchOS and iOS versions.

Thanks again for taking the time to reply.

I was able to retrieve the log and as far as I can see it is exactly the same issue as described in the original post.

crashlog: com.apple.MobileSoftwareUpdate.UpdateBrainService-2026-10-25-173513

My series 9 fails on updating and now I have basically bricked my watch. Super mad that Apple has allowed this issue to occur with no way to bypass the update