Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

watchOS 11.2 Beta 2 Failing to Install on Some Apple Watch Models: 'Software Update Failed' [Fixed]

MacRumors

MacRumors

macrumors bot
Original poster
Apr 12, 2001
65,979
34,766


Apple today seeded the second beta of watchOS 11.2 to developers for testing, but some users are unable to install the beta at this time, according to posts from affected users across the MacRumors Forums and social media.

watchos-11-smart-stack.jpg

The issue appears to be limited to the Apple Watch Series 9 and Apple Watch Ultra 2, at least based on the reports we have seen so far. Affected users are receiving a "Software Update Failed" message after attempting to install the latest beta. Users with other Apple Watch models have been able to install the beta without any problems.

Apple might have to re-release the second watchOS 11.2 beta to fix this issue. We will update this story as more details become available.

Other developer betas released today include the third betas of iOS 18.2, iPadOS 18.2, and macOS Sequoia 15.2, and the second betas of tvOS 18.2 and HomePod Software 18.2. All of the updates should be released in December.

Update: The issue has been resolved, according to Nicolás Alvarez.

Article Link: watchOS 11.2 Beta 2 Failing to Install on Some Apple Watch Models: 'Software Update Failed' [Fixed]
 
Article Link
https://www.macrumors.com/2024/11/11/watchos-11-2-beta-2-installation-issue/
Last edited:
Not worry everyone, for Apple Support is here to the rescue. Here is the standard response:

1. This is not an issue because if it was, Apple Support would know about it before a customer does, because they talk to millions of customers an hour.
2. For issues like this, you'll need to re-install WatchOS and set-up the watch as new. If the issue persists, you'll need to install a profile and collect logs, with Mail logging enabled, just to be safe. After you collect the logs, you'll upload them to Apple to attach to the RTA.
3. Engineering will reply in 48 hr, confirming this is a known issue, there is no current fix, keep your device up to date, and no further troubleshooting will be provided.
 
  • Haha
  • Disagree
  • Like
Reactions: mganu, srbNYC, zmicier and 11 others
goonie4life9 said:
Not worry everyone, for Apple Support is here to the rescue. Here is the standard response:

1. This is not an issue because if it was, Apple Support would know about it before a customer does, because they talk to millions of customers an hour.
2. For issues like this, you'll need to re-install WatchOS and set-up the watch as new. If the issue persists, you'll need to install a profile and collect logs, with Mail logging enabled, just to be safe. After you collect the logs, you'll upload them to Apple to attach to the RTA.
3. Engineering will reply in 48 hr, confirming this is a known issue, there is no current fix, keep your device up to date, and no further troubleshooting will be provided.
Click to expand...

Wrong, once you are on a beta they will excuse themselves and not help at all unless you are running the latest public release
 
  • Like
  • Haha
Reactions: macfacts, tshane, decypher44 and 1 other person
goonie4life9 said:
Not worry everyone, for Apple Support is here to the rescue. Here is the standard response:

1. This is not an issue because if it was, Apple Support would know about it before a customer does, because they talk to millions of customers an hour.
2. For issues like this, you'll need to re-install WatchOS and set-up the watch as new. If the issue persists, you'll need to install a profile and collect logs, with Mail logging enabled, just to be safe. After you collect the logs, you'll upload them to Apple to attach to the RTA.
3. Engineering will reply in 48 hr, confirming this is a known issue, there is no current fix, keep your device up to date, and no further troubleshooting will be provided.
Click to expand...
It's beta things happen.
 
  • Like
  • Disagree
  • Love
Reactions: TracerAnalog, Radeon85, PTVMan and 3 others
This issue is all over social media. The fact that Apple has yet to pull it from the servers for uw2 is problematic.
 
  • Haha
Reactions: LlamaLarry
Models newer than Series 6 and Series 7 use an "Apple Encrypted Archive" for OTA updates instead of zip.

The Series 9 and Ultra 2 (N207bAP N207sAP N208bAP N208sAP N210AP) are using Apple Encrypted Archive but don't have the decryption key in the update server response. This may not be the actual cause (they can still decrypt the update in other ways), but then that would be an incredible coincidence in affected models.
 
  • Like
Reactions: Realityck
Just trying on my Watch Ultra 2 and get the exact same rror. Watch are on charger and unlocked, iPhone just installed the latest beta released today. Probsbly I will need to wait for fix or release of the new beta
 

Attachments

  • IMG_0732.png
    IMG_0732.png
    147.1 KB · Views: 14
  • Like
Reactions: slimejester
contacos said:
Wrong, once you are on a beta they will excuse themselves and not help at all unless you are running the latest public release
Click to expand...
Wrong, Apple Support must follow the standard response protocol. It's science!

But seriously, this is either a server or specific package issue.
 
I somehow left my watch on Beta updates after the 11.1 RC/final and was unpleasantly surprised to find Beta 11.2 installed yesterday. Doesn't seem to be a way to go back even with an unpair/reset so I'm glad I caught it before this.
 
goonie4life9 said:
Not worry everyone, for Apple Support is here to the rescue. Here is the standard response:

1. This is not an issue because if it was, Apple Support would know about it before a customer does, because they talk to millions of customers an hour.
2. For issues like this, you'll need to re-install WatchOS and set-up the watch as new. If the issue persists, you'll need to install a profile and collect logs, with Mail logging enabled, just to be safe. After you collect the logs, you'll upload them to Apple to attach to the RTA.
3. Engineering will reply in 48 hr, confirming this is a known issue, there is no current fix, keep your device up to date, and no further troubleshooting will be provided.
Click to expand...
This would be too funny if it wasn't so sad and true. This is exactly my experience with Apple support, beta reports and dealing with their engineers. I keep finding edge cases, report, report, wait, wait, then finally raise such a fuss that they finally collect more information, confirm I was right all along and push a semi-fix out in an upcoming release (think USB drives sleeping and ejecting, universal control, etc...) The universal control one took me years to get their attention on.
 
nicolas17 said:
Models newer than Series 6 and Series 7 use an "Apple Encrypted Archive" for OTA updates instead of zip.

The Series 9 and Ultra 2 (N207bAP N207sAP N208bAP N208sAP N210AP) are using Apple Encrypted Archive but don't have the decryption key in the update server response. This may not be the actual cause (they can still decrypt the update in other ways), but then that would be an incredible coincidence in affected models.
Click to expand...

Hah, so I was right about the cause. They added ArchiveDecryptionKey to the affected devices now and it's fixed.
 
  • Like
Reactions: LlamaLarry and Realityck
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back