Skip go content

Windows Time

Windows ServiceMicrosoft Corporation

Dem still dey call am w32time, windows time service, ntp

WindowsMicrosoft

Di Windows time service wey dey keep di clock in sync with domain or NTP source.

Wetin you need know

Dis one dey keep di clock honest. Kerberos and certificates care even if you no care.

W32Time dey talk to NTP or di domain hierarchy. Clock wey drift dey break sign-in and TLS long before you notice di tray time. E no be Windows Update.

Important?
Yes, for logon and certificates
High CPU?
Rare. Check di clock source
E safe to disable?
Clock drift go surprise you later
Feex tok say
If di clock jump afta CMOS battery die, I go start W32Time and resync. I no go disable di service to "stop network".

Wetin dis service dey do?

Display name: Windows Time. Service name: W32Time.

E dey sample time source, dey slew or step di clock, and dey publish status. PCs wey join domain usually dey follow domain hierarchy instead of time.windows.com.

History on Windows

Still present

W32Time come out with Windows 2000 when Microsoft add Kerberos and need clocks wey align well. E don remain di Windows Time service through XP, Vista, Windows 7, and current Windows 10 and Windows 11. Di service name na still W32Time.

Windows Time service history
First come out as W32Time Windows 2000 (2000)
Still present Yes, including Windows 10 and Windows 11
Discontinued No

Why Windows need am?

Kerberos tickets, TLS, and file timestamps dey assume say di clock close. Skew of five minutes dey enough to fail domain logon.

When e dey run?

E dey poll on interval. You no suppose see constant high CPU. Spike afta resume from sleep na resync.

E suppose dey run always?

Automatic or Manual (Trigger Start) both dey show on client SKUs. Disabled mean say di clock only dey waka with hardware RTC.

I fit disable am?

Only if you accept drift

To disable W32Time dey stop NTP and domain sync. Set di clock by hand if you must test. Turn am back on before you join domain or use VPN wey dey check time.

Wetin go happen if I disable am?

Di clock go drift. Domain logon and some certificates go fail. Scheduled tasks wey assume local time go still run, but at di wrong UTC.

Process host

W32Time commonly dey run inside svchost.exe. See svchost.exe.

Dependencies

Windows Time dependencies
Depend on RPC
Used by Domain join, Kerberos, and anything wey trust di OS clock

Resource behavior

CPU
Low
Network
Short NTP polls
Disk
Low
Memory
Small

Common wahala dem

Clock dey off afta dead CMOS battery

Fix di battery, den w32tm /resync. Di service no fit invent good RTC.

VM time vs host

Hypervisors still dey inject time. Two sources fit fight. Dat na VM setting, no be reason to delete W32Time.

How to troubleshoot

Safe steps first.

w32tm /query /status

Dey show di source. time.windows.com versus di domain PDC na di usual split.

No set di clock every hour by hand

Turn di service back on.

Technical details

Technical details
W32Time technical details
Display name Windows Time
Service name W32Time

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Dis article make sense to you?