Today’s software update, problem?

I was just on the phone with Apple Support, it's a known issue that affects only users in Australia and New Zealand. They are working on a fix, but in the meantime a workaround is to temporarily set the language to e.g. English US (instead of AU/NZ) and attempt the update again. That worked for me! After the update you can safely set it back to Aussie or Kiwi language again :-)

I don’t know. My first suggestion is to restart your phone, then try the software update on the phone again. There was a bunch of reports like yours yesterday, but I haven’t seen any today, so it may be fixed.

When you update using a computer it does not restore the device, it only replaces iOS and leaves your data untouched. To be extra safe, when you click update you have a choice of Download and Install or Download Only. Choose Download Only, then make Install a separate step.

It not only detected it, the update has been downloaded. Can you tap Install Now? The problem isn’t the update, it’s the update screen appears to be broken. As it’s downloaded, see if it updates automatically overnight. It needs to be plugged in, connected to Wi-Fi and locked; then the update should self-install.

Off hand, I would say that it looks like you have a very weak WiFi signal. You may want to try to get a better WiFi connection.

See the articles If your iPhone, iPad or iPod touch won’t update - Apple Support

If you can't update or restore your iPhone, iPad, or iPod touch - Apple Support

If you see an error when you update or restore your iPhone, iPad, or iPod - Apple Support

I spent some time today with the support chat. Things I've tried

1) Reboot phone and try update again - no good.

2) Restart phone with up volume, down volume, side button and try update again - no good.

3) Attempt to install update with itunes on windows PC. Gets through backup, and then hangs indefinitely - no good.

Support suggested I back up the phone and restore it and try again. That's a lengthy and somewhat risky procedure that I haven't tried yet -- largely because my icloud backup has 4 hours remaining to complete..

Maybe try updating through your computer.

Try force-quitting the Settings app→Close an app on your iPhone or iPod touch - Apple Support

I passed it up to the forum manager, who can pass it up the line, but it would be more effective if everyone with the problem would contact Apple official support using the Get Support link at the top of this page.

Can you tap Download & Install, which is displayed on the screen?

