Windows Time Service cannot be started.

In some cases, the Windows Time Service cannot be started due to the use of optimization tools, cleaning assistants, or Trojans, and the system clock cannot be synchronized with the Internet time server.

For the problem that Windows clock cannot be synchronized, the solution provided on the network is basically:

1. Run cmd to enter the command line, and then type

W32tm/register <br/> the correct response is: w32time successfully registered. </P> <p>

2. If the preceding step is correct, Use Net start "Windows Time" or net start w32time to start the service. You can also go to computer management to directly start the Windows Time Service.

3. If the time synchronization problem occurs on the server address, you can copy the following text, create a new text file and save it as the reg file, and double-click to import the registry:

Windows Registry Editor Version 5.00 <br/> [HKEY_LOCAL_MACHINE/software/Microsoft/Windows/CurrentVersion/datetime/servers] <br/>@= "6" <br/> "1" = "time.windows.com" <br/> "2" = "time.nist.gov" <br/> "3" = "time-nw.nist.gov" <br/> "4" = "time-a.nist.gov" <br/> "5" = "time-b.nist.gov" <br/> "6" = "210.72.145.44" </P> <p>

Double-click the time below the system tray, enter the IP address of the National Time Service Center Server (210.72.145.44) in the address bar of the server, and click "OK" to save it.

The above content is about the Internet.

Here, we need to emphasize and solve the problem that the first command above: w32tm/register is not always successful. I have encountered this situation several times. Sometimes, when you use the w32tm/register to re-register the time component, you will be prompted to reject access and fail to complete registration, even in safe mode. In this case, if you try to start the Windows Time Service, you will be prompted that the module cannot be found and the startup fails. Of course, in this case, clock synchronization cannot be used.

 

).

Run regedit to open the registry and locate HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time. We can see several key projects. The correct ones should be:

