We have noticed an issue with the new 10.12.4 update and 13" MacBook Pro (w/ touchbar). In order to block this update, without blocking the App Store, we are pushing the following script in a policy:
#!/bin/bash sudo softwareupdate --ignore "macOS" sudo softwareupdate --ignore "macOS Sierra" sudo softwareupdate --ignore "macOS Sierra Update" sudo softwareupdate --ignore "macOS Sierra Update-10.12.4"
If you need to allow the users to update, after testing, running the following script will reset the software update to allow this:
#!/bin/bash sudo softwareupdate --reset-ignored
@hkabik We had previously ran "softwareupdate" on a 15" MBP w/Touchbar, and it just dropped into the kernel panic/infinit loop.
Our Apple TAM worked with someone that has had the problem, and their recommendation for systems already having the issue is to boot into Recovery Mode > Disk Utility > First Aid and then it worked.
No issues on our end with the MacBook Pro 15 and 13 Touchbar via App Store or using "softwareupdate -ai". My colleague did have weird graphics issues this morning on a non-touch bar new 13" MB Pro. A restart seemed to have fixed the issue, but we're not sure.
That said, I've been having funky wifi issues on a 2015 MB Pro 15" running macOS 10.12.5 beta 1. It doesn't like my home Xfinity wifi router and refuses to connect. A couple of restarts seems to fix it, but it comes back again... The trials and tribulations of running beta software. No biggie.
So, we saw this issue with immediately rebooting when attempting to log on after the 10.12.3 update on quite a few TB-MBP machines and in each case, the clock on the computer was set years in the future. If we booted each machine to something external that had network access like a deploy studio netboot and it could reset the clock to the current time, then we could put the machine in target mode and run the combo updater from another laptop while tethered. Once we would restart it out of target mode, it would then finish doing the firmware update for the touchbar and finish doing the OS update.
We've had the same problem with the date showing the year 2037 and then going to a boot loop. Both were 15" 2016 MBP. I've had to wipe both machines and only installed 10.12.3 and they work fine.
What's going to be the best way to get them on 10.12.4 without having these problems?
Just wiped a machine and reinstalled 10.12.3. Enabled FileVault. Then did the combo update to 10.12.4. When it was done, it went into the boot loop.
So I wiped again and reinstalled 10.12.3. Enabled FileVault. Let encryption complete this time. Did combo update to 10.12.4. Now it boots but the time is off (year is set to 2037).
Downloaded the full Install macOS Sierra version 10.12.4 (4.96GB) file from the App Store and copied it to a bootable USB drive. Booted from that drive on the problematic MacBook Pro. Wiped the machine again and this time installed the full version of 10.12.4 and now it's working. Time & Date is correct and no longer doing the boot loop.
I've seen the date and time issue on two Late 2013 MBP Retina this week, both computers recently updated to 10.12.4. Logging in I'd see the updating Managed Prefrences box for a few seconds and then the date was set to December 2037. I was able to log in as the local admin and go to the Date and Time preferences and uncheck the box to automatically set the date and time, adjust date and time to correct settings, recheck the box to automaticlly udpate date and time and do a reboot of the computer.
Well, the bug is back. I had made it through about 3 reboots until the final application install before giving it back to the customer and now it's showing the year 2040 (in the menu bar) and 2037 in the Date & Time Preferences panel.
Right after posting this I looked back at the machine and the year is back to 2017. I did nothing! What is going on here??
Another reboot. Back to 2040.
We saw this on a 15-inch Retina MacBook Pro with TouchID (Late 2016)
The Date was flipping between November 13, then December 19 2037 in the system.log, occasionally jumping to the current date.
It was set to autoset from Apple time servers.
Not imaged, just updated to 10.12.4
We saw this behavior when using a Belkin USBC to GB Ethernet.
After I read this discussion, mentioned above
I followed the suggestion to install the realTek driver for the Belkin chipset inside the adapter from http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=56&Level=5&Conn=4&DownTypeID=3&GetDown=false and the date problem immediately stopped on this device.
Weird. Hope this helps someone.
An update from AppleCare:
macOS 10.12.5 beta 4 is now available to eligible users. The build is 16F67a and it is available to members of the AppleSeed for IT (https://appleseed.apple.com) and Apple Developer seed (https://developer.apple.com/download/) programs. The beta 4 release is expected to address this issue described in this case where the date can randomly jump to twenty years in the future (2040). Please install the 10.12.5 beta 4 release on a test client and let us know if this appears to have addressed the issue.
I've run into a different problem with a MacBook Pro (Retina, 13-inch, Early 2015), since the update to 10.12.4 we've been experiencing total lock-up during random workloads, designing in Adobe Creative Cloud, copying text from a website, clicking between windows on desktop. Can't seem to pinpoint the conflict. Anyone else have heard of similar?
Attached activity monitor screenshot to look for any conflicts.