You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Update to 10.12.4 causing Date/Time Issues

Immediately after installing the 10.12.4 update I have problems with my system date-time. On initial boot I am getting a system date of 7th November 2040 or thereabouts. A few seconds later the system gets the correct time from an internet time server. I have reset PRAM and this did not help. I've not been able to get the key combination to reset SMC to work for me. It seems erratic, sometimes the date is correct. Were it not that this occurred immediately after the update I might consider other problems but I'm sure it's linked somehow.


I am about to download and reinstall 10.12.4


Not sure why I can't get SMC reset to do anything.

MacBook Pro (Retina, 15-inch, Late 2013)

Posted on Mar 28, 2017 11:24 AM

Reply
88 replies

Mar 28, 2017 11:30 AM in response to DaveGarratt

Possible Fixes for El Capitan and Later Installations


You should try each, one at a time, then test to see if the problem is fixed before going on to the next.


Be sure to backup your files before proceeding if possible.


  1. Resetting your Mac’s PRAM and NVRAM
  2. Reset the System Management Controller (SMC)
  3. Start the computer in Safe Mode, then restart normally. This is slower than a standard startup.
  4. Repair the disk by booting the from the Recovery HD. Immediately after the chime hold down the Command and R keys until the Utility Menu appears. Choose Disk Utility and click on the Continue button. Select the indented (usually, Macintosh HD) volumeentry from the side list. Click on the First Aid button in the toolbar. Wait for the Done button to appear. Quit Disk Utility and returnto the Utility Menu. Restart the computer from the Apple Menu.
  5. Create a New User Account Open Users & Groups preferences. Click on the lock icon and enter your Admin password when prompted. On the left under Current User click on the Add [+] button below Login Options. Setup a new Admin user account. Upon completion log out of your current account then log into the new account. If your problems cease, then consider switching to the new account and transferring your files to it - Transferring files from one User Account to another.
  6. Install Combo Updater Download macOS Sierra 10.12.4 Combo Update and install.
  7. Reinstall OS X by booting from the Recovery HD using the Command and R keys. When the Utility Menu appears select Reinstall OS X then click on the Continue button.
  8. Erase and Install OS X Restart the computer. Immediately after the chime hold down the CommandandRkeys until the Apple logo appears. When the Utility Menu appears:
  1. Select Disk Utility from the Utility Menu and click on Continue button.
  2. When Disk Utility loads select the drive (out-dented entry) from the Device list.
  3. Click on the Erase icon in Disk Utility's toolbar. A panel will drop down.
  4. Set the Format type to Mac OS Extended (Journaled.)
  5. Click on the Apply button, then wait for the Done button to activate and click on it.
  6. Quit Disk Utility and return to the Utility Menu.
  7. Select Reinstall OS X and click on the Continuebutton.

May 16, 2017 6:06 AM in response to DaveGarratt

As per this article : About the macOS Sierra 10.12.5 Update - Apple Support

About the macOS Sierra 10.12.5 Update

This update is recommended for all macOS Sierra users.


The macOS Sierra 10.12.5 Update improves the stability, compatibility, and security of your Mac, and is recommended for all users.

This update:

  • Fixes an issue where audio may stutter when played through USB headphones.
  • Enhances compatibility of the Mac App Store with future software updates.
  • Adds support for media-free installation of Windows 10 Creators Update using Boot Camp.
  • Adds support for more digital camera RAW formats.
  • Resolves an issue, affecting some enterprise and education customers, that may cause the system date to be set to the year 2040.
  • Prevents a potential kernel panic when starting up from a NetInstall image. This fix is available when starting up from a NetInstall image created from the macOS 10.12.5 installer.

See Apple Security Updates for detailed information about the security content of this update.

Learn how to get this macOS update.

You , can install Mac OS Sierra combo update 10.12.5 that has been released .

Apr 19, 2017 1:22 AM in response to DaveGarratt

Wanted to post an update; I installed the ethernet drivers, and I haven't had the problem happen for me since then. I've rebooted/booted from a shut down multiple times. If it does happen I'll update accordingly, but the ethernet drivers did the trick for me! 2016 15" MBP.


Edit: Considering the fact that installing the updated ethernet drivers solved the problem for some of us so far, I'd suggest others to do the same, even if they aren't using a USB-C to ethernet adapter, or any ethernet device for that matter. Link to the original post with the drivers - Re: Update to 10.12.4 causing Date/Time Issues


Link to the drivers - http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=56&Lev el=5&Conn=4&DownTypeID=3&GetDown=false

Apr 26, 2017 3:17 PM in response to DaveGarratt

I bought a new MBP 15 Late 2016 earlier this week. Been having all kinds of issues with tied to time...have rebuilt it twice. Same thing happening to me today whenever trying to use time.apple.com to set date and time automatically. Every time I rebooted, time was being set to late 2040.


Finally I tried the NVRAM / SMC resets. Wasn't even sure if I did those right as there is no confirmation when you do this. Booted my machine back up and before I logged in, I could tell the time had changed and was wrong. Someone walked in my office, so it was 2-3 minutes later before I logged in. By the time I did, the system time fixed itself before I had logged in.


In short, it might be that if you are having this issue, you just need to wait 10-15 seconds before you log in. I'm not sure if it was this on its own or this paired with the NVRAM / SMC reset that worked, but regardless, my machine is finally working correctly again with the set date and time automatically enabled.


