These advanced steps are primarily for system administrators and others who are familiar with the command line. You don't need a bootable installer to upgrade macOS or reinstall macOS, but it can be useful when you want to install on multiple computers without downloading the installer each time.
Mac OS X 10.5 or earlier. Please remove the.pkg files related to that application on the following location: System volume/Library/Receipts; Mac OS X 10.6 or later. The receipts don't exist anymore, instead something like the receipts are stored in another place. This is how you can make them visible: Open Terminal.app (found in /Applications. Free to try Koingo Software Mac OS X 10.6/10.7/10.8 Version 1.4.3 Full Specs. Editors' Rating. Amnesia, at $19.95, is the most expensive of these dedicated app 'uninstallers'. So what does it. It should be as easy as dragging and dropping to the Trash. But uninstalling Mac apps is rarely that easy. That's why there are uninstaller utilities, which claim to get rid of every last vestige.
Download macOS
Find the appropriate download link in the upgrade instructions for each macOS version:
macOS Catalina, macOS Mojave, ormacOS High Sierra
Installers for each of these macOS versions download directly to your Applications folder as an app named Install macOS Catalina, Install macOS Mojave, or Install macOS High Sierra. If the installer opens after downloading, quit it without continuing installation. Important: To get the correct installer, download from a Mac that is using macOS Sierra 10.12.5 or later, or El Capitan 10.11.6. Enterprise administrators, please download from Apple, not a locally hosted software-update server.
Installers for each of these macOS versions download directly to your Applications folder as an app named Install macOS Catalina, Install macOS Mojave, or Install macOS High Sierra. If the installer opens after downloading, quit it without continuing installation. Important: To get the correct installer, download from a Mac that is using macOS Sierra 10.12.5 or later, or El Capitan 10.11.6. Enterprise administrators, please download from Apple, not a locally hosted software-update server.
OS X El Capitan
El Capitan downloads as a disk image. On a Mac that is compatible with El Capitan, open the disk image and run the installer within, named InstallMacOSX.pkg. It installs an app named Install OS X El Capitan into your Applications folder. You will create the bootable installer from this app, not from the disk image or .pkg installer.
El Capitan downloads as a disk image. On a Mac that is compatible with El Capitan, open the disk image and run the installer within, named InstallMacOSX.pkg. It installs an app named Install OS X El Capitan into your Applications folder. You will create the bootable installer from this app, not from the disk image or .pkg installer.
Use the 'createinstallmedia' command in Terminal
- Connect the USB flash drive or other volume that you're using for the bootable installer. Make sure that it has at least 12GB of available storage and is formatted as Mac OS Extended.
- Open Terminal, which is in the Utilities folder of your Applications folder.
- Type or paste one of the following commands in Terminal. These assume that the installer is still in your Applications folder, and MyVolume is the name of the USB flash drive or other volume you're using. If it has a different name, replace
MyVolume
in these commands with the name of your volume.
Catalina:*
Mojave:*
High Sierra:*
El Capitan: - Press Return after typing the command.
- When prompted, type your administrator password and press Return again. Terminal doesn't show any characters as you type your password.
- When prompted, type
Y
to confirm that you want to erase the volume, then press Return. Terminal shows the progress as the bootable installer is created. - When Terminal says that it's done, the volume will have the same name as the installer you downloaded, such as Install macOS Catalina. You can now quit Terminal and eject the volume.
* If your Mac is using macOS Sierra or earlier, include the
--applicationpath
argument, similar to the way this argument is used in the command for El Capitan.Use the bootable installer
After creating the bootable installer, follow these steps to use it:
- Plug the bootable installer into a compatible Mac.
- Use Startup Manager or Startup Disk preferences to select the bootable installer as the startup disk, then start up from it. Your Mac will start up to macOS Recovery.
Learn about selecting a startup disk, including what to do if your Mac doesn't start up from it. - Choose your language, if prompted.
- A bootable installer doesn't download macOS from the Internet, but it does require the Internet to get information specific to your Mac model, such as firmware updates. If you need to connect to a Wi-Fi network, use the Wi-Fi menu in the menu bar.
- Select Install macOS (or Install OS X) from the Utilities window, then click Continue and follow the onscreen instructions.
Learn more
For more information about the
createinstallmedia
command and the arguments that you can use with it, make sure that the macOS installer is in your Applications folder, then enter this path in Terminal:Catalina:
Mojave:
High Sierra:
El Capitan:
InstallAnywhere 2017
Edition • Authentication support is available in the Premier edition of InstallAnywhere.
InstallAnywhere has support for signing macOS or OS X–based installers with a Developer ID Application certificate at build time. Signing an installer with this type of certificate enables you to distribute it outside the Mac App Store. When an end user downloads and runs your installer, Gatekeeper allows the installer to run.
![Uninstallers For Mac Os X Uninstallers For Mac Os X](/uploads/1/1/8/8/118892981/737139388.jpg)
If an end user tries to launch an unsigned, downloaded installer on an OS X Mountain Lion or later (including macOS) system on which Gatekeeper is turned on, the system displays an alert and blocks the installer from running.
If you want your macOS or OS X–based installers and uninstallers to install files to and remove files from locations where write permissions are restricted for standard users, you can configure your project to require authentication. When authentication is required and standard users who are not root users or administrative users with adequate privileges try to launch your installer or uninstaller, they are prompted to enter an administrator name and password in order to proceed.
If your installer and uninstaller installs files to and removes files from unrestricted locations such as the user’s home directory, authentication is not required on macOS or OS X–based target systems.
Note that in order to require authentication for macOS or OS X–based installers and uninstallers, they must be code signed.
Run-Time Behavior for a Code-Signed Installer that Includes Authentication Support
An installer that includes authentication support consists of the following primary files:
• | An authentication wrapper |
• | A helper tool-the file that is used to launch the installer or uninstaller with elevated privileges |
• | The installer application-that is, the Java installer |
• | Optionally, the uninstaller application. Note that InstallAnywhere generates the uninstaller and bundles it into the installer at build time. |
The authentication wrapper, helper tool, installer, and uninstaller must all be code signed with the same Developer ID Application certificate.
At run time on target systems, the following process occurs for a properly code-signed installer or uninstaller that includes authentication support:
1. | The end user launch the authentication wrapper on a macOS or OS X–based system. |
2. | The authentication wrapper prompts for elevation (if needed for a standard user) and installs the helper tool with root privileges. |
3. | The authentication wrapper requests that the helper tool launch the LaunchAnywhere. |
![For For](https://pxhst.co/avaxhome/4a/25/0031254a_medium.jpeg)
4. | The helper tool launches the LaunchAnywhere, which inherits the elevated privileges from the helper tool. |
5. | The LaunchAnywhere launches the installer or uninstaller, which inherits the elevated privileges. |
At the end of the installation or uninstallation, the authentication wrapper shuts down the helper tool and uninstalls it. If any part of the process is not signed with a matching Developer ID Application certificate, the process fails.
Overview of the Process of Code Signing Installers and Including Authentication Support
Preparing Your Machines
The following steps outline the process of preparing your machines to build and code sign installers with authentication support.
Appcleaner For Mac Os X 10.5 8
1. | Determine whether you will be performing the code-signing step at build time on your InstallAnywhere build machine, or on a designated code-signing machine. To learn more, see Code-Signing Methods for macOS or OS X–Based Installers. |
2. | Ensure that your build and code-signing machines meet the requirements for code-signing support. To learn more, see Requirements for Code-Signing Support for macOS or OS X–Based Installers. |
3. | If you have not already done so, obtain your Developer ID Application certificate. To learn more, see Obtaining a Developer ID Application Certificate for Code Signing macOS or OS X–Based Installers. |
4. | Prepare your code-signing machine. This involves importing your Developer ID Application certificate, ensuring that the latest Xcode IDE and its default SDKs are present, building and code signing the helper tool, verifying the code-signed helper tool, and copying the code-signed helper to all of your InstallAnywhere build machines. To learn more, see Adding the Code-Signing Capability to Your InstallAnywhere Build Machines or Code-Signing Machines. |
Configuring Your InstallAnywhere Projects
Once you have competed the aforementioned preparation steps, perform the following steps for generating code-signed installers with authentication support:
1. | Configure your projects for code signing and authentication. To learn more, see Code Signing Your macOS or OS X–Based Installers and Including Authentication Support. |
Uninstaller For Mac Os X
2. | Verify that the resulting installers were successfully code signed. To learn more, see Verifying that Your Code-Signing Output Files Are Working as Expected on macOS or OS X–Based Target Systems. |
See Also
InstallAnywhere 2017 Help LibraryNovember 2016 | Copyright Information | Flexera Software |