Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Try to boot in safe mode or in Disk Utility so you can try to reinstall MacOS again. If not try to use internet recovery mode to download the latest or out of box that was running on your 2018 MacBook Pro.

Thank you for the suggestion. Luckily after multiple reboots the system booted and all updates installed successfully.
 
Are those 17G build number going the wrong way?
MacRumors has the build number wrong. 17G2037 may be the build number of the original release of 10.13.6 for the 2018 MacBook Pro but I don't have one handy to check.

Looking inside the installers:

The first supplemental update was 17G2208.

The second supplemental update is 17G2307.
 
Everything went smoothly here... No notable outward changes that I'm seeing/feeling... I was having excessive fan issues, so I'll keep an eye on that... I also updated JAVA in Safari, as I was having significant memory issues with certain websites...
 
MacRumors has the build number wrong. 17G2037 may be the build number of the original release of 10.13.6 for the 2018 MacBook Pro but I don't have one handy to check.

Looking inside the installers:

The first supplemental update was 17G2208.

The second supplemental update is 17G2307.
Build 17G2037 is correct according to developer site.
0jcbDa2.png
 
This patch might not be the one a few of you were asking for.

Windows received further patches for Intel CPU security problems last week. Today's update must have included those.

Geekbench results on 2.6Ghz model look good. SC 5214. MC 21939.
 
  • Like
Reactions: Lennyvalentin
Hi guys, Apple decided to replace my 2018 MBP 15 with T2 BridgeOS kernel panic. I just picked it up, it’s a retail box version, not replacement box version. I will see how it goes with this one. I have time machine backup on all the time.
 
Last edited:
  • Like
Reactions: DeepIn2U
Update went trouble-free for me, and reasonably quickly too. I didn't time it, but less than 10 mins all told probably (not counting time spent downloading.) Did not notice any difference in the 30 seconds I spent after the OS booted back up... ;) Will see if I hear any chimes or such; had a few singular charger chimes over the course of a week and a half maybe, and then it went nuts, chiming multiple times over the course of maybe an hour or two, at which point it eventually crashed - which I only noticed the day after when I lifted the lid and it was black and dead and unresponsive. Booted it back up, and it had had its first (and so far only) kernel panic. (T2 related, although I did not examine exactly what had gone wrong.) This was over a week ago now, and nothing since. Not a single peep in fact.

So touch wood...

it hasn't fixed the constant noise in my headphone port which sounds like really bad shielding. during the install process, the noise (which is the same volume irrespective of the computer's volume setting) went away until the install was halway complete making me think it might be fixed, but no such joy.
If the issue is what it sounds like - IE bad shielding - then no software in the world will be able to fix it. That it went away momentarily is probably because the installer most likely shut down the audio sub-system/amp during the update. Then after activation it would power up the audio hardware again, and the noise would return.

Personally I've never been super impressed by Apple's audio hardware; my OG Apple Watch's speaker hisses extremely audibly any time it plays audio, my previous MBP's headphones jack hissed, plus it popped any time the audio CODEC went in/out of power save mode (known issue for my generation of MB IIRC). My 2018 MBP's headphones jack also hisses, but then again I plan on basically never using it, or at least as little as possible, preferring the cordless freedom of airpods instead. :)

It usually gets pretty hot while doing things that i would't expect it to get hot while doing them. Like downloading a large file or playing a video on plex. And it feels like the fans are at full speed pretty often.
My experience has been pretty far from that, with the unit running silently and cool most of the time, although curiously, this particular software update made the fans rev crazy high. I've literally never heard them spin that fast before, ever. :p Unit did not have time to heat up noticeably though, as it quieted down significantly after a one or a couple minutes.

I often had my old MBP spin its fan up to turbo speed though (2011 generation), and it had a really horrible, noisy fan, so this was not fun. 2016 onwards MBPs have a much better designed cooling system, from a noise standpoint, as the dual blowers used now are never anywhere as loud as the 2011 generation's single.
 
I have the 13" MBP 2018, almost maxed out. I have gotten like 5-10 kernel panics. Mostly related to playing videos in fullscreen in safari, like youtube clips. Screen freezes, putting lid down and screen is still glowing. They seem a bit random. Computer is pretty slow to restart after force shutting it down.

Hope this update fixes this one.
 
  • Like
Reactions: answan
Your statement isn’t correct, as High Sierra will continue after Mojave is released.

Heck, Sierra will continue as well.

Apple has consistently been patching the three most-recent versions of macOS / OS X for quite some time. I stayed on El Capitan until recently - and just moved to High Sierra a couple months ago, anticipating El Capitan's EOL.
 
  • Like
Reactions: martyjmclean
Just wondering if anyone else encountered the same issue installing? Error 602
 

Attachments

  • 44979738-6491-4618-879D-399759244912.jpeg
    44979738-6491-4618-879D-399759244912.jpeg
    158.6 KB · Views: 244
I have the most recent 2018 15" i9 and have really push it to it's limits since the day it landed.

