“No packages were eligible for install” is a message that appears when attempting to install OS X El Capitan on older macs. MacBooks are a very popular purchase in Melbourne and around Australia so it is important to understand the reasoning behind why this message appears. Simply put, if your Mac isn’t old enough to run the latest El Capitan operating system then it won’t install. Right now (2016), the newest iteration of OS X is 10.11, known as macOS Sierra. In this guide, we’ll show you how to install macOS Sierra on your PC with the newly released Hackintosh Sierra Installer. Read this article completely once before beginning any procedures. Most of the troubleshooting information is included in this article. Connect to a wifi or plug in ethernet and download os x (second option I believe.) It will download and then try to install itself and then fail with no packages were eligible message with option to restart. Shut off wifi (top right) or unplug ethernet cord go to utilities -terminal- type this and only this, date. Before you try to install a new version of macOS. It’s essential that before you perform any major upgrade, say from Catalina to Big Sur, that you backup your Mac. One of the steps described below involves a complete reinstall of the operating system, resulting in erasing data from your drive.
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
Oh dear… When trying to install OS X 10.11 (El Capitan) you may encounter this message. This happens because the the installer certificates are no longer valid when checked against the clock of your mac.
Don’t panic though as this is easily fixed using Terminal, so don’t restart immediately.
No Packages Were Eligible For Install Os X 2017
- Click Utilities on the menu bar
- Select Terminal
- Type date 062112422016
- Exit Terminal
- Click Restart
No Packages Were Eligible For Install Os X Version
When you restart the mac and try the installer again it will now believe the certificates are valid and will continue as it should.