Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x80CF0437 | Company Portal app and Intune management extension logs | -> Indicates system clock out of sync |
| Affected OS build range | Windows 10 / Windows 11 | Microsoft documentation | -> Applies to all supported versions |
| Relevant service/endpoint URL | time.windows.com | Windows Time Service configuration | -> Default NTP server used by Windows |
| Log file signature | 'Token expired' or 'System clock out of tolerance' | C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\ | -> Indicates time synchronization issue |
| CMOS battery status | Dead or dying | BIOS/UEFI setup and device inspection | -> Causes BIOS clock reset on power cycle |
Log Files to Check
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\C:\Windows\System32\Winevt\Logs\Microsoft-Windows-Time-Service%4Operational.evtx
What This Error Actually Means
The error code 0x80CF0437 indicates that during Microsoft Intune enrollment, the device's system clock is significantly out of sync with the Intune service. Specifically, the time difference exceeds a 5-minute tolerance enforced by OAuth 2.0 and certificate validation mechanisms. This causes the JSON Web Token (JWT) issued by Entra ID to be considered expired or not-yet-valid from the device's perspective, resulting in enrollment failure at the token acquisition step.
This error is raised by the Intune management extension when it detects a time discrepancy during the enrollment process. The root cause lies in either hardware-level timekeeping issues (e.g., CMOS battery failure) or misconfigurations in the Windows Time service (w32tm), which handles network time synchronization.
Affected Versions and Scope
This error affects devices running:
- Windows 10 (all builds)
- Windows 11 (all builds)
The issue is not specific to any particular Intune tenant configuration but rather depends on the device's ability to maintain accurate time synchronization. Devices enrolled via Autopilot or manual enrollment through the Company Portal are equally susceptible.
Where To Look First: Logs and Event IDs
To diagnose this issue, examine the following log files:
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\: Look for entries containing'Token expired'or'System clock out of tolerance'.C:\Windows\System32\Winevt\Logs\Microsoft-Windows-Time-Service%4Operational.evtx: Search for Event IDs201(time synchronization failure) and306(clock not updated due to large discrepancy).
Root Causes
Dead or Dying CMOS Battery
A dead CMOS battery causes the BIOS/UEFI clock to reset to a default date (e.g., 2013-01-01) after each power cycle. This results in an extreme time discrepancy that persists even after booting into Windows.
To identify this issue:
- Enter BIOS/UEFI setup immediately after booting the device.
- Check the hardware clock against a known correct time source (e.g., mobile phone or wall clock).
- If the date is set to an old year (e.g., 2013), the CMOS battery is likely dead.
Misconfigured Windows Time Service
The Windows Time service (w32tm) may be stopped, misconfigured, or unable to synchronize with the configured NTP server. This can happen if:
w32tmis not running.- The service startup type is set to Manual instead of Automatic.
- The device has never synchronized time since first boot (common in offline deployments).
Network Firewall Blocking NTP Traffic
If the network firewall blocks UDP port 123 (time.windows.com or the configured NTP server), the Windows Time service cannot synchronize the system clock. This is particularly common in environments with strict egress filtering.
Mixed UTC/Local-Time BIOS Settings
Some devices may have conflicting time zone settings where:
- The hardware clock is set to UTC but the OS expects local time, or vice versa.
- This mismatch causes the system clock to drift significantly after each boot cycle.
Fix Procedure
- Check Windows Time Service Status:
Get-Service w32tm | Select Name, Status, StartTypeIf the service is not running or set to Manual, start it and configure it to start automatically:
Set-Service -Name w32tm -StartupType Automatic - Force NTP Synchronization:
Warning: Manually setting the system time can cause issues with Kerberos authentication. Only proceed if automated synchronization fails.Run as Administrator:
w32tm /resync /force - Test NTP Connectivity:
Test-NetConnection -ComputerName time.windows.com -Port 123If connectivity fails, check firewall rules or configure an alternative NTP source:
w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:YES /update - Replace CMOS Battery:
TIP: Most motherboards use a standard CR2032 battery. Replace while the device is powered off and grounded.After replacement:
- Enter BIOS/UEFI setup and set hardware clock to current date/time.
- Boot into Windows and force NTP synchronization as above.
- Configure Domain Time Source:
For domain-joined devices, ensure the PDC emulator is correctly synchronized:
Get-WinEvent -LogName "Microsoft-Windows-Time-Service%4Operational" -FilterXPath "*[System[(EventID=201)]]" - Verify Time Zone Settings:
Ensure the hardware clock is set to UTC if configured in BIOS, or local time otherwise. Check:
Get-TimeZone
Error Code Variants
| Error Code | Description | Distinguishing Factors |
|---|---|---|
| 0x80CF0437 | System clock out of sync with Intune service. | Occurs during enrollment; linked to time validation failures in OAuth/JWT tokens. |
| 0x80CF0436 | Device certificate validation failure. | Similar error code but caused by invalid or expired device certificates, not time sync issues. |
| 0x80CF0438 | Enrollment token validation failed. | Occurs when the enrollment token is invalid or tampered with; unrelated to system clock. |
Verification
To confirm the fix:
- Check Intune management extension logs for successful sync:
'Token expired'should no longer appear. - Verify Windows Time service status:
w32tm /query /statusLook for a recentLast Successful Sync Time. - Attempt enrollment again through the Company Portal or Settings app. It should complete successfully without error code 0x80CF0437.
Prevention
To avoid recurrence:
- Implement a baseline policy to ensure Windows Time service is running and configured correctly:
./Device/Vendor/MSFT/Policy/Config/ADMX-TimeService/EnableWindowsTimeSvc - Schedule regular time synchronization checks using PowerShell:
Schtasks /Create /SC DAILY /TN "Time Sync Check" /TR "powershell.exe -Command 'w32tm /resync'" - Monitor CMOS battery health in devices with replaceable batteries.
- Ensure network firewalls allow outbound UDP port 123 to NTP servers.