macOS High Sierra (10.13) Unsupported Macs Thread

[Caesar_091]

I have the same unibody MacBook and I don't have any issues with the App Store Updates. It is probably safer to install 2018-002 SU manually(read the first page of this thread).

Never updated my system: this is the state from the very first installation of High Sierra OS.

Also:
- my MacBook on each reboot plays the "boong" sound two times... is that normal?
- my network location list was wiped out installing High Sierra with the reported tutorial... is that normal?

 

[danyMRF]

Apple has released "Security Update 2018-003" for macOS High Sierra (10.13.6).

(The Build version of the System should be 17G4015)

Please share your installation experience and first operating impressions on unsupported Macs.

Thanks!

 

[Takohashi]

Apple has released "Security Update 2018-003" for macOS High Sierra (10.13.6).

(The Build version of the System should be 17G4015)

Please share your installation experience and first operating impressions on unsupported Macs.

Thanks!

I installed this update without any problems, like the previous one (2018-002).

 

[jbarley]

I installed this update without any problems, like the previous one (2018-002).

Does the 2018-003 update show in "About This Mac" similar as seen here in the photo of my Sierra installation?


[doublepost=1544052218][/doublepost]

Apple has released "Security Update 2018-003" for macOS High Sierra (10.13.6).

(The Build version of the System should be 17G4015)

Please share your installation experience and first operating impressions on unsupported Macs.

Thanks!

Unfortunately this update failed exactly as did 2018-002 did, with the same error message.
It does show a build version of 17G4015 but not show as installed under About This Mac-Installations.

 

[Falstaff66]

Does the error message and the update missing from the installation log mean the update "failed" if the build and Safari versions are both listed as current, and the update is no longer showing in the App Store? Is there a definitive answer to this question?

 

[jbarley]

I also attempted this update on a supported system, (2012 mac mini) and the end result was the same, correct build number but not showing up in the install log.
The installation proceeded slightly different, no error message, system just hung on reboot and required a hard restart.
The security update for Sierra (2018-006) installed without any problem as have all previous Sierra updates.

 

[Takohashi]

Does the 2018-003 update show in "About This Mac" similar as seen here in the photo of my Sierra installation?

View attachment 808708

Yes.



Do not pay attention to the Russian language in these screenshots. It is my native language.

 

[MDangerous]

I also attempted this update on a supported system, (2012 mac mini) and the end result was the same, correct build number but not showing up in the install log.
The installation proceeded slightly different, no error message, system just hung on reboot and required a hard restart.

Same here on my unsupported MacPro 3,1.

 

[LEXX_Gruzovik]

Macbook Pro 5,5 freezes during install of security update)

 

[mrploppy]

Couldn't someone doctor the scripts in the RecoveryUpdate.pkg to either (a) do nothing and just return, or (b) return a success code, or whatever's required, so that the installation could at least finish and thereby show itself in the installation log? A couple of people on here have said that the Recovery partition is useless anyway, so on that basis does it really matter whether its Update scripts run at all?

 

[BartmanEH]

has anyone compiled a list or computed the success rate for the ROM patcher tool for APFS support? I'm toying with trying it but don't wanna brick my old iMAC.

 

[EugW]

I had all sorts of problems with Security Update 002 (October) on both my unsupported High Sierra machines. I don’t think it ever installed correctly as it crashed during install on both machines and I couldn’t see a record of its install. This was attempted through the App Store. I didn’t try the manual method.

However...

Macbook Pro 5,5 freezes during install of security update)

Yesterday’s Security Update 003 installed fine via Software Update on my MacBook5,1 and The App Store indicates it was correctly installed. (I originally thought it worked on my MacBookPro5,5 too, but that was just Safari. The Security Update 003 failed, and now I can't install it.)

I can confirm with the built number and About This Mac when I get home.

However, am I right to think that these security updates are NOT cumulative? IOW, am I still missing the security updates from 002?

 

[EugW]

Macbook Pro 5,5 freezes during install of security update)

