Upgrading to El Capitan with an old installer
I upgrade my Macbook to El Capitan as soon as I could, and have had very few issues with the release. On my iMac at work though, I’ve been putting off the upgrade since last October – due to time constraints and not wanting to mess anything in my dev environment up.
Today I tried to install El Capitan using the Install OS X El Capitan.app installer.

I was greeted with this message. How could this be? The installer has simply been sat in my Applications directory since October, nothing has changed.
I used the following command to verify the integrity of the installer image:
hdiutil verify /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg
Which told me the image is VALID. Alright, so there must be another cause?
Well I downloaded the installer in October 2015; In February 2016 Apple’s Signing Certificate expired. I actually encountered this issue when doing a fresh install of El Capitan on another Macbook earlier this year, the solution is simple: change the system date to earlier than February 2016.
date 1021120015
That command changes the date to October 21st 2015 at 12:00.
Alternatively you can use the Date & Time System Preferences pane:

Now you can run the installer without issue.
After OS X El Capitan has installed, it will set the date and time back to their correct values.
Now, rather than having to re-download a 7GB installer image, I just have to download a 2GB update!
Related posts
- Making GIMP feel less like punishment
GIMP has always had an interface problem. I’m not blaming the GIMP team (they’ve built something powerful on a shoestring). They’ve been clear they’re not interested in copying Photoshop wholesale; their FAQ argues that designing around actual user research beats imitating someone else’s interface decisions. Fair enough in principle, but coming from years as a Photoshop user, that design still feels hostile to me. I’m just one user story out of many they’ve had to design for, but it still expects me to learn its own way of doing things rather than offering a config closer to what I’m used to out of the box.
- Replacing the macOS audio switcher with SwiftBar
The built-in audio output menu in macOS has always felt a bit limited. The icons aren’t very helpful, the device names can’t be customised, and if you’ve got a few different outputs, it becomes tricky to quickly tell what’s what.
- Installing Chrome OS on a Late 2009 MacBook
I’ve got an old 2009 MacBook 6,1 (A1342) kicking about in my office that I’ve been playing with on and off lately.
Discussion
No interactions yet
Join the conversation
Reply from your own site with a Webmention (how?).
