Login screen clock is incorrect

[macbeginner101]

My mac is set at an automatic time and is correct when I am logged in. However, if I were to shutdown and turn on, I am met by the login screen with an incorrect time set 3 hours back. Once I login, the time goes back to normal, but this issue is bothering me. Tips?

 

[ferrarr]

Can you please give us all the pertinent info:

about your Mac?
about your internet/home network setup?

 

[chscag]

Welcome to our forums.

Go to System Preferences, Date & Time, and make sure you have selected which time zone you're located in and the date/time. You will need to click on the small lock at the bottom and enter your admin password before changes can be made. After doing that, reboot and log on again. The date/time should then be correct.

 

[macbeginner101]

It is an M1 MacBook Air 256gb 16gb RAM 7 Core GPU. I am connected to relatively quick internet.

 

[pm-r]

Is your System Preferences -> Date & Time tab set with the "Set Date and Time automatically" option box checked and enabled???


- Patrick
=======

 

[chscag]

@Patrick:

Aside from that, he also has to set the correct time zone. Which I believe he hasn't done because his log on is off by 3 hours.

 

[pm-r]

Aside from that, he also has to set the correct time zone. Which I believe he hasn't done because his log on is off by 3 hours.

Hmmm...I forget that it seems that you admins can see much more posted info than us, ordinary members.


- Patrick
=======

 

[chscag]

Hmmm...I forget that it seems that you admins can see much more posted info than us, ordinary members.

Huh? Read his first post. We admins do not have a Crystal Ball.

 

[macbeginner101]

The time is set automatically, so is the time zone. When I enter my password, the time is correct, it is only the login screen that shows a 3hr early time.

 

[IWT]

The time is set automatically, so is the time zone. When I enter my password, the time is correct, it is only the login screen that shows a 3hr early time.

Have you, by any chance got more than one user? What I mean, is did you create a second user at any time, be it Admin or Guest and with the same login password?

I'm just toying with the idea that your opening login gets you into the system which is set at a different time; then you get into your account with the correct time.

Ian

 

[Lifeisabeach]

The time is set automatically, so is the time zone. When I enter my password, the time is correct, it is only the login screen that shows a 3hr early time.

Try turning off automatic setting of the time zone just to see what happens.

I did a brief googling of the problem and found a short thread on Reddit where others are having the same problem. Methinks this may be a Big Sur bug.

EDIT: Here's another thread on Reddit. What version of Big Sur are you on? Make sure you are fully updated to 11.1.

 

[pm-r]

Huh? Read his first post. We admins do not have a Crystal Ball.

OK, I guess I was thinking that maybe you as an admin could see some incorrect or offset timestamp in their posts.

But it seems quite likely that Big Sur has a bit of a bug as Lifeisabeach discovered in their google search.


- Patrick
=======

 

[chscag]

But it seems quite likely that Big Sur has a bit of a bug as Lifeisabeach discovered in their google search.

Yep, I think "Life" may be right. The first iteration of Big Sur (11.0.1) had a lot of holes in it that needed to be fixed. That's why we saw 11.1 shortly thereafter. But hang on to your Canadian Sombrero, because we are going to see 11.2 before long.

 

[pm-r]

But hang on to your Canadian Sombrero, because we are going to see 11.2 before long.

Well, some may, but I sure won't be one of them, and not because my 2011 iMac cannot even run it.

I wonder if the timestamp bug is just related to the Apple chips or not???


- Patrick
=======

 

[Lifeisabeach]

Well, some may, but I sure won't be one of them, and not because my 2011 iMac cannot even run it.

I wonder if the timestamp bug is just related to the Apple chips or not???

I checked mine yesterday before posting and I'm not seeing it, but I wouldn't rule it out being something that was fixed with 11.1.