I've experienced several instances were the incremental is missing necessary files or misses files from previous updates that for whatever reason didn't get updated. I ALWAYS recommend using the combo updater, even if updating from the immediate prior release, for example, even if updating from 10.13.4 to 10.13.5, I would still using the combo, not the incremental. For High Sierra, the fixes are included in 10.13.5 update. It is actually Security Update 2018-003 for Sierra and El Capitan is the most current. In any case, for emergencies, you should ALWAYS have another boot option available to regain access to your working partition in case of trouble.Īs of June 4, 2018, this MU listing is incorrect. With disk drives so inexpensive and HUGE these days, there is no excuse not to have an external boot drive or to divide your existing internal drive into multiple partitions, plus macOS is SO easy to clone and excellent cloning software is readily available (Chronosync, SuperDuper, CarbonCop圜loner to name just a few). it takes a few reboots and a lot more time before everything is updated. If you try to update the same drive you boot from, not all files can be updated first time around because the system is still running, its like trying to replace a rug while you are still walking on it. This is because by booting from a different drive, the one you are updating is completely accessible and files can be updated quickly without delay. In my experience, this virtually eliminates the reports you hear about the update taking forever, and or the system taking forever to reboot, or runs slow after the update. never boot from and install an update to/from the same boot partition. That's a tip everyone should follow, i.e. I don't know if it would have worked had I gone through MAS I always apply my updates by manually running the installer BECAUSE I always boot from another drive to run update. Then I was able to apply SecUpdate2018-004 (which results in build number 15G22010 btw). I had to first RE-APPLY SecUpdate2018-003 (the newer one and the one you get currently if you download a fresh copy from Apple) to get the build number from 15G21012 to 15G21013. Run it over SecUpdate2018-003 build 15G21013 and no issues.
NOW, if you try manually try to run SecUpdate2018-004 over SecUpdate2018-003 build 15G21012, it will refuse and say the SecUpdate2018-004 update can not be installed.
If you installed the initial SecUpdate2018-003 download, the build number shows 15G21012, if you waited and downloaded it after Apple replaced it with the new one, the build is 15G21013 when completed. There were TWO SecUpdate2018-003 updates for El Cap, an initial and a slip stream version that Apple very quietly slipped in to replace the initial one a few days later. When applying SecUpdate2018-004 to previous SecUpdate2018-003 installation on El Capitan, HEADS UP.
0 kommentar(er)
