Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
So updated to 10.13.2 wreaked all sorts of havoc on my mid-2009 MacBook Pro. First symptom was that Safari would not load web pages however Chrome worked fine. I noticed that Mail and the App store also were not working properly.

I reset PRAM and this re-enabled SIP. Or maybe SIP was already re-enabled by the update somehow and I was only informed of this after the restart after resetting PRAM? So, I tried to disable SIP by starting up on the recovery partition but I got the "do not enter" sign. Pressing the option key while restarting I noticed that the recovery partition was a recovery partition for 10.13.1! I tried to select it manually but got the do not enter sign again. I don't recall seeing any messages that suggested that my update to 10.13.2 was incomplete but perhaps it was.

I saw a few suggestions on this thread to clean things up with OnyX. I haven't used OnyX and it was no longer installed on my machine so I downloaded and ran the Automation script. Well that's was a mistake. This disabled my touchpad and keyboard. Luckily, I was able to log into my MacBook from my iMac via screen sharing. I noticed that safari and mail were working again but it seems that USB and Bluetooth were not.

Finally, I downloaded the full version of High Safari from the app store on my iMac, created an install flash drive. Using this I disabled SIP and went through the High Safari installation process again including installing dosdude1's patch. All is well now.

Fun!

Recovery updates are stripped down from thr updates installed via App Store, so if you pacthed your Recovery partition it’s still patched and working after an update. So, maybe you don’t have a pacthed recovery.

SIP status are stored on the PRAM, so resetting PRAM is turning back on SIP.

Without SIP you don’t have a working USB, so after clearing the cached with onyx, you are avle to loosr keyboard and trackpad. This is not a bug with Onyx, this is because you reenabled SIP.

You need to boot from any SIP compatible os (El Capitan or later) and turn off SIP and recreate the kext cache.
 
Maybe clearing the caches is the key for the fix.
[doublepost=1512761928][/doublepost]

If you find only the App Store and Safari is the non working apps, you need to run Onyx automation tasks to clean and rebuild the neccessary caches on your Mac. (this bug is not affects only us, it's happened to me on my HS supported iMac)


I had tried automation with no luck and ended up having to use a fresh USB install.
 
Experiencing problem during boot of previously working 10.13.2 install. After chime, screen turns black and starts running some kind of shell script. It quickly fails stating “no boot file”. I tried the usual things- made sure SIP is disabled, re-ran post-install and forced kext rebuild. Was also not successful.
 
I have a mbp 17 early 2009 (5,2) with SSD -- and I upgraded from 10.13.1 to 10.13.2, two days ago, and initially thought everything was fine, but I've started to notice the system become unresponsive during "heavy" (normal) disk access, mainly related to spotlight indexing and hourly with backupd_helper. Automatic Time Machine backups are not enabled, but backupd_helper triggers kernel_task high CPU and device input lags and freezes. And now, when the screens turn off while idle (but not sleeping,) the internal display doesn't wake afterward. I'm forced to unplug the external monitor, and then internal display returns to normal behavior. Aside from those two annoying issues, it seems to perform well, although I may have to downgrade to 10.13.1, again.

Update: After running Onyx Automation, those annoying symptoms seem to have vanished. I have no idea why rebuilding some caches seems to help so much, or why I didn't have to do that regularly back before my hardware was abandoned by Apple. But, whatever. And thank goodness. I'll just have to remember to superstitiously run Onyx when I see issues.
 
Last edited:
Ok so that security patch borked my system. No trackpad no usb so I couldn’t get in. So I’m wiping and putting Linux on it. Guess if I want OS X I need a supported system. :) next year maybe
 
Ok so that security patch borked my system. No trackpad no usb so I couldn’t get in. So I’m wiping and putting Linux on it. Guess if I want OS X I need a supported system. :) next year maybe
That sounds like SIP became enabled. You'd only need to disable SIP and redo the post install patch.
 
@doobydoooby I did a DuckDuckGo search on "continuity activation tool" (wasn't familiar with it) and found it at GitHub. The most current version is a beta for Sierra. Is that what you used?

Hi Hack, yes indeed I used the most up to date continuity activation tool which works fine on high sierra. Just to be clear however, this isn't something to fix any issues caused by the most recent high sierra OS update. The continuity activation tool just allows older macs to use handoff / continuity from ios and it is one of the things that typically needs to be checked and re-enabled after each major software update - in fact the tool automatically checks at login whenever it has been turned off without reason.
 
I downloaded the Combo Update, and modified it so it could run on my MacPro 3.1. With only a few minutes remaining of the install it quit with an error message. So I restarted and everything was at a crawl, however About This Mac shows that I am on 10.13.2, but this is not reflected in the Installations section of System Report. Had to run Onyx to get Safari etc working, but was wondering why the installer quit and if anything was missed in the install by it quitting.
 
That sounds like SIP became enabled. You'd only need to disable SIP and redo the post install patch.

So I did disable SIP and that’s when I lost usb and trackpad support. I think rebuilding the kext Cache would have worked but I think for all the performance hits Linux will be my best bet for now. :) 2018 could provide a new Mac mini so maybe then I’ll be back to macOS
 
