No Packages Were Eligible For Install Os X

Posted on by admin

When the OS X installer complains that 'No packages were eligible for install' and displays this window: don't restart your Mac. Turn Wi-Fi off or unplug the Ethernet cord, depending on your configuration, to prevent your Mac from connecting to the Internet. Please watch version 2 of this video here: the 'install failed' and 'No packages were eligible for install'.

When you’re booting your Mac from the recovery partition and are planning to reinstall OS X, you might be met by the following message:

An error occurred while preparing the installation. Try running again

Now, if you haven’t used your Mac for a while, the error might be caused by an incorrect system date setting. You can check this by going to utilities and opening the terminal. Once in the terminal enter the following command and hit return/enter:

The result of this command will be the date that the system currently has been set to. For some reason, it might have been reset to 2001, in which case we need to set it to the right date. To do this, we enter a new command. This command will be entered as follows:

Every bracket should be replaced with a two-digit number based on UTC time. Below you see what the command should be for your current time and date – . To avoid trouble with timezones, we will use UTC time instead (). Which means, you can just enter it exactly like this:

Enter the command and hit return. You can then check if it was set correctly by running the first command again. If the date was wrong, it was likely that which caused the error, and after you quit the terminal it should be able to install OS X just fine.

Buying a Tesla? Use my referral link at the purchase of your new Model 3, S or X and get 1500km / 1000mi of free supercharging!Get free supercharging

Related

ACF lazy load Select options

Advanced Custom Fields is used a lot by WordPress developers, and it comes with a lot of handy fields. It's also very developer friendly, for example giving the ability to populate a select field through filters. But in some cases you may have a crazy amount of options/choices to populate…

No Packages Were Eligible For Install Os X

Serving WordPress with Caddy 2

I've been using Nginx for about a decade, and beyond using Varnish every now and then I haven't really had the need to use anything else. Well, recently I started trying out Caddy – in fact, this site is served using Caddy. Would you consider trying Caddy or just stick…

Tibber – the Electric power company for the future

Electric power companies, in general, are pretty much the same. Tibber however, is unlike any electricity company I had seen before. They try to utilise the data we get from smart devices, which they also sell, to save electricity, money and the environment, as well as improving comfort. It’s a…

When trying to upgrade from OS X 10.6.8 Snow Leopard to OS X 10.11.6 El Capitan, I repeatedly encountered a frustrating 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.'
What does no packages were eligible for install mean

My end goal was to install macOS 10.13 High Sierra. I read online that one must upgrade to OS X 10.11 before upgrading to macOS 10.13 if one is starting from OS X 10.6. This upgrade route did not work for me no matter how many solutions I attempted. I eventually found a solution to this frustrating problem which I'll share below, but before I do that, I'd like to share what did NOT work for me to hopefully help others avoid unnecessary frustration and wasted time:
Solution attempts that did NOT work for me:
I tried changing the time to the correct present time and to a past time when the installer certificates may have still been valid (mid-2016). The upgrade problem persisted either way.
Manually setting the date and time via the Terminal (see above link) to an earlier date is worth trying because it has worked for some people. Try this time: 1010101015
2) Erasing my internal hard drive using Disk Utility in Internet Recovery Mode
All this did was remove my data, but the persistent 'OS X could not be installed...' problem remained.
3) Booting from an external hard drive that was formatted to act as an installer for OS X 10.11

No Packages Were Eligible For Install Os X 10 12

4) Booting in the Internet Recovery Mode option to install the version closest to the operating system that came with my Mac (Shift+Option+Command+R).
My Mac came with Snow Leopard, which is not available to download, so it attempted to install Lion, but wasn't able to do so because I had not purchased it with my Apple ID.
Here's the upgrade route that DID work for me:
1) I purchased OS X 10.7 Lion with my Apple ID and downloaded it via the Mac App Store on another Mac (so it would be in my App Store download history)
Were
2) I booted in the Internet Recovery Mode option to install the version closest to the operating system that came with my Mac by holding down Shift+Option+Command+R while my MacBook was restarting.
3) I selected 'Reinstall Mac OS X' in the 'Mac OS X Utilities' window that appeared when Internet Recovery Mode fully booted up.
4) When prompted, I entered my Apple ID information that was used to purchase and download OS X 10.7 Lion and allowed the OS X upgrade to proceed to completion. I then had a fresh version of OS X 10.7 Lion installed on my Mac.
5) The next step was to upgrade from OS X 10.7 Lion to macOS 10.12 Sierra using these steps.
6) Once macOS 10.12 Sierra was fully installed, I upgraded to macOS 10.13 High Sierra using these steps.
Install
My MacBook Pro is now successfully running macOS 10.13.6 High Sierra.

No Packages Were Eligible For Install Os X 10 11

Install
Basically, what worked for me was circumnavigating the suggested route of installing OS X 10.11 before installing macOS 10.13. Instead, I followed this upgrade route: 10.6 to 10.7, then 10.12 to 10.13.

No Packages Were Eligible For Install Os X Without

I thought it may be helpful to share what worked for me in case someone else out there is trying to upgrade from OS X 10.6 Snow Leopard to macOS 10.13 High Sierra and encountering the issue I encountered. Please feel free to ask me any questions about this and I will do my best to help.