For example, "Install macOS High Sierra.app" would become Install\ macOS\ High\ Sierra.app Be aware that any spaces will need to be preceded by a backslash. You can change various parts of this command to suit your own circumstances, with the main one being the name of the installer. Sudo /Applications/ Install\ macOS\ Big\ Sur.app/ Contents/Resources/createinstallmedia -volume /Volumes/macos_installer You can find out which Mac you have by clicking on the Apple logo in the top-left corner and selecting "About This Mac" to see the name and year of release. If you're not sure what your Mac came with, head to Apple Support and search for your exact model. Your Mac's "earliest" supported version of macOS is the one that it came with. Older versions were written for Intel chips, which use the x86_64 instruction set, while the newer Apple Silicon chips use the ARM instruction set. It's common knowledge that new macOS releases often drop support for older hardware, but the same is true for newer Mac models and older software, too.įor example, you cannot install any version of macOS prior to Big Sur (released in 2020) on a Mac with an Apple Silicon chip, including the M1. It's important to understand that not all versions of macOS (or Mac OS X) work with all hardware configurations. And it's true for both of my Macs running OS 10.14.6.While the process is pretty straightforward, getting your hands on older releases of macOS isn't so easy. I still don't understand, though, why I cannot get this installer file directly from the App Store, like I've ALWAYS been able to do. I'm hoping that works (I expect it to).Īppreciate your assistance. I'm going to do a fresh, clean installation of OS 10.15.1, using that installer file, onto my external Samsung 860 EVO 500 gig SSD, and then will migrate/copy needed files, folders, settings, etc. In this case, it was in my downloads folder. I guess the only other "surprise" is that previously, whenever one downloaded the full OS version, that installation file would wind up inside the Applications folder. It downloaded Catalina V10.15.1.03, which is (I'm assuming) the most recent, stable, non-beta version. Given that it was a "patcher", I was definitely reluctant to double click on the resulting file. Initially, after downloading the "patcher", there were no instructions on what to do next. I'll see what it says.Ĭlick to expand.OK, that was helpful. I can try it with my external SSD which I have OS 10.15.1 installed on. Use with -background to trigger a background scan regardless of "Automatically check" pref products A comma-separated (no spaces) list of product keys to operate on. product-types Limit a scan to a particular product type only - ignoring all othersĮx: -product-types macOS || -product-types macOS,Safari no-scan Do not scan when listing or installing updates (use available updates previously scanned) all Include all processes in history (including App installs) By default, only displays updates installed by softwareupdate. evaluate-products Evaluate a list of product keys specified by the -products option dump-state Log the internal state of the SU daemon to /var/log/install.log background Trigger a background scan and update operation r | -recommended Only recommended updates R | -restart Automatically restart (or shut down) if required to complete installation. l | -list List all appropriate update labels (options: -no-scan, -product-types) Softwareupdate: unrecognized option `-full-installer-version' Softwareupdate: unrecognized option `-fetch-full-installer' "softwareupdate -fetch-full-installer -full-installer-version 10.15.1 I just tried on my Mac Mini (am entering this post on it) running the latest version of Mojave, and here is what I got: Click to expand.I believe that "new" softwareupdate command works only with the Catalina version of Terminal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |