Apple Releases Rapid Security Response Updates for iOS 16.4.1 and macOS 13.3.1

[Lounge vibes 05]

I’m kind of curious whether this was just a first out of beta test or that an actual security update was delivered. It went really quick on my iPhone after the no internet problem was fixed.

Well given that the macOS update was way over 1/4 of a GB, I'm going to assume it includes something.
All the test releases they put out for Beta testers were all around 20MB, so clearly were just tests.

 

[Choco Taco]

It finally worked.

 

[TigerNike23]

Wow. That was fast. I’m using an XS Max, and it took maybe 40 seconds from tapping “Install” to typing this message.

 

[mxrider88]

Why do they call it rapid if it takes almost as long as a normal update and also requires a restart??

 

[Huracan]

Why do they call it rapid if it takes almost as long as a normal update and also requires a restart??

I guess because they don't wait for the next regular software update, but speed up the release of security fixes. On the other hand, although it required a restart the restart was much quicker than on a regular update, so in that sense it was also somewhat "rapid".

 

[CarAnalogy]

I'm going to one-up myself. Gave my phone a reboot, went to install (was already downloaded) the update and it ACTED LIKE it crashed my iPhone. But it booted and gave indication the Rapid Response update was installed. So, that was an intense 42 seconds 🤪

Now that’s rapid. Similar experience here, it sat on verifying for a while then I look down to see Apple logo and then the lock screen with no progress bar or anything, it was scary fast.

Glad they finally rolled this system out, it’s a lot better than the old way.

 

[Yrmmont]

I updated both my Iphones, Ipad and both Macs without any problem. Yay!

 

[Huracan]

That "unable to verify" message is misleading, the internet is just one reason verification can fail. If I have to guess it was caused by the security response not being signed by Apple for some reason when it first released.

That definitely could be one reason, but my guess would be that whichever server and microservice involved in that verification was not dimensioned properly and it was overwhelmed and unable to process all the requests (like in a denial of service attack). Probably allowing the user to keep hitting Retry might have contributed to the problem.

 

[Mac Hammer Fan]

Hopefully we will also see a security update for older OS such als iOS 15.7.5 and Monterey 12.6.5

 

[brunerd]

Not very rapid if they take just as a long as a regular software update... lol

Well, the required reboot is a bit disappointing for a "rapid" response but there's firmware in payload it seems. The preparation phase was estimated to be 5 minutes, but took 2 1/2 minutes and the application and reboot took 30 seconds. So not too bad, really.

 

[Ifti]

Installed on my iPad perfectly fine.
I notice you also have the option to remove the update as well now under the Software > General > iOS version menu.

Installing on my iPhone now - all seems good so far.

 

[BeatCrazy]

Is this a case where we now know that both Big Sur and Monterey are now inherently less secure than Ventura with a RSR update?

 

[alangore]

That was a fast install! And on an M1 Studio, M2 iPad, and iPhone 12.

 

[b17777]

That "unable to verify" message is misleading, the internet is just one reason verification can fail. If I have to guess it was caused by the security response not being signed by Apple for some reason when it first released.

I had one iPad update automatically earlier this morning, and I updated one manually right after no problem. A couple hours later I tried my phone and had the delay.

 

[Cunir]

Worked okay on my ipad

 

[mxrider88]

I guess because they don't wait for the next regular software update, but speed up the release of security fixes. On the other hand, although it required a restart the restart was much quicker than on a regular update, so in that sense it was also somewhat "rapid".

Yeah ok. I’m not so thrilled knowing they now can introduce bugs in a quicker way though…

 

[Marcel Turcotte]

Upon rebooting after installing 13.3.1 (a) on my MBP 14-inch M2, the LG UltraFine 4K external display was not recognized. I tried rebooting, rebooting in safe mode, changing 'Allow accessories to connect' to 'always,' but nothing worked. I could see that the MBP was getting power from the external display, but no display. I had an iPad Pro 12.9 M2 and an iPhone 12 connected to the external display. After unplugging those two devices and rebooting, the external display was recognized. This is the second time that the LG UltraFine external display is not recognized, which is well, annoying, to say the least. If memory serves me well, this had occurred after updating the OS the last time as well. I'm alone? Are there known workaround?

 

[JosephAW]

Wondering if iTunes can install it?

 

[TheYayAreaLiving 🎗️]

Wondering if iTunes can install it?

Try it with iTunes on windows and let us know. Retro style!

 

[I7guy]

Yeah ok. I’m not so thrilled knowing they now can introduce bugs in a quicker way though…

The bugs they introduce will be less worse than those they fixed.

 

[killhippie]

Wondering if iTunes can install it?

Nope and there is no need to, its done in seconds, fast reboot. Its not on iTunes or finder on my mac but you can trigger it by going to software update.

 

[libertysat]

Hung for a long time on Preparing so I gave up and moved on. Next thing I knew is I needed to login again.

 

[I7guy]

Wow. That was fast. I’m using an XS Max, and it took maybe 40 seconds from tapping “Install” to typing this message.

I’m using the max also. Got that “not connected” message. Probably servers overloaded as others suggested. But it was fast once it connected.

Edit: oh yeah for some odd reason needed to activate FaceTime and iMessage again.

 

[JosephAW]

How do you update using DFU mode?
I hope they don't stop signing 16.4.1.0?

 

[doboy]

So updated my Mac and had to type in my password and it rebooted after installing. So how is this rapid??? To be fair, it took ~2 min to reboot vs 10+ min with normal update, haha.