I see this in my errors log when I try to update (and I can't invoke the update from MacOS either)

<NSXPCConnection: 0x281d094a0> connection to service on pid 270 named com.apple.softwareupdateservicesd: Exception caught during invocation of reply block to message 'downloadAndInstallState:'.

Ignored Exception: Unable to activate constraint with anchors <NSLayoutXAxisAnchor:0x28363d7c0 "UITableViewLabel:0x1027e9830.trailing"> and <NSLayoutXAxisAnchor:0x28363d340 "UITableViewCellContentView:0x1027e9ad0.trailing"> because they have no common ancestor.  Does the constraint or its anchors reference items in different view hierarchies?  That's illegal.

(

0   CoreFoundation                      0x00000001a30225c8 58500388-BF36-397C-84CF-17315A3445B6 + 1217992

1   libobjc.A.dylib                     0x00000001b7aa17a8 objc_exception_throw + 60

2   CoreAutoLayout                      0x00000001b7d47710 9D52B2D9-88F6-3696-BDD7-2C5C39CB55E2 + 177936

3   SoftwareUpdateSettings              0x00000001e6964c38 36F37400-D51D-37E4-A9ED-BEEF7DBB33FA + 64568

4   SoftwareUpdateSettings              0x00000001e6963c78 36F37400-D51D-37E4-A9ED-BEEF7DBB33FA + 60536

5   UIKitCore                           0x00000001a5f44c20 186C18FD-1082-3811-A761-88E8376C7E69 + 17873952

6   QuartzCore                          0x00000001a63cb91c B5B69CA2-65B2-359F-BCFF-24FD57D1EBF7 + 1472796

7   QuartzCore                          0x00000001a63cbe00 B5B69CA2-65B2-359F-BCFF-24FD57D1EBF7 + 1474048

8   UIKitCore                           0x00000001a5f30c74 186C18FD-1082-3811-A761-88E8376C7E69 + 17792116

9   UIKitCore                           0x00000001a5f37b34 186C18FD-1082-3811-A761-88E8376C7E69 + 17820468

10  UIKitCore                           0x00000001a5c31fbc 186C18FD-1082-3811-A761-88E8376C7E69 + 14651324

11  UIKitCore                           0x00000001a5c32224 186C18FD-1082-3811-A761-88E8376C7E69 + 14651940

12  UIKitCore                           0x00000001a5c5f000 186C18FD-1082-3811-A761-88E8376C7E69 + 14835712

13  UIKitCore                           0x00000001a5c64d24 186C18FD-1082-3811-A761-88E8376C7E69 + 14859556

14  UIKitCore                           0x00000001a5c02918 186C18FD-1082-3811-A761-88E8376C7E69 + 14457112

15  UIKitCore                           0x00000001a5bfaedc 186C18FD-1082-3811-A761-88E8376C7E69 + 14425820

16  UIKitCore                           0x00000001a5c12e08 186C18FD-1082-3811-A761-88E8376C7E69 + 14523912

17  SoftwareUpdateSettingsUI            0x00000001e696daf8 D38DE291-41F4-3E2E-843F-F10BF7532797 + 15096

18  SoftwareUpdateSettingsUI            0x00000001e696d45c D38DE291-41F4-3E2E-843F-F10BF7532797 + 13404

19  SoftwareUpdateSettingsUI            0x00000001e6972a60 D38DE291-41F4-3E2E-843F-F10BF7532797 + 35424

20  SoftwareUpdateSettingsUI            0x00000001e6972eec D38DE291-41F4-3E2E-843F-F10BF7532797 + 36588

21  SoftwareUpdateSettingsUI            0x00000001e698069c D38DE291-41F4-3E2E-843F-F10BF7532797 + 91804

22  SoftwareUpdateSettingsUI            0x00000001e6980890 D38DE291-41F4-3E2E-843F-F10BF7532797 + 92304

23  CoreFoundation                      0x00000001a3027874 58500388-BF36-397C-84CF-17315A3445B6 + 1239156

24  CoreFoundation                      0x00000001a2efaba4 58500388-BF36-397C-84CF-17315A3445B6 + 7076

25  Foundation                          0x00000001a449d448 63D26DEE-A1FB-34B0-9ADA-CC52E7F1D60C + 2290760

26  Foundation                          0x00000001a4282e34 63D26DEE-A1FB-34B0-9ADA-CC52E7F1D60C + 85556

27  Foundation                          0x00000001a449eec8 63D26DEE-A1FB-34B0-9ADA-CC52E7F1D60C + 2297544

28  libxpc.dylib                        0x00000001eea71168 51B3F90E-3B21-383E-9DBD-AE48625C9E9D + 110952

29  libxpc.dylib                        0x00000001eea64a70 51B3F90E-3B21-383E-9DBD-AE48625C9E9D + 60016

30  libdispatch.dylib                   0x00000001a2c0f874 FFC93E7E-8360-32A0-9EB5-FE3761B8C90A + 18548

31  libdispatch.dylib                   0x00000001a2c2bf54 FFC93E7E-8360-32A0-9EB5-FE3761B8C90A + 134996

32  libdispatch.dylib                   0x00000001a2c1db2c _dispatch_main_queue_callback_4CF + 608

33  CoreFoundation                      0x00000001a2f9c1f8 58500388-BF36-397C-84CF-17315A3445B6 + 668152

34  CoreFoundation                      0x00000001a2f960d0 58500388-BF36-397C-84CF-17315A3445B6 + 643280

35  CoreFoundation                      0x00000001a2f951c0 CFRunLoopRunSpecific + 600

36  GraphicsServices                    0x00000001ba57d734 GSEventRunModal + 164

37  UIKitCore                           0x00000001a5a037e4 186C18FD-1082-3811-A761-88E8376C7E69 + 12363748

38  UIKitCore                           0x00000001a5a09054 UIApplicationMain + 168

39  Preferences                         0x0000000100c64c78 Preferences + 52344

40  libdyld.dylib                       0x00000001a2c51cf8 B08AB7C2-64E8-3937-9487-C33D0175FD34 + 7416

)

I have the same issue on three iPhones in my family, have an ultrafast internet connection and strong WiFi so that is not the issue. Suspect update servers are overloaded, but it may be something else as our two iPads didn't have this problem.

Well, Apple could have taken several weeks to test the update using every possible combination of settings on the phone to see if there was a conflict with any of them, but by then how many phones would have been compromised by this very serious security vulnerability that 14.5.1 resolves? 14.5.1 was released only a few days after 14.5 (which had been beta tested by over a million users for several months, and did not have this rather strange issue).

I’d say the quality control is really outstanding, because the cause of the problem was identified in less than 24 hours and a workaround was published.

Thanks, I’ve passed some examples of this issue to the forum manager. Meanwhile, see if the Get Support link at the top of this page can help.