An error occured synchronizing windows with


Okay so I've tried stopping/registering the win32tm service on this Windows Server 2008 Enterprise Computer.

C:\Users\Administrator>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.

C:\Users\Administrator>w32tm /unregister
The following error occurred: Access is denied. (0x80070005)

C:\Users\Administrator>w32tm /unregister
W32Time successfully unregistered.

C:\Users\Administrator>w32tm /register
W32Time successfully registered.

C:\Users\Administrator>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.

(Source :

And I get this error from the Date and Time, Internet Time tab (After also following the steps here).


I've even tried the Atomic Time Clock Worldtimeserver and I get the error The following error occurred: The specified module could not be found. (0x8007007E).

I've also disabled the Windows Firewall, that might of been blocking the synchronization.

windows firewall

I've done a file scan with sfc /scannow that came back with no errors.

C:\Users\Administrator>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.


But I'm not having much luck. Is there anyway lo possibly solve this? or is the servers unsupported? because the software is from 2008? (I really don't know :/), My ping result to


Pinging [] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

And tracert result


Tracing route to [] over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 2 32 ms 31 ms 32 ms []

3 31 ms 32 ms 31 ms [] 4 31 ms 31 ms 31 ms [] 5 31 ms 31 ms 30 ms [ 09] 6 167 ms 166 ms 166 ms []

7 175 ms 175 ms 175 ms [ 43] 8 177 ms 180 ms 176 ms [ 6] 9 205 ms 205 ms 204 ms [ 1] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 ^C

And nslookup

Server:  UnKnown

Non-authoritative answer:
asked on Server Fault Oct 11, 2012 by Killrawr • edited Mar 25, 2020 by Glorfindel

4 Answers


Its a little late, but you often get that error if your clock is wrong. Shockingly enough, you need to set the clock to a nearly correct time for it to synchronise properly.

Its probably so that if you DID get time related wierdness regularly , you will get off your rear and work out why its happening - its often due to a dead or weak bios battery.

answered on Server Fault Oct 11, 2012 by Journeyman Geek

Here's a better and pretty standard option... use the public NTP Pool or the USNO Master Clock for time synchronization. If you change your time clock source do you still have the same problem? Have you tried testing any external time source manually?

answered on Server Fault Oct 11, 2012 by Brent Pabst

Is this server part of a domain? It's best practice to sync from the domain environment.

Is it a Hyper-V virtual machine? If it is you need to make sure you have the "Time Synchronization" Integration service disabled.

When you run:

W32tm /query /configuration

Do you see all [local] settings? If not that may be an indicator that Group Policy is setting the time settings.

Have you tried running the commands to sync from an external time source manually?

W32tm /config /syncfromflags:manual /manualpeerlist:""
W32tm /config /reliable:yes
W32tm /config /update
Net stop w32time && Net start w32time (Alternatively, reboot if you can)
W32tm /resync /rediscover
answered on Server Fault Oct 11, 2012 by brett

I downloaded and it now synchronizing

answered on Server Fault Oct 11, 2012 by Killrawr

User contributions licensed under CC BY-SA 3.0