Os X Could Not Be Installed No Packages

Macos Could Not Be Installed
Mac Os Cannot Be Installed
Os X Could Not Be Installed No Packages Were Eligible For Install

Jul 26, 2019 There are a number of things you can do to fix your Mac when you see the message: “macOS could not be installed on your computer.” If the problem is that you don’t have enough space, you can use CleanMyMac X to get rid of files you don’t need. Otherwise, go through the above steps one at a time until you’re able to install a new. Now pages says it has a new update but I can’t install it because a notice advised that it can’t be updated since the previous version was installed with a different Apple ID. I may have made a mistake in keying in my Apple ID pages update App Store request but there is no way for me to go back to request and see if I made a mistake.

Here in Belgium schools are locked down due to #coronavirus. With the school of my two oldest kids now switching to remote teaching, I took the time to set up my old MacBook Pro (model late 2008) for my two oldest kids to use. That didn’t go without any hiccups though: the OS X installer refused to install …

The MacBook I had shelved a long time ago was still running OS X Mavericks. As that version was quite showing its age – and didn’t seem to support 2FA for use with my Apple ID – I decided to upgrade it to El Capitan, of which I still had the installer app lying around. I opened up the installer, it prepared some things, and nicely asked to reboot. Upon reboot the installer was ready to install, but when actually starting it greeted me with this error message:

OS X could not be installed on your computer.

No packages were eligible for install. Contact the software manufacturer for assistance. Quit the installer to restart your computer and try again.

Uhoh! Restarting the MacBook, as suggested, did nothing: the installer kept showing that same error message. Trying to change the startup disk to get back into Mavericks (by pressing ⌥+R upon starting the machine) also didn’t help, as I could only launch the installer and a recovery partition. Yes, the machine was actually stuck in a loop where it would only launch the installer and the installer wouldn’t install.

How to fix no packages were eligible for install

With a Google Search Coupon in hand I found that the installer refuses service because the certificate it was signed with (some time back in 2015, when El Capitan was released) got expired by now.

Thankfully one can easily circumvent this expiration by simply changing the date of your system. You can do this before starting the installer, or through a Terminal if the installer is already loaded (as it was in my case).

In the OS X Installer, choose Utilities > Terminal.
Enter date 020101012016 and press Enter.
Quit Terminal and reboot to retry the installation.

💡 In this particular Terminal you’re running as root, so no need for sudo here 😉

Here the date is being set to Feb 1st, 2016. You might need to tweak the date a bit depending on when you downloaded the installer originally (as it might be signed with a different certificate). Be sure to set it no earlier than the release date of the OS X version you’re trying to install.

💡 The syntax for the date command is a bit counterintuitive. Choosing your own date will require some puzzling from your end:

Later versions of OS X, such as High Sierra, have become a bit smarter: they give you the warning upfront – when first launching the Installer.app – instead of after having prepared your disk for installation.

Macos Could Not Be Installed

Os x could not be installed no packages were eligible for install

Did this help you out? Like what you see?
Thank me with a coffee.

Mac Os Cannot Be Installed

I don't do this for profit but a small one-time donation would surely put a smile on my face. Thanks!