Yesterday’s Security Update 003 installed fine via Software Update on my MacBook5,1 and The App Store indicates it was correctly installed. (I originally thought it worked on my MacBookPro5,5 too, but that was just Safari. The Security Update 003 failed, and now I can't install it.)

However, am I right to think that these security updates are NOT cumulative? IOW, am I still missing the security updates from 002?

Here are the results from my MacBook5,1. As mentioned, the update on my MacBookPro5,5 seems to have failed.

Note though, there is no Security Update 002 installed, since that failed.

Also note that the build number is the same for both my MacBook5,1 and MacBookPro5,5. Does that mean the security update actually got installed on the MacBookPro5,5? Or perhaps just part of the security update?

The downloaded High Sierra Security Update 003 file won't let me install it on the MacBook Pro (without modification).

 

[avz]

Never updated my system: this is the state from the very first installation of High Sierra OS.

Also:
- my MacBook on each reboot plays the "boong" sound two times... is that normal?
- my network location list was wiped out installing High Sierra with the reported tutorial... is that normal?

From what I gather some people had luck fixing various things by running scripts(automation etc.) in Onyx.
I am not quite sure what is normal at the startup, my MacBooks seem to spin the DVD drive at startup.

 

[BartmanEH]

[...]However, am I right to think that these security updates are NOT cumulative? IOW, am I still missing the security updates from 002?

This thread suggests that updates are cumulative but this thread conflicts and says they're not.

 

[jbarley]

FWIW I just completed a fresh clean install of High Sierra 10.13.6 on a supported machine and once completed checked for updates, the only security update listed was 2018-003.
So if Apple is not worried about previous updates, why should I?

Edit: Using the clean install above plus a tip from another forum member (Fishrrman) I created a "Mule" drive and after cloning it to my MacPro3,1 High Sierra boot drive (excluding the Home folder) and running the Post installer patch tool I now have a fully updated MacPro3,1 running High Sierra 10.13.6.
Took some fiddling but then this is only a hobby for me and I'm always looking for things to pass the time.

 

[avz]

FWIW I just completed a fresh clean install of High Sierra 10.13.6 on a supported machine and once completed checked for updates, the only security update listed was 2018-003.
So if Apple is not worried about previous updates, why should I?

Edit: Using the clean install above plus a tip from another forum member (Fishrrman) I created a "Mule" drive and after cloning it to my High Sierra boot drive (excluding the Home folder) and running the Post installer patch tool I now have a fully updated High Sierra 10.13.6.
Took some fiddling but then this is only a hobby for me and I'm always looking for things to pass the time.

View attachment 809064

Which build version of HS did you clean install on a supported machine?

 

[L Caputo]

FWIW I just completed a fresh clean install of High Sierra 10.13.6 on a supported machine and once completed checked for updates, the only security update listed was 2018-003.
So if Apple is not worried about previous updates, why should I?

Edit: Using the clean install above plus a tip from another forum member (Fishrrman) I created a "Mule" drive and after cloning it to my High Sierra boot drive (excluding the Home folder) and running the Post installer patch tool I now have a fully updated High Sierra 10.13.6.
Took some fiddling but then this is only a hobby for me and I'm always looking for things to pass the time.

View attachment 809064

The latest Security Updates include the previous SecUpdates so no need to download them individually.
Also if this was a recent download of the full High Sierra installer it would probably have included the last security updates prior to this one.

 

[ScooterComputer]

It would be an interesting test for the Security Updates that are failing on the Recovery Partition update to see if REMOVING the Recovery Partition completely before attempting the update causes the install script to skip that component. Considering that the Recovery Partition is really of very little use for most of us, not having one isn't as tragic as it might be for "supported" users. (FWIW, I recommend everyone keep a microSD with the patched installer on it nearby at all times.) I'm running a MacBookPro5,5, so it isn't exactly EASY for me to swap drives, but perhaps an unsupported MacPro user here in this thread might would give it a whirl.
If jettisoning the Recovery Partition completely is what "fixes" this, then by all means that would be the smartest thing to have the patcher do, what we should be recommending in the thread.

 

[jbarley]

Which build version of HS did you clean install on a supported machine?

10.13.6 build #17G65
[doublepost=1544199951][/doublepost]

It would be an interesting test for the Security Updates that are failing on the Recovery Partition update to see if REMOVING the Recovery Partition completely before attempting the update causes the install script to skip that component. Considering that the Recovery Partition is really of very little use for most of us, not having one isn't as tragic as it might be for "supported" users. (FWIW, I recommend everyone keep a microSD with the patched installer on it nearby at all times.) I'm running a MacBookPro5,5, so it isn't exactly EASY for me to swap drives, but perhaps an unsupported MacPro user here in this thread might would give it a whirl.
If jettisoning the Recovery Partition completely is what "fixes" this, then by all means that would be the smartest thing to have the patcher do, what we should be recommending in the thread.

I tried removing (deleting) the Recovery partition back when attempting to get Security Update 2018-002 to install.
Didn't change a thing, still failed with the same error message.

 

[ATC]

Apple has released "Security Update 2018-003" for macOS High Sierra (10.13.6).

(The Build version of the System should be 17G4015)

Please share your installation experience and first operating impressions on unsupported Macs.

Thanks!

Same as before, the update fails on my iMac 9,1. Basically it would restart normally to begin the update process, but then about half way through the progress bar would simply go back to the beginning and it would just stay there indefinitely. I had to force reboot and it says updates were not installed and in the MAS the 003 security update is no longer available as an option to download.

But as you can see, it does say build 17G4015 in About This Mac:

 

[humanafterall]

Apple has released "Security Update 2018-003" for macOS High Sierra (10.13.6).

(The Build version of the System should be 17G4015)

Please share your installation experience and first operating impressions on unsupported Macs.

Thanks!

On a Mac Pro 3,1 the update installation was close to finish and I got the message:
An error occurred while running scripts from the package “SecUpd2018-003HighSierra.RecoveryHDUpdate.pkg”

After the restart the boot screen appeared normally but there was a freeze around the 3/4 of the progress bar. A loading spinner appeared over the progress bar and went on without any progress.

After a hard shut down I run dosdude1 postinstall script and it booted normally but with a serious performance graphics lag. Black blocks on animated UI elements, lagging scroll and and an overall bad graphics performance and security update wasn't installed.

I reinstalled the OS with the dosdude1 patch tool and everything works well now but without the security update installed.

@dosdude1 Any suggestions?

 

[BartmanEH]

On my Mac 10,1 sec update 2018-003 "installed" the same as previous updates (although I skipped 2018-002)--fails on recovery partition (despite it being a functional recovery partition), reboots cleanly with no hangs, presents a "not installed" message:

but no longer shows as available in MAS:

Version has updated in About This Mac (ATM):

System Report details:
before:

after:

and finally, nothing shows as installed except the Safari update I did just before Sec Update:

 

[ScooterComputer]

I tried removing (deleting) the Recovery partition back when attempting to get Security Update 2018-002 to install.
Didn't change a thing, still failed with the same error message.

OF COURSE, Apple. Sheesh.

Thanks for replying @jbarley.

 

[mrploppy]

I've always been fed up of getting the "An error occurred while running scripts from the package “XXXX.RecoveryHDUpdate.pkg”, so I followed my own suggestion of doctoring the script(s) so that at least the installation could run to completion and thereby show up in the install.log.

So, basically I followed the instructions in the OP for installing Security Updates. Downloaded the update manually. Added my board id and removed my model number as instructed. I also modified the replaceRecovery bash script - which is the one that fails (at the hdutil attach command). I commented out everything between creating and deleting the temporary mount point (which it creates in /var/folders). I know I could have commented out everything but I decided to only comment out the part that was causing the failure. I also edited the echo command so that I knew it was running my modified script. Repackaged per the instructions.

Suffice to say, the update ran to completion (no error report) and I got the Installation Successful dialog. About This Mac now reports build 17G4015. The security update also shows in the Installations list in System Report. The App Store doesn't show the security update as recently installed, but it also doesn't show the update as available anymore.

The other thing I did (and I don't know if this was strictly necessary) was to mount the Recovery partition and manually modify the System Version therein to say 17G4015.

No problems so far. I haven't tried booting into the Recovery partition yet but don't anticipate any problems.