PSA: iOS 26.2 Turns on Automatic Software Updates for Some Users

[Starfia]

iOS 26 continues to be quite "popular".


View attachment 2587734

I can't recall how exactly a tab was closed in iOS 18, but I'm definitely getting tabs closed in two steps on iOS 26 while searching for a three-step way.

 

[I7guy]

I can't recall how exactly a tab was closed in iOS 18, but I'm definitely getting tabs closed in two steps on iOS 26 while searching for a three-step way.

Two steps. Long press in the address bar and then touch either close tab or close all tabs.

Or to close the current tab pinch to shrink and then press the “x”.

Took me thirty seconds to figure that out.

 

[boswald]

And on MR that also means: Please Stay Angry.

Sadly, you’re not wrong. 😔

 

[zorinlynx]

If Apple wants us to update, how about not drastically changing the look and feel of the system, arguably for the worse, in a single release?

 

[neuropsychguy]

The iOS 26.2 update force-turned on Apple Intelligence. I had it turned off. I turned it back off.😒

Updating to iOS 26.2 didn’t do that to me. I have Apple Intelligence off because of the space savings and it’s still off after the update.

 

[neuropsychguy]

Two steps. Long press in the address bar and then touch either close tab or close all tabs.

Or to close the current tab pinch to shrink and then press the “x”.

Took me thirty seconds to figure that out.

You can also just drag up from the address bar and touch the X to close.

 

[dampfnudel]

I always like to wait at least a couple of days before updating in case there’s a serious problem with the update.

 

[NetMage]

I still don't understand exactly how a simple software update process could possibly bring the U.S. airport network to its knees, but countless people were affected by this foolish oversight.

There is nothing simple about a Crowdstrike update. Crowdstrike is deeply embedded in Windows and can interfere with core Windows processes.

In this particular case, a code update was deployed months earlier that added new rule’s capabilities but they weren’t in use. Initial rules added to use the new capability matched test cases and worked fine. A few months later a rules update added a rule that used the new code in a different way supported but untested way, which turned out to trigger a number of bugs. Since Crowdstrike is so tightly integrated into Windows, crashing caused Windows to crash and reboot.

 

[artifex]

Not to excuse them ignoring user preferences, but I just read they may have rushed out those updates because of active 0-day exploits.

Hoping to read more about it later, but I'm going to be disgusted if it was due to a browser engine vulnerability, because you shouldn't have to patch the whole OS to update that.