WINDOWS时间服务启动失败的原因

WINDOWS启动时间服务，基本上都启动不了，试了多台电脑。提示信息如下：

net start w32time

The Windows Time service is starting.The Windows Time service could not be started.A system error has occurred.System error 126 has occurred.The specified module could not be found.

试了许多方法，最有效的是这个：

w32tm /debug /disable

w32tm /unregister

w32tm /register

net start w32time

w32tm /resync

我估计第一条命令是最重要的。不能启动可能和日志文件有关，关掉调试，不写日志，问题自然解决。

以下是查到的一堆资料，供参考：

You might check your registry.

1. Navigate to the following Registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
2. Double click on the TYPE key and remove the extra space after the value.Extra spaces entered after the Value are shown as aue selected text.
3. Restart the computer. bl

sc triggerinfo w32time start/networkon stop/networkoff

This command will fix the triggers for the Windows Time service and it should launch automatically when it’s supposed to, fixing your problem.

w32tm /unregister

https://appuals.com/windows-time-service-wont-start/

"Windows could not start the Windows Time Service on Local Computer. Error 2: The system cannot find the file specified".

net stop w32time

w32tm /unregister

w32tm /register

net start w32time

w32tm /resync

This error occurred in five windows servers 2008.Error 2: The system cannot find the file specified ... Windows Event Log service could not start.I tried the following steps:1) Link Server 2008 Event log restore

2) Full control for administrator user in the folder

C:\Windows\System32\winevt\Logs3

Delete files in the

C:\Windows\System32\winevt\Logs

Plz i need help.I did a test, and I believe it is a hotfix that was applied. Now the question is what is the hotfix that is causing this problem.

I met the exact problem yesterday, and tried the  3 options as you mentioned, but the problem remained.

However, with the help of procmon, it turned out that the issue was caused by an incorrect registry entry at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Parameters\ServiceDll

Event Log service by default will look at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\ServiceDll for the service dll to start the service, however, when "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Parameters" presents, it will look for ServiceDll underneath the "Parameters" sub key.

And in my case, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Parameters\ServiceDll was referring to an empty string, so Event log service cannot find the service dll file to start the service.

So, I just deleted the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Parameters, and after that, Event log service starts correctly.Hope this helps.

Deleting 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs

fixed my problem.

Story:

Nothing here solved my problem.

I run process monitor to check for file errors by svchost and found some dlls that were missing.

I looked in the entire registry for those dlls and found they were all mentioned only in the infamous AppInit_DLLs entry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows

Deleting the value in AppInit_DLLs fixed my problem.

The DLLs were non existent nvidia drivers from a previous video card.  The uninstall didn't remove this value it seems.

Strangely it seems AppInit_DLLs are DLLs that are loaded in EVERY new process.  The load failure only made start service service fail.... windows and all the programs I've been using were working just fine.

Hope this helps some of you.