macOS 10.12.4 change system date to 5 december 2040

[imactor]

Hi,
Am I the only one? the OS change the date of the system to 5 december 2040 or 2037 after a cold restart.
Any suggestions?

 

[rpmurray]

Replace the PRAM battery.

 

[chrfr]

Hi,
Am I the only one? the OS change the date of the system to 5 december 2040 or 2037 after a cold restart.
Any suggestions?

I have seen some mention of this happening to a few 10.12.4 computers but haven't seen it myself. It isn't related to the PRAM battery, but is perhaps a 10.12.4 bug.
It seems that it may be limited to the 2016 Touch Bar MacBook Pros. Is that what you have?
https://discussions.apple.com/thread/7904723?start=0&tstart=0

 

[leventozler]

Hi,
Am I the only one? the OS change the date of the system to 5 december 2040 or 2037 after a cold restart.
Any suggestions?

Happened to me only once on a 2013 iMac, after a cold start. The date was set to Nov 22, 2040. Messed up everything (certificates, safari history, imessages)

 

[Yahooligan]

Those that have had this problem, do you have NTP enabled (System Prefs -> Date & Time -> "Set date and time automatically") or do you have the clock set manually?

This really shouldn't happen if you're having time set automatically, even if the date/time is way off in the hardware clock this would correct it in the OS.

If it's happening even with this enabled, well...that's one heck of a bug!

 

[chrfr]

Those that have had this problem, do you have NTP enabled (System Prefs -> Date & Time -> "Set date and time automatically") or do you have the clock set manually?

This really shouldn't happen if you're having time set automatically, even if the date/time is way off in the hardware clock this would correct it in the OS.

If it's happening even with this enabled, well...that's one heck of a bug!

From what I've read, it's happening even when the computer is configured to set time and date automatically.

 

[imactor]

I have seen some mention of this happening to a few 10.12.4 computers but haven't seen it myself. It isn't related to the PRAM battery, but is perhaps a 10.12.4 bug.
It seems that it may be limited to the 2016 Touch Bar MacBook Pros. Is that what you have?
https://discussions.apple.com/thread/7904723?start=0&tstart=0

Hi, I have a MBPr Early 2015 :-(
First issue of this kind in this computer. My mac is exactly 1 year old.
[doublepost=1492447286][/doublepost]

Those that have had this problem, do you have NTP enabled (System Prefs -> Date & Time -> "Set date and time automatically") or do you have the clock set manually?

This really shouldn't happen if you're having time set automatically, even if the date/time is way off in the hardware clock this would correct it in the OS.

If it's happening even with this enabled, well...that's one heck of a bug!

Yes! the "Set date and time automatically" is on! The way I fix it it's by reloading that option.

 

[Filin]

Hi,
Am I the only one? the OS change the date of the system to 5 december 2040 or 2037 after a cold restart.
Any suggestions?

I had same issue, but only for the first boot. I went to Date & Time settings, unlock changes and time & date was updated automatically.

 

[imactor]

I had same issue, but only for the first boot. I went to Date & Time settings, unlock changes and time & date was updated automatically.

Yes! that's exactly what I end it up doing every time.

 

[JasonDog3]

Hi,
Am I the only one? the OS change the date of the system to 5 december 2040 or 2037 after a cold restart.
Any suggestions?

I have it too. Only a clean install of Sierra seems to have fixed it for now. But now my Time Machine is messed up and I can't correctly restore some files. Apple Engineering are studying the issue, after I chatted with them for 2 hours and did all kinds of things.

Also, this new update to Sierra has serious problems with WiFi connectivity -- Mail and Safari freezing needing a force-quit, Siri and App Store losing their connection.

What a HORRIBLE update. Typical of Apple to do such things to ruin perfectly good computers, forcing their customers to buy new machines. What a disaster!

 

[beltman]

Those that have had this problem, do you have NTP enabled (System Prefs -> Date & Time -> "Set date and time automatically") or do you have the clock set manually?

This really shouldn't happen if you're having time set automatically, even if the date/time is way off in the hardware clock this would correct it in the OS.

If it's happening even with this enabled, well...that's one heck of a bug!

After extensive troubleshooting, I've found that the problem occurs ONLY when NTP is enabled. Disabling NTP is the only way I can prevent this problem from recurring. Of course, this results in clock drift, which is annoying but far less of an issue than setting the date to 2040 after each restart.
-B

 

[Yahooligan]

After extensive troubleshooting, I've found that the problem occurs ONLY when NTP is enabled. Disabling NTP is the only way I can prevent this problem from recurring. Of course, this results in clock drift, which is annoying but far less of an issue than setting the date to 2040 after each restart.
-B

That's wild. If you or someone else would be willing, I'd be interested in seeing what the output of "ntpq -pw" shows.

Sample output...

$ ntpq -pw
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*usatl4-ntp-002.aaplimg.com
                 .GPSs.           1 u   67  128  377   31.807    0.122   2.060