So I did disable SIP and that’s when I lost usb and trackpad support. I think rebuilding the kext Cache would have worked but I think for all the performance hits Linux will be my best bet for now. :) 2018 could provide a new Mac mini so maybe then I’ll be back to macOS

No. You created the kext cache when you booted with enabled SIP, thats why you lost USB.
 
Some good news finally. It appears that Apple may finally be done with firmware updates. The new 10.13.3 beta seed applies cleanly over a patched 10.13.2 on a MacPro 3,1 without any installations issues. There are no notifications of installers failing to complete from the update and the resulting Safari and AppStore works normally. Nice.
 
  • Like
Reactions: Dr.Bleed
Hi Hack, yes indeed I used the most up to date continuity activation tool which works fine on high sierra. Just to be clear however, this isn't something to fix any issues caused by the most recent high sierra OS update. The continuity activation tool just allows older macs to use handoff / continuity from ios and it is one of the things that typically needs to be checked and re-enabled after each major software update - in fact the tool automatically checks at login whenever it has been turned off without reason.

Currently I don't use Continuity, so I wasn't aware a separate program was needed to enable it. Learned something new, thanks!
 
10.13.2 update killed the two mid 2009 macbook pros I was running it on as well. Everything was slow and memory usage was almost maxed at idle. Put them back on 10.11 until 10.13 is done updating.
 
Looks like this update messed up my iMac 2009. Safari and App Store aren’t working. Oh the fun!
 
Just curious, is patched 10.13.2 supposed to boot twice? MacBook Pro 5,2 chimes, restarts and then fully boots. Runs fine after that.
 
I have a 2009 MacBook Pro 5,2 ( 17 inch ) and have been able to update the operating system, without an issue, through 10.13.3 (first beta of 10.13.3 series.)
My HDD is a "hybrid" type (Momentus (?)). System was patched with 2.5.1 version of High Sierra Patcher, and drive is formatted in APFS.

Note, that if the drive is formatted in APFS, one cannot create a recovery partition. If that has changed recently, please advise.

Hope this information may be of help.
 
10.13.3 installed over night. first patch since 10.13.1 where I didn't have to run automation in onyx on a 5,3 MacBook Pro.
 
Updated to 10.13.2 today on the Macbookpro 5,2. Works great. Computer even wakes up now without any issues and brightness works right off the bat. I manually updated though and ran the post installer again for good measure. The only thing I can figure with the issues I was having in 10.13.1 is either they were specifically related to that version and the update fixed it or it didn't play well with the post installer for whatever reason. It also could have been updating through the app store instead of doing it from scratch which I think I might just take the time to do in the future to make sure there aren't any mishaps. At any rate very happy! Thanks for the help guys.
[doublepost=1513206397][/doublepost]
Just curious, is patched 10.13.2 supposed to boot twice? MacBook Pro 5,2 chimes, restarts and then fully boots. Runs fine after that.

Same here. I don't think its supposed to do that but as long as it runs like it should beyond that point I'm a happy guy.
 
  • Like
Reactions: zrw2011
MacBook 5,1 Unibody, running MacOS High Sierra 10.13 on AFS, want to update it to 10.13.2, downloaded and tried update combo, can someone please guide me with it.
 
MacBook 5,1 Unibody, running MacOS High Sierra 10.13 on AFS, want to update it to 10.13.2, downloaded and tried update combo, can someone please guide me with it.
Follow the instructions below for modifying the update so it can be installed on an unsupported machines.
The instructions below mention the 10.3.1 update but just substitute the 10.13.2 Combo update for it.

Modifying the 10.13.1 Update for High Sierra.



Download 10.13.1 Update.

Open 10.13.1 Update.

Move 10.13.1Update.pkg to Desktop.

Open Terminal.

Enter pkgutil --expand ~/Desktop/macOSUpd10.13Update.pkg ~/Desktop/Expanded



Open Expanded folder and then open Distribution file in BBEdit



Change Distribution file, change Board iD line 33 to <your Macs boardID> at line 41 remove <your Mac model>



Save As .xml file to the Desktop



In Terminal chmod +x ~/Desktop/distribution.xml

Remove the extension .xml

Move new Distribution file to Expanded folder replacing the original

In Terminal pkgutil --flatten ~/Desktop/Expanded ~/Desktop/Modified.pkg



Using the .pkg extension is crucial.

The Modified package on your desktop should now allow you to install the latest update
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.