Alot of code compilation, multitasking, running VMs as well as some gaming with the graphics cranked up and I run several applications that have 3rd party kernel extensions (VMWare Fusion, Little Snitch and something else I can't remember).

Interestingly I haven't had a single kernel panic, lock up, weird noise or anything unexpected. I'm not saying those problems don't exist for some people - but it is interesting that I haven't encountered them.
 
  • Like
Reactions: DeepIn2U
I have the most recent 2018 15" i9 and have really push it to it's limits since the day it landed.

Alot of code compilation, multitasking, running VMs as well as some gaming with the graphics cranked up and I run several applications that have 3rd party kernel extensions (VMWare Fusion, Little Snitch and something else I can't remember).

Interestingly I haven't had a single kernel panic, lock up, weird noise or anything unexpected. I'm not saying those problems don't exist for some people - but it is interesting that I haven't encountered them.
Same w my wife’s i9. Problem free and well used.
 
  • Like
Reactions: DeepIn2U
If the issue is what it sounds like - IE bad shielding - then no software in the world will be able to fix it. That it went away momentarily is probably because the installer most likely shut down the audio sub-system/amp during the update. Then after activation it would power up the audio hardware again, and the noise would return.

Personally I've never been super impressed by Apple's audio hardware; my OG Apple Watch's speaker hisses extremely audibly any time it plays audio, my previous MBP's headphones jack hissed, plus it popped any time the audio CODEC went in/out of power save mode (known issue for my generation of MB IIRC). My 2018 MBP's headphones jack also hisses, but then again I plan on basically never using it, or at least as little as possible, preferring the cordless freedom of airpods instead. :)

i use it for audio as well as gamedev and even though i will often have it hooked up to a proper soundcard once i replace my firewire one, i still need to plug in quality wired headphones on the go, just as an example. my iphone and 2012 macbook pro exhibit no audible noise plugged into the same cord (all on max volume.)

after a bit more digging i've found the source of the noise to be when the USB-C -> Displayport cable is plugged in. so that means it should be ok on the road at least as i probably won't often be plugged into a screen.

it doesn't matter if the USB-C -> Displayport is on the other side from the headphone output, it seems the signal of the thunderbolt bus is getting transferred onto the audio path somehow. so if it just shielding as you say, it may not be fixable. :eek: i will consider another cable... so many new dongles and cables for this new machine haha :D at least i have an avenue to explore i guess.

no audio stutter / corruption since the update (6 hours or so uptime) which is something! i do think the DAC sounds noticably worse than the 2012 though.

the game i'm working on seems to run choppier. i've noticed that, even at the same resolution and settings, i'm seeing worse spikes in Metal on the 2018 than on OpenGL on the retina 2012. hopefully it's just the update 'settling', but it was doing this from time to time before. it's as if this machine is constantly fiddling around with its settings to manage thermals and it causes spikes here and there where it jumps down in speed. not ideal for gamedev ... my 2012 was def more consistent, though it did drop a few fps below 60 in the busiest spots, this one manages those spots, but has consistent spikes. all this for a couple of mm of thickness.

i also don't think we'd be seeing half these issues if it wasn't for the T2. i don't even like the touchbar, will never use it unless forced to (having tried in earnest) and wish i could remove it as it causes more errors than correct entries in my workflow. it's draining battery, causing complications in the software, making keyboards less repairable, slower to achieve the same functions as before, lacks haptic feedback. the additional security layers i can take or leave tbh. the SSD speed is welcome but i doubt i'd notice the different with one half as fast.

sorry i know it's not the exact thread for this full review but it does relate to the issues seen which are hopefully being patched in this update.
 
Just wondering if anyone else encountered the same issue installing? Error 602
I saw the same issue - and also had it with the last 2018 patch update (thermal throttle fix). The fix for me both times was to join another WiFi network and to turn off my web proxy in network settings. And to keep trying. And to burn some incense. Eventually it worked without error.
 
  • Like
Reactions: Lennyvalentin
I wonder if they are going to fix the Mail app from force quitting. Hopefully Mojave fixes that! Wonder why the rest of us didn't get the update!
 
Hopefully this update fixes my wake issues when plugged into TB3 dock as well as a few weird Wi-Fi issues I’ve had...anyone else experienced dropped Wi-Fi connections? Had to toggle Wi-Fi on and off. Also had constant Bluetooth Mouse connect/disconnects... that seemed to happen every 15-30 minutes for 5 - 10 secs
 
I saw the same issue - and also had it with the last 2018 patch update (thermal throttle fix). The fix for me both times was to join another WiFi network and to turn off my web proxy in network settings. And to keep trying. And to burn some incense. Eventually it worked without error.

I didn't have this issue with the first Supplemental Update so it's odd to me. I tried looking into it before posting and saw the Web Proxy solution. Mine has been unchecked the entire time so it doesn't work for me. Even the manual install doesn't work for me. Better use the cursed monkey paw ;)
 
Looks like audio crackling issue was resolved for both os(macos and windows).i think is firmware update. There is no issue for me anymore. Mbp 13 2018tb

My 15" 2.2ghz/555x/32gb was consistently running at 3.3ghz-3.5ghz through the day with temp hovering around 64-65 celsius and pushing 2 external 1920x1200 monitors/parallels windows 10/etc. It just hums along at 3.3-3.4ghz as if that were it's clock speed and I had turbo boost engaged to hold it at 3.4ghz.

Very pleased with the 2.2ghz and this update.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.