Took a total of ~20 minutes to install the update from 12.5, from restart to the completed update.
2020 Intel 27” iMac and it’s “only” 1.18GB for me. Did you miss/skip an update?They so need to move to incremental updates...2 GB for a .1 release?
That's a complete installer for 12.5.1, not an updater.The full updater is almost 12 GB.
The size of the update does not in any way tell you how much was changed. OS updates are released by module. Say you have Module 1 that changed one character in the code. The whole thing has to be released as an update. You don’t just release one character. If you change one tiny thing in each of 20 modules, you have to release 20 modules, no matter how big or small the changes. For most modern OS’es, modules are generally libraries. 2GB just means enough code was changed to affect 2GB worth of libraries.They so need to move to incremental updates...2 GB for a .1 release?
Ask Microsoft how well incremental “patches” workThey so need to move to incremental updates...2 GB for a .1 release?
You made a backup first, right?This update just killed my new M1 iMac.. stuck in a reboot loop, one time it went into recovery mode and was not able to recover..
Now figuring out how to revive my $2500 paperweight..
It actually appears that this is exactly what they’re doing.They so need to move to incremental updates...2 GB for a .1 release?
I hope it doesn't ArrayDecayt your machine like it has for some unlucky punters.My first OS upgrade on my new Starlight MBA!
You say explited, I say exploited... let's call the whole thing off.
You mean .x.y releaseThey so need to move to incremental updates...2 GB for a .1 release?
I was shocked when I saw that it was 2GB. It took like ten minutes of my brand new M2 Starlight MacBook AirThey so need to move to incremental updates...2 GB for a .1 release?
Let’s assume so, but that misses the point. A backup is of little short term use if one cannot even boot into Recovery.You made a backup first, right?
1.18GB on M1 MBProThey so need to move to incremental updates...2 GB for a .1 release?
Might be released later, they did the same when 12.2.1 was released.are older macOS versions not vulnerable to this issue?
This update just killed my new M1 iMac.. stuck in a reboot loop, one time it went into recovery mode and was not able to recover..
Now figuring out how to revive my $2500 paperweight..