Again, we know this further up the thread, but other users are still SOL.If your system came with Sierra, use the recovery mode to get Sierra again.
Again, we know this further up the thread, but other users are still SOL.If your system came with Sierra, use the recovery mode to get Sierra again.
Avid Media Composer 8.9 is not compatible with High Sierra yet, so not finding Sierra on the App Store was bad news... Thank you so much jasminetroll, 'mas install 1127487414' saved my day.
It wasn't working with my main Apple ID with which I downloaded Sierra a while ago but it worked with a client's ID with which I recently downloaded Sierra.
Sierra was not showing in the App Store but to my surprise 'mas install 1127487414' triggered the download!
Easy. You just quit it by cancelling the update (or just acknowledging that, yes, it is incompatible, *after* the download finishes). It's not like it will delete itself, it only does that if you are upgrading and follow through with the installation process (and that's why you should either/both create a bootable installer – see below – or/and back up the installer app itself before performing the upgrade).And how does one then quit the installer after it's downloaded, and then use it on another machine/VM?
If your internet is down, can’t do that. I know about internet recovery. That wasn’t the point.If your system came with Sierra, use the recovery mode to get Sierra again.
If your internet is down, can’t do that. I know about internet recovery. That wasn’t the point.
A week before High Sierra was released, I downloaded a Sierra installer which was created on 2017-07-14. This seems to be the installer for the last version of Sierra, 10.12.6. Aside from doing another install, how do I confirm the version it will install? Will this installer stop working after a certain period of time?Of course, how long that (or any) downloaded version will work to do a new Sierra install, is anyone's guess, due to the certificates problem.
So the issue of getting a fresh Mac App Store download of the Sierra installer, remains.
Good question.A week before High Sierra was released, I downloaded a Sierra installer which was created on 2017-07-14. This seems to be the installer for the last version of Sierra, 10.12.6. Aside from doing another install, how do I confirm the version it will install? Will this installer stop working after a certain period of time?
I also used the link in Post #155 to successfully install Sierra. I installed it on a MacBook Pro (13-inch, Mid 2012). In "System Preferences > Security & Privacy > General > Allow apps downloaded from", I did have to select "Anywhere" before it would install, though.
Everything seems to be working OK. Thanks, folks, especially to Mr_Brightside_@, jimthing, and Bob-K.
I was a little nervous about not downloading it directly from the Mac App Store, so I did make an attempt to verify it using the procedures I found here in an article entitled "Verifying that you’ve downloaded genuine Apple software."
The first part all checked out regarding the checks on the installer's digital signature, but when I went to verify that the signature isn’t broken, I got the result that the "resource envelope is obsolete (custom omit rules)". Not sure what that means. Any ideas? Is this cause for concern?
I also verified that the SHA1 checksum for the installer (InstallESD.dmg) matched the value listed here.
I had intended to check the download using the procedure here, but for some reason the installer was an .app instead of a .pkg. When I double-clicked the installer, it just started the installation instead of opening an installer window.
Finally, I see that the link in question keeps getting deleted from the original thread that was linked to in Post #155 for some reason...
Whether it will work for a set period of time, I cannot answer. To get the version it will install, you need something like Pacifist, which will open up a .dmg file. Right click on the installer.app, Show Package Contents, browse to /Contents/SharedSupport/InstallESD.dmg. Right click on that file to open it in Pacifist, then browse the contents to /System/Library/CoreServices/SystemVersion.plist, and that file will list the version number it will install. You can also find your current version at any time (other methods are easier), by reading /System/Library/CoreServices/SystemVersion.plist.Good question.
Aside from doing another install, how do I confirm the version it will install?
HA! I've still got disk images for Snow Leopard and Tiger!
All good to know, but how is that different to simply doing this?:Whether it will work for a set period of time, I cannot answer. To get the version it will install, you need something like Pacifist, which will open up a .dmg file. Right click on the installer.app, Show Package Contents, browse to /Contents/SharedSupport/InstallESD.dmg. Right click on that file to open it in Pacifist, then browse the contents to /System/Library/CoreServices/SystemVersion.plist, and that file will list the version number it will install. You can also find your current version at any time (other methods are easier), by reading /System/Library/CoreServices/SystemVersion.plist.
________When I click on the installer app in the Finder (in column view) (or do "get info"), it says "Version: 12.6.03"
I guessed that this meant it would install 10.12.6, and that was the case.
That command didn't work for me for some reason, I have the Sierra installer.app on my Desktop, and got the following:Thx for the instructions to determine the target OS version of the Sierra installer. Yesterday I confirmed
the installer created on 2017-07-14 does indeed install 10.12.6.
The 12.6.03 in the installer Get Info window is the PackageVersion found in com.apple.pkg.InstallOS.plist (which, as suggested, is related to 10.12.6).
As far as the signing certificate, from Terminal, execute the following:
pkgutil --check-signature path/to/Install\ macOS\ Sierra.app/Contents/SharedSupport/InstallESD.dmg
This will display the status of the installer's certificate but does not indicate an expiry date.
[doublepost=1507579021][/doublepost]Here's an example output:
Package "InstallESD.dmg":
Status: signed by Apple
Certificate Chain:
1. Apple Mac OS Installer Package Signing
SHA1 fingerprint: 06 BD 50 40 07 CC 4B 3B BF 77 7E CF E9 22 3B ED 55 4B 22 76
-----------------------------------------------------------------------------
2. Apple Worldwide Developer Relations Certification Authority
SHA1 fingerprint: FF 67 97 79 3A 3C D7 98 DC 5B 2A BE F5 6F 73 ED C9 F8 3A 64
-----------------------------------------------------------------------------
3. Apple Root CA
SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60
jimthing, sorry, in the above path, you'll have to replace path/to with ~/Desktop. So something like:
pkgutil --check-signature ~/Desktop/Install\ macOS\ Sierra.app/Contents/SharedSupport/InstallESD.dmg
Thanks. Though I presume this means that the expiry date is thus seemingly at the whim of Apple, whenever they decide to stop signing that particular version; goodbye to any of us using it then?Package "InstallESD.dmg":
Status: signed by Apple
Certificate Chain:
1. Apple Mac OS Installer Package Signing
SHA1 fingerprint: 06 BD 50 40 07 CC 4B 3B BF 77 7E CF E9 22 3B ED 55 4B 22 76
-----------------------------------------------------------------------------
2. Apple Worldwide Developer Relations Certification Authority
SHA1 fingerprint: FF 67 97 79 3A 3C D7 98 DC 5B 2A BE F5 6F 73 ED C9 F8 3A 64
-----------------------------------------------------------------------------
3. Apple Root CA
SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60
No idea, sorry. :-|When the certificate attached to an installer has expired, the installer will display a warning. Note the option, Show Certificate:
https://derflounder.wordpress.com/2...tion-and-downloaded-mac-app-store-installers/
This will show the certificate's expiry date. So if we set the system date to 2030-01-01 and force this error on the Sierra installer, maybe the expiry date can be exposed?
Nice work. Good question, too. How anyone would find that out, is anyone's guess...?I tried fooling the installer with a 2030-01-01 system date and unfortunately it would only return a generic error message "... application is damaged, and can't be used to install macOS." There was no expiry warning with an option to Show Certificate. So through trial and error I nailed the expiry date to 2019-10-24. I'm unsure if this date is somehow related to the date I downloaded the installer, 2017-09-14. I'd be curious to know if other installers share the same expiry date or not.
YepAll good to know, but how is that different to simply doing this?:
That does not show the subversion, or "build" number. Apple occasionally releases updates to a "release", with a slightly upgraded build version. So, 10.12.3 build 16D32, or build 16D35?
/System/Library/CoreServices/SystemVersion.plist does show you the build version.
________
Anyway the more important question remains: how does one know if the certificate is still valid?
I'm not sure of the answer to this. All of my saved installers from Snow Leopard up to Yosemite were made invalid by an expired certificate.
Seemingly you can't find this out? (until you try and run the installer app, and it doesn't work, of course!)
Lucky I downloaded the Sierra 10.12.6 installer last week.
Would you be open to sharing?Sure it's possible. But why make it harder than it was last week?