Windows Registry Editor Version 5.00 </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time] <br/> "displayname" = "@ % SystemRoot % // system32/ /w32time. DLL,-200 "<br/>" ImagePath "= hex (2): 25, 00, 53,00, 79,00, 00, 6d, 00, 6f, 00, 6f, 00,/<br/>, 00, 5C, 00, 5C, /<br/>, 00, 6f, 00, 2e, 78, 00, 00, 2d, 00, /<br/> 6B, 20, 00, 4C, 00, 6f, 00, 6C, /<br/>, 00, 00 <br/> "Description" = "@ % SystemRoot % // system32 // w32time. DLL,-201 "<br/>" objectname "=" nt authority // LocalService "<br/>" errorcontrol "= DWORD: 00000001 <br/> "start" = DWORD: 00000003 <br/> "type" = DWORD: 00000020 <br/> "servicesidtype" = DWORD: 00000001 <br/> "requiredprivileges" = hex (7):,/<br/>, 69,, 69, 00, 6C, 68, 00,/<br/>, 00, 4E, 00, 6f,/<br/>, 00, 6C,, 00,/<br/>, 00, 6C,/<br/>, 69, 00, 6C,, 00,/<br/>, 00, 6d, 00, 6C,, 65,/<br/>, 65, 00, 00 <br/> "failureactions" = HEX: 80, 51, 00, 00, 00, 00,, 00, 00,/<br/>, 01, 60, EA, 00, 00, C0, D4, 00, 00, 00,00 </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/config] <br/> "frequencycorrectrate" = DWORD: 00000004 <br/> "polladjustfactor" = DWORD: 00000005 <br/> "largephaseoffset" = DWORD: 02faf080 <br/> "spikewatchperiod" = DWORD: 00000384 <br/> "localclockdispersion" = DWORD: 0000000a <br/> "holdperiod" = DWORD: 00000005 <br/> "phasecorrectrate" = DWORD: 00000001 <br/> "updateinterval" = DWORD: 00057e40 <br/> "eventlogflags" = DWORD: 00000002 <br/> "announceflags" = DWORD: 0000000a <br/> "timejumpauditoffset" = DWORD: 00007080 <br/> "minpollinterval" = DWORD: 0000000a <br/> "maxpollinterval" = DWORD: 0000000f <br/> "maxnegphasecorrection" = DWORD: 127d2f0 <br/> "maxposphasecorrection" = DWORD: 127d2f0 <br/> "maxallowedphaseoffset" = DWORD: 00000001 </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/parameters] <br/> "servicedll" = hex (2): 25, 00, 79,00,, 6d, 00, 6f, 00, 6f,/<br/>, 00, 00, 5C,, 65, 00, 6d, 32, 00, 5C, 00,/<br/>, 00, 2e,, 64, 00, 6C, 00, 6C, 00 <br/> "servicemain" = "svchostentry_w32time" <br/> "servicedllunloadonstop" = DWORD: 00000001 <br/> "type" = "NTP" <br/> "ntpserver" = "time.windows.com, 0x9 "</P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/security] <br/>" security "= HEX: 01,00, 04,80, 84,00,, 90, 00, 00, 00, 00, 00, 00, 02,/<br/>, 00, 00, 01,, 00, 12, 00,/<br/>, FF, 01, 00, ,/<br/>, 00, 00, 8D, 01, 01, 00, 00, 00, 00, 00, 00, 00, 00, 00, /<br/> 8D, 01,02, 00,01, 01,00, 00,00, 00,00, 05,06, 00,00, 00,00, 00,14, 00, 9d, 01,02, 00,01,/<br/> 01,00,, 01, 01,/<br/>, 05, 00,00 </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/timeproviders] </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/timeproviders /ntpclient] <br/> "dllname" = hex (2),, 79, 65, 00, 6d, 00, 5C,/<br/>, 33, 00, 00, 6d, 00000001, 65, 00, 2e, 00, 6C, 00, 6C, 00 <br/> "enabled" = DWORD: <br/> "inputprovider" = DWORD: 00000001 <br/> "allownonstandardmodecombinations" = DWORD: 00000001 <br/> "crosssitesyncflags" = DWORD: 00000002 <br/> "resolvepeerbackoffminutes" = DWORD: 0000000f <br/> "resolvepeerbackoffmaxtimes" = DWORD: 00000007 <br/> "compatibilityflags" = DWORD: 80000000 <br/> "eventlogflags" = DWORD: 00000001 <br/> "largesampleskew" = DWORD: 00000003 <br/> "specialpollinterval" = DWORD: 00093a80 <br/> "specialpolltimeremaining" = hex (7, 6d, 65, 00, 2e, 69, 00, 6e,/<br/>, 64, 00, 6f, 00, 00, 2e, 00, 6f, 00, 6d, 00, 2c, 00,/<br/>,, 00, 00,/<br/>, 00 </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/timeproviders/ntpserver] <br/> "dllname" = hex (2): 25, 00, 79,00, 6d, 00, 00, 6f, 00, 00,/<br/>, 25, 00, 5C,, 65, 00, 6d, 00, 5C,/<br/>, 00, 00, 00, 2e, 00000000, 00, 6C, 00, 6C, 00 <br/> "enabled" = DWORD: <br/> "inputprovider" = DWORD: 00000000 <br/> "allownonstandardmodecombinations" = DWORD: 00000001 <br/> "eventlogflags" = DWORD: 00000000 <br/> "chainentrytimeout" = DWORD: 00000010 <br/> "chainmaxentries" = DWORD: 00000080 <br/> "chainmaxhostentries" = DWORD: 00000004 <br/> "chaindisable" = DWORD: 00000000 <br/> "chainloggingrate" = DWORD: 0000001e </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/timeproviders/vmictimeprovider] <br/> "enabled" = DWORD: 00000001 <br/> "inputprovider" = DWORD: 00000001 <br/> "dllname" = hex (2):, 6d,, 52, 00, 6f, 00, 6f, 00,/<br/>, 00, 5C, 6d,, 32, 00, 5C,/<br/> 00, 6d, 00, 00, 6f,, 69, 00,/<br/> 64, 00, 2e, 00, 6C, 00, 00 </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/timeproviders/vmictimeprovider/parameters] </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services /w32time/triggerinfo] </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/triggerinfo/0] <br/> "type" = DWORD: 00000003 <br/> "action" = DWORD: 00000001 <br/> "guid" = HEX: BA, 0a, E2, 1C, 51,98, 1d, de, b7, 66, E8, 09 </P> <p> [HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/triggerinfo/1] <br/> "type" = DWORD: 00000003 <br/> "action" = DWORD: 00000002 <br/> "guid" = HEX: 6e, 51, AF, DD, C2, 58,66, 74, C3, b6, 15, D4, 2e, A1

If your computer has the above problems, you will find that there are several fewer items in the registry, and when you try to add the missing registry, you may find that the registry key is not added!

Right-click the HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time sub-key and select "permission". In the displayed dialog box, you may see "group and user name, there is only one "w32time" item, and the problem lies here! As you can see, the w32time registration item does not have the Administrator permission. Therefore, when we perform the preceding operations, all of them fail.

If the cause of the error is found, the solution is simple. In the permission dialog box, click the "advanced" button. In the displayed dialog box, click "add" in the "Permissions" column ", in the "select user or group" dialog box, click "advanced". A "select user or group" dialog box is displayed. Click "Search now" on the right ", some users or groups on the local machine are listed below. Select the corresponding user or group shown in, and set the corresponding permissions (if you do not know much about it, you can select all permissions ). Select "replace all sub-object permissions with the permissions inherited from this object" in ".

Set HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time and its subitem permissions in sequence according to the preceding instructions. Then, refresh the registry and you will find that there are more items in the subitem. Note that, in the subitem HKEY_LOCAL_MACHINE/system/CurrentControlSet/services/w32time/timeproviders, there should be three items: ntpclient, ntpserver, and vmictimeprovider. If there is another item similar to XYZ, delete it.

After the registry is set up, perform the first steps in sequence, that is, run w32tm/register, and then start the Windows Time Service. If it still fails, restart the computer and run the preceding command after the computer is fully started.

Generally, the above method can solve the Windows time synchronization problem.