Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
Desktops (Apple) Bug Operating Systems Apple IT Technology

Users Complain About Installation Issues With macOS 10.13.4 (theregister.co.uk) 90

An anonymous reader shares a report: The 10.13.4 update for macOS High Sierra is recommended for all users, and was emitted at the end of March promising to "improve stability, performance, and security of your Mac." But geek support sites have started filling up with people complaining that it had the opposite effect: killing their computer with messages that "the macOS installation couldn't be completed."

The initial install appears to be working fine, but when users go to shutdown or reboot an upgraded system, it goes into recovery mode. According to numerous reports, there doesn't appear to be anything wrong with users' Macs -- internal drives report that they're fine. And the issue is affecting a range of different Apple-branded computers from different years. Some have been successful in getting 10.13.4 to install by launching from Safe Mode, but others haven't and are deciding to roll back and stick with 10.13.3 until Apple puts out a new update that will fix whatever the issue is while claiming it has nothing to do with it.

This discussion has been archived. No new comments can be posted.

Users Complain About Installation Issues With macOS 10.13.4

Comments Filter:
  • by bobstreo ( 1320787 ) on Friday April 20, 2018 @05:30PM (#56474195)

    It's always best to let other people be the guinea pigs/beta testers.

      Unless it fixes something that is broken that matter to you.

    • by Anonymous Coward

      I do that, I waited over 6 months I think before installing High Sierra (just installed 3 weeks ago).

      This issue is kind of an automatic update, in fact I never told it to install but it did after a reboot, and my settings say to always ask before installing. Macs are getting as bad as Windows for that shit. Now I see ""the macOS installation couldn't be completed." when I restart my computer and have to do a system restore, but it still happens everytime after a full restart.

    • Equally important: backup everything manually, nuke from orbit and - if at all possible - perform a fresh installation, not an update!
  • by 93 Escort Wagon ( 326346 ) on Friday April 20, 2018 @05:31PM (#56474199)

    After trying Sierra a couple times, I rolled back to El Capitan - and only recently upgraded my computers to High Sierra 10.13.4. None of the computers I upgraded (2016 MacBook Pro, 2015 MacBook Pro, 2012 MacBook Pro, 2012 Mac Mini, 2017 iMac) had any issues with the upgrade nor with any subsequent updates.

    I realize that's just anecdotal, but so are the reports in the story itself.

    • I've been told by various people that High Sierra has serious SMB performance issues when connecting to a Windows file server. I'm not sure if that's also true when connecting to any NAS as well. El Capitan, no problem.

      Apple changed something for sure.

      • Of course, Apple wants you to care, share, pay, and use their cloud storage, not be a selfish oaf and use local file storage :)
        • by dgatwood ( 11270 )

          Hah. Their maximum storage tier is only 2 terabytes. I can't remember the last time I had so little data to back up. Probably somewhere around the time they changed the name from .Mac to MobileMe.

    • Of course a possibly important distinction is that I updated to 10.13.4 from El Capitan, while it sounds like the problem reports are from people who are upgrading within High Sierra - from 10.13.3.

      • I installed 10.13.3 on 9-Feb and 10.13.4 on 12-Apr. I haven't had any of these problems they speak of, nor have I heard anything from IT support vendors about it.
  • by DMJC ( 682799 ) on Friday April 20, 2018 @05:32PM (#56474207)
    My housemate uses a Macbook with OSX for work, he's had this exact issue. I run Linux on mine so I avoided it, always annoying when patches break core os functionality.
  • by Anonymous Coward

    10.13.4 also breaks external monitors. We have had to prevent updates on many of the MACs on our network because of this.

    • See the link I posted about about authorizing the DisplayLInk Driver.

      • by dgatwood ( 11270 )

        Doesn't work. If you read the very top of that page, it says that the page applies up through 10.13.3, and there's a link to info about 10.13.4 [displaylink.com] that basically says, "It doesn't work in any mode that's actually useful. Don't upgrade."

    • I'm on 10.13.4 and I've got two external portrait displays working just fine. Did you buy genuine Apple video adapters or those cheap shit USB adapters from DisplayLink?
  • by Anonymous Coward on Friday April 20, 2018 @05:55PM (#56474391)

    For me, even though 10.13.4 installed fine, it has brought nothing but instability and performance degradation:
    1. There is 50% chance that if I close the lid on the laptop and then open it, it will crash silently.
    2. There is 95% chance that if the laptop entered deep sleep it will not get out of it without crashing. These crashes are not detected
    3. The kernel memory leaks are even worse than before. On startup with nothing open the kernel takes in excess of 1.5gb and in 30 minutes of work is up to 3gb of memory. After a couple of days it is taking about 6gb of memory.
    4. The purge command is completely broken, it never purges any memory, even if activity monitor says I have more than 3gb of purgeable memory.
    5. WindowServer does not reliably pass clicks to applications.
    6. Safari memory management is even worse than before. On average it takes 330mb per tab. If you have something like Jira, that tab is easily over 1gb of memory.

    Quality is down the drain. Windows 8.1 is my preferred platform these days.

    • As a user of Windows 8.1 at work and MacOS 10.13.4 at home. I have to say that your problems with MacOS are not universal, and that Windows 8.1 is truly a horrible chore to use. Which makes me think perhaps you are a troll.

  • I had an installation problem when installing the macOS 10.13.4 update on my MacBook Air.

    After rebooting, my system would crash (requiring a reboot) ad nauseam.

    I rebooted in Safe Mode and somehow got the machine out of the annoying reboot cycle. At that point, I rebooted back int 10.13.3 and resolved not to upgrade to 10.13.4 until I heard it was safe to install. When I went to the App Store and checked for updates, the 10.13.4 update disappeared from the list. (It seemed at the time that Apple had pulled i

  • by Ecuador ( 740021 ) on Friday April 20, 2018 @07:11PM (#56474857) Homepage

    As a developer, I have seen multiple times how under the "shiny" surface, Apple isn't really careful about what they are releasing, but the current macOS is one of the worse I've seen. For example, if you have installed it (and you can still boot), try opening the error console. Chances are you'll see that it throws several "signpost_notificationd - 0 is not a valid connection ID" errors every few seconds! It happens on all machines I have checked, a few 2013 Macbook Pros, a 2010 Mac Pro, a 2011 Mac Mini... And there are multiple threads about it, so it is not something in my part of the world :) Sure, it might be benign (although it is reported as an "error" - not warning - and some users claim it is related to excessive fan speeds), but how on earth can they release something that floods the error logs on many configurations, (including on a clean system, installed from scratch)?

    About that "clean system". Last week I decided to install a bigger SSD on my 2010 Mac Pro (the last type that was upgradeable - still hanging on with a 6-core 3.46GHz Xeon, 32GB RAM, USB3 and eSATA cards). I had a Mavericks install usb, did a clean install and upgraded directly to 10.13.4. The "clean" system was pretty unusable, there was an obvious lag on most UI things. E.g. hovering over each section of the top menu would open it after at least half a second (depended on the app - some faster, some slower). Activity monitor showed nothing in CPU or Disk usage. I actually thought there was something wrong with my new SSD, until I cloned the old disk with Mavericks to the new disk, booted and everything was snappy again. Not upgrading the old mac to High Sierra any time soon... Well, I can afford to as I have XCode on the laptop...

  • I just had this problem when installing Sierra (not High Sierra) on a MacBook Pro. This problem may be more wide spread than they think.

  • When I upgraded to 10.13.4 my machine went into safe mode upon reboot. It said the OS failed to install. A look at the error logged showed complaints about some file missing from the installer directory. Sent me into quite a panic for a while. I finally did a fresh, complete install.

The only possible interpretation of any research whatever in the `social sciences' is: some do, some don't. -- Ernest Rutherford

Working...