Sierra is the latest version of macOS (at time of. Once you are there, you can go through the new settings and enable the ones that make sense to you.You can do this, for example, via a Time Machine or another external hard drive. The latest version of macOS Sierra has a new tool to help you clean the junk out of your Mac just go to the menu and choose About This Mac and then flip over to the Storage tab. Use the Storage Tools in macOS High Sierra.Step 4 Clean install macOS. Step 3: Erase the non-startup drive. Step 2: Download macOS High Sierra installer. Smart displays, iOS 12.5.5 and Catalina security update, iPhone 13 problem with Apple Watch unlockingMac High Sierra Cache Cleaner Mac High Sierra Part 3: Clean Install macOS High Sierra Without USB Step 1: Backup your Mac.
![]() (Did you know that different versions of Command-R cause different versions of macOS to be installed by macOS Recovery? Check out this Apple support article for the details.) Afterward, everything was fine, so I chalked it up to gremlins and started writing this article, but got sidetracked by work on our Internet infrastructure.A few days later, however, my MacBook Air was performing badly, so I decided to restart it as well. I looked through the log and saved a copy, but none of the errors looked all that problematic.With seemingly no other recourse, I clicked Restart one last time, held down Command-Option-R to boot into macOS Recovery, and reinstalled the operating system. Instead of booting normally, I ended up at a screen containing only an Installation Log window and an error dialog saying “The macOS installation couldn’t be completed.” That was confusing since I hadn’t asked the App Store app to install macOS 10.13.4.However, clicking the Restart button just brought up the screen and error dialog again. It was the same Installation Log screen and error as I’d seen on both my Macs.Luckily, the trick I’d employed to get my MacBook Air to boot worked well for him too — it’s always nice when we aged parents get to show off our technical prowess. When I looked, I couldn’t believe my eyes. This never happens — like many people of his generation, Tristan is categorically allergic to the telephone — but I hadn’t responded to a picture of his MacBook Pro that he’d sent me in Slack. If that doesn’t work, boot into macOS Recovery and reinstall the operating system. Restarting doesn’t help, but the first thing to try is holding down Option as the Mac boots and selecting the primary drive. Upon restart — without the user asking to install 10.13.4 — the Mac boots into the Installation Log app and shows an error saying the macOS installation couldn’t be completed. In three separate instances, a Mac that’s running macOS 10.13.3 starts running slowly. He said that it had been running very slowly before that too.So let’s recap. In fact, his MacBook Pro had restarted only because he had plugged it back in after it had run out of power and shut down. Disk Cleaner Sierra Mac Os X InstallFor example, if the installer finds what it considers a viable system on your target partition, it will not install anything older to that partition.There have even been circumstances in the past where a supplemental security update could supersede the latest OS installer version and render the built-in system installer absolutely useless. There’s also a chance that a “mac os x install data” folder at the root level of the target partition could be errantly left behind during an installation and require certain some specific actions to get things working correctly again.I think the Apple HT204904 article has some information about startup key combinations for reinstalling MacOS that are simplified to the extent of causing confusion. It might not even be connected to macOS 10.13.4 — perhaps the “macOS installation” that’s failing is related to the “Install system data files and security updates” checkbox, which should always remain selected (see “ Make Sure You’re Getting OS X Security Data,” 30 March 2016).If you have any insight into this problem, let us know in the comments.Did anyone experiencing the problem try the four-finger salute to reset NVRAM (hold command-option-P-R and wait for 2 or 3 additional startup chimes)? I’m pretty sure that some of these issues can be avoided by using the High Sierra 10.13.4 Combo Update, which can under most circumstances be applied to a qualifying target partition even while booted from another qualifying partition. Perhaps it’s related to the “Download newly available updates in the background” checkbox in System Preferences > App Store, although that was set differently on my two Macs. But if you’ve been holding off upgrading, which is usually the cautious thing to do, be aware that it’s possible you might encounter this situation on your next restart.I have little idea of what could be going on under the hood. If you’ve already upgraded to macOS 10.13.4, you’re probably safe. I looked through the log and couldn’t see anything that seemed suspicious, but I’m pretty minor league on reading logs. As often happens something hangs and I reboot, but this time I ended up at the same screen you saw. Also (correct me if I’m wrong), although you can nondestructively convert an HFS+ volume to APFS, you can’t nondestructively perform the action in a reverse manner, that is, convert an APFS volume to HFS+.I’ve had to go into safe boot lately to do OS upgrades and Friday (the 13th) I decided to go for. Clear recent list in excel for macIt was odd, it should have told me I can’t use DU from a hard drive on an SSD formatted with APFS. If I’d only waited a couple of days or had read my saved notes on recovery.The other problem I ran into is that I booted my MBP 2013 off another drive and tried Disk Utility and it would only do a quick check (took only a few seconds to check the drive compared to the normal minute or two) which seemed odd. Forgot about Cmd-R mode and spent $75 at the local computer store to find out about my ignorance. I had installed the Security Update 2018-003 10.13.6. Only one startup.You can add the DU misinformation to your list of Mac irritants.Well it’s happening to me suddenly too, on my iMac Pro running 10.3.6. 4 upgrade and since I took it in this morning and picked it up an hour ago I can’t say everything is fine. Reinstalling did work, but it has continued to happen. Before doing so I did try to reset NVRAM and the SMC, and ran Disk First Aid, scanned with ClamXAV and Malwarebytes, and everything else I could think of. Finally, like others, I opted to reinstall the system. I restarted 3 times and got the log all three times. I got the aforementioned Log and message that the installation couldn’t be completed. It may be an intermittent problem with the power brick and a replacement has been ordered.However, after this, I noticed general sluggish behavior of the Mac and decided to restart.
0 Comments
Leave a Reply. |
AuthorDavid ArchivesCategories |