And if none of this works for you, setting the time manually with the time zone detected automatically was working for me fine...just frustrating that part of the functionality of your $3000 computer doesn't work. Feels very Microsoftish.


How to reset NVRAM on your Mac - Apple Support

Reset the System Management Controller (SMC) on your Mac - Apple Support

Mar 31, 2017 3:26 PM in response to DaveGarratt

Immiediatly after reboot I load the console log view app and select system log and scroll to the top. As you can see the date is for a moment the 9th of October. I suspect a lot of people are getting this and don't realise it because the OS is getting the internet time and correcting it. Also I normally do a cold boot rather than resume from suspend. It may also be tied to certain hardware configurations depending on where the RTC clock stores its data.


Oct 9 02:28:23 MacbookPro15 com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit

Oct 9 02:28:24 MacbookPro15 com.apple.preference.datetime.remoteservice[607]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked

Oct 9 02:28:24 MacbookPro15 logd[76]: Time zone changed, updating file headers

Oct 9 02:28:28 MacbookPro15 filecoordinationd[403]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked

Oct 9 02:28:28 MacbookPro15 com.apple.xpc.launchd[1] (com.apple.preference.datetime.remoteservice[607]): Service exited due to signal: Killed: 9 sent by com.apple.preference.datetime.re[607]

Oct 9 02:28:32 MacbookPro15 com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit

Oct 9 02:28:32 MacbookPro15 com.apple.preference.datetime.remoteservice[617]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked

Oct 9 02:28:33 MacbookPro15 logd[76]: Time zone changed, updating file headers

Oct 9 02:28:43 MacbookPro15 GoogleSoftwareUpdateDaemon[561]: 2040-11-14 08:56:59.925 GoogleSoftwareUpdateDaemon[561/0x7fffcf59e3c0] [lvl=2] -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.

Mar 31 22:58:21 MacbookPro15 Dropbox[386]: PyObjCPointer created: at 0x112fcc0e0 of type ^{OpaqueJSContext=}

Mar 31 22:58:22 MacbookPro15 garcon[411]: Connecting to Dropbox on 'com.getdropbox.dropbox.garcon.cafe_501'

Mar 31 22:58:22 MacbookPro15 garcon[411]: Connected to Dropbox on 'com.getdropbox.dropbox.garcon.cafe_501'.

Mar 31 22:58:22 MacbookPro15 garcon[411]: Invalidating watch set.

Mar 31 22:58:22 MacbookPro15 garcon[411]: Watch set is now: {(

Apr 4, 2017 1:31 PM in response to atkin88

I did a PRAM and SMC reset and I thought it had fixed the problem but it still occurs from time to time. When I spoke to apple support they were at a loss to fix it and suggested a total format and reinstall. I need my laptop operational and can't afford the downtime. You are the 3rd person who has mentioned this on the forum so there must be a link however obscure to the latest is Sierra update. I'd rather apple fix it than have to reinstall and then encounter the same problem again. If you can speak or chat to apple maybe they will be more likely to investigate.


Dave


I am using a MacBook Pro 15 - 2013

Apr 5, 2017 1:44 AM in response to DaveGarratt

Hi. Sorry to hear about your problems. I found this thread when searching for answers since I have the same issues. Today I tried the suggested methods:

* Resetting SMC

* Resetting NVRAM

* Reinstalling Sierra.


For the record, I completely wiped the ssd and re-partitioned the SSD prior to reinstalling.


Unfortunately, none of this helped. A soft reboot will keep the date correctly, but a hard reboot sets the time to November 2040.


I have a 15" MacBook Pro with Touch Bar.

Apr 5, 2017 6:38 AM in response to DaveGarratt

I'm in contact with a senior advisor at AppleCare, but the issue is not yet resolved with them.


After an immense troubleshooting, I may have found the cause of the date issue. But it sounds very odd to me.


Do you guys by any chance have an LG UltraFine 5K display (Thunderbolt 3), and a Belkin USB-C Ethernet adapter?


Each time I unplug the Thunderbolt monitor, it works without any issues. It seems to be working with the Belkin Ethernet adapter unplugged from the display. It also seems to be working with the Belkin Ethernet adapter plugged in directly to the MacBook Pro 15" Touch Bar 2016 model. But not with all the adapter plugged in to the USB-C host of the LG UltraFine 5K display.


Can anyone confirm? Or maybe this opens to more detailed conclusions?

In any case, I hope this can spare someone a lot of time troubleshooting.


Thanks.

Apr 5, 2017 8:24 AM in response to gmrepoli

Seems I resolved the issue! Many thanks to olsberg for his hint!


Just install the driver for the Chipset built into the Belkin adapter from this webpage:

http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=56&Lev el=5&Conn=4&DownTypeID=3&GetDown=false


This driver improved the network speed when the adapter is connected to the 5K monitor and also resolved the issue with wrong date at boot up! Now I can boot with everything connected and date stays correct as booting without anything connected!

Apr 5, 2017 5:23 PM in response to DaveGarratt

Unfortunately, this is getting to be a thing. I brought my computer down to an Apple Store after the clock repeatedly showed a 2040 date and I manually reset the clock to the correct date and time and the automatic clock function took over. The technician at the Apple Store ran Disk First Aid. They recommended trying to create a new identity to see if the problem arises with the new identity. Their strategy is to reinstall Sierra if it doesn't appear using the new identity. I've read here this doesn't address the issue. I suspect it's a hardware problem since this happened to me sporadically before the last update.

Update to 10.12.4 causing Date/Time Issues

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.