Archive. This is an archive of the Apple Support Community. Discussions are being restored and soon you will be able to read and post here again.

Incorrect clock shown on login screen at first cold boot (MacBook Air m5)

Hello,


I am experiencing a strange and reproducible issue with the clock displayed on the login screen.


Context:


  • MacBook Air m5(Apple Silicon, M-series)
  • macOS up to date 27.0
  • Correct time zone and “Set date and time automatically” enabled


Issue description:


  • After a cold boot (first startup of the day), the clock on the login screen shows an incorrect time.
  • Once I log in, the system time immediately corrects itself and is accurate.
  • If I lock the session or switch users afterward, the clock is always correct.
  • The issue only occurs at the very first startup, not after sleep, restart, or logout.


What I have checked:


  • Time zone and NTP settings are correct
  • Network is available (wifi)
  • No issue once the user session is active
  • No problems with system time inside macOS


Question:


Is this a known behavior or limitation of macOS during early boot on Apple Silicon Macs, possibly related to time synchronization before full network initialization?

Help with solutions


Thank you for any insights or confirmations.

13 replies

Based on the pattern you describe, temporarily disabling FileVault is a reasonable diagnostic test, but I have not found Apple documentation identifying FileVault as the cause of an incorrect clock at startup.


The important detail is that the incorrect time appears only before you log in after a cold boot. Once macOS is running, the time immediately becomes correct and remains correct.


That distinction is useful because the startup process before authentication is not identical to the fully running macOS environment. Apple documents that, on a Mac with Apple silicon, FileVault credentials are required during the boot process. Apple also documents that the Mac has a sequence of boot components that run before macOS itself is fully running. (Apple Support)


Apple separately documents that macOS can set the date and time automatically using network time services. (Apple Support) However, I have not found Apple documentation stating that FileVault controls the clock or that FileVault is responsible for an incorrect time in the pre-login environment.


For that reason, disabling FileVault should be viewed as a way of testing whether changing the startup and authentication path affects the symptom. It does not, by itself, test or establish that FileVault is the cause.


Before changing anything, I would first make the comparison as controlled as possible. After the Mac has been completely shut down for several hours, perform a cold boot and record the displayed time at the login/FileVault screen. Then record it immediately after authentication and again shortly after the macOS desktop appears. This establishes exactly when the correction occurs.


It is also useful to compare three situations: a cold boot after a complete shutdown, a normal Restart, and waking the Mac from sleep. If the incorrect time occurs only after a complete shutdown, that would provide useful evidence that the symptom is associated specifically with that startup path.


Network availability before authentication is another relevant observation. Since automatic time setting can depend on network time services, it would be useful to note whether the Mac has an active network connection at the pre-login screen. I would not change the configured time server at this stage; first establish whether the existing configuration behaves differently depending on the startup method. (Apple Support)


The FileVault test can then be performed if you want to continue isolating the cause. With FileVault enabled, perform several comparable cold boots and record the result. If you subsequently disable FileVault, repeat the same cold-boot test under otherwise similar conditions. If the symptom consistently disappears only when FileVault is disabled, that would establish a relationship between the changed startup configuration and the symptom. It still would not establish that FileVault itself is responsible for setting the wrong time.


One other point is important when interpreting that experiment: disabling FileVault does not mean that an Apple-silicon Mac simply becomes an unencrypted computer. Apple documents that internal storage on Apple-silicon Macs uses hardware-assisted encryption and that FileVault provides an additional user-authentication layer for protecting the volume. (Apple Support) Nevertheless, changing FileVault is a security-related configuration change, so I would use it only as a deliberate diagnostic test rather than as a routine troubleshooting step.


At this point, I would therefore describe the situation as follows: the symptom is clearly associated with the pre-login portion of a cold boot, but the available Apple documentation does not establish what component is responsible for the incorrect time. The most useful next step is to determine whether the behaviour changes with cold boot versus Restart versus wake from sleep, and then, if necessary, use the FileVault change as a controlled diagnostic comparison.


I have not found Apple documentation describing this exact pattern—an incorrect clock only in the pre-login environment following a cold boot, followed by an immediate correction once macOS is running—as a documented limitation or known issue.


Relevant Apple documentation:



Boot process for a Mac with Apple silicon



Volume encryption with FileVault in macOS



Startup security in macOS



If you can't change the time or time zone on your Apple device



Intro to FileVault



I have confirmed that FileVault is the culprit, at least on my M5 Pro 14" MacBook Pro. Off = correct time on start screen; On = incorrect time, i.e., Cupertino.

It is normal for the information on the login screen....especially after a reboot to be incorrect due to no users being logged into the system. With no users logged into the system, the system defaults to protecting user privacy & security by limiting the information that can be shown or updated. It has been this way for some years now.


And if Filevault is enabled, only the system firmware and the most basic system files are active which means none of the system configuration settings are even known or accessible until Filevault has been unlocked with the first user login.


FYI, I never trust the information shown on the login screen these days. I am usually most interested the battery charge level which I don't trust until after logging into the system as I've seen it report incorrectly too many times. I don't usually pay attention to the time as I'm just interested in logging into the system.

If you can-

take tge backup and reinstall macos it will b solved i did that now its fine

CanandaiguaMan wrote:
I have confirmed that FileVault is the culprit, at least on my M5 Pro 14" MacBook Pro. Off = correct time on start screen; On = incorrect time, i.e., Cupertino.

Thanks for the update & confirming FileVault can indeed cause this problem.


You can provide Apple with product feedback here:

Feedback - macOS - Apple


Personally I would stick with FileVault being enabled as it may be automatically re-enabled with some future macOS update patch or upgrade anyway. But everyone must make this choice for themselves.


sakshamiishra wrote:
If you can-
take tge backup and reinstall macos it will b solved i did that now its fine

I doubt that will help @CanandaiguaMan since they confirmed FileVault is the source of their problem. I explained the reason why FileVault may cause such an issue. Privacy & security come at a cost.


I suspect the same for you. When you reinstalled macOS, was FileVault enabled (was it prior to reinstalling)? You never followed up on this when I originally suggested this to you. I have never seen macOS enable FileVault by default when installing a clean fresh OS, but I have seen reports where upgrading an existing installation of macOS will enable FileVault automatically without any user intervention or notice which happened to people who upgraded from an older OS to macOS 26+.


I am fairly certain FileVault is the reason here. Of course every person's computer configuration is personally customized, so there are a lot of other variables in play here. It is possible you had something else going on here than @CanadaiguaMan has.


There is no need for @CanadaiguaMan or anyone to reinstall macOS these days since the OS itself cannot be modified (since macOS 11.x+). Only erasing the user customizations & data with "Erase All Content & Settings" followed by setting up the OS again with a new user account will actually be of any use as long as the user is careful with the stuff they restore from a backup as some restored configuration settings or apps may cause the problem to return again.

Can disabling FileVault fix it? I just want to check whether FileVault is causing the incorrect time to be displayed.

If FileVault is enabled, Apple confirms that the startup process differs from a normal login: an authorized FileVault user can start the Mac and log in using their password. 


However, Apple's documentation does not establish that FileVault causes an incorrect clock at startup. (Apple Support)


I could not find an Apple support document identifying a clock approximately 10 hours behind at the startup screen, followed by the correct time after login, or an Apple-documented Terminal command specifically intended to fix this symptom.


Edit: Deleted 2nd post due to forum website issue causing my post to appear twice.

I recently purchased a Mac, but the time shown on the login screen is incorrect, which is a little concerning. Is there any way to fix it so that the correct time is displayed?

What is tge backup? I don’t recognize the term.

i mean backup :)

It did for me. Try it and see.