Windows could not start the Windows event log service on local computer
I was trying to setup a new Share Name for the C: Drive and found that I needed to "Take Ownership" of the drive. This was my downfall (at least I think this is how I caused the problem). Now when I restart my machine quite a few of the Automatic Services do not start. They were all Dependent on the Event Viewer.I put TrustedInstaller back as the Owner of the C: Drive but I still get the same error:Windows could not start the Windows event log service on local computererror 4201: The instance name passed was not recognized as valid ba a WMI data providorI need the Event Viewer to be able to start can anyone assist? JPMTJR
December 22nd, 2009 12:15pm

The Services have a lot of connections and dependencies on each other. Usually when one fails, you will find others that have also failed. There are several threads on this forum dealing with this particular issue. Go to the following link. Re: Event Log stopped working - Error 1747 : The Authentication Service is Unknown - TechNet Forums: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2790941&SiteID=17 Scroll down to the first message from Al Oliveira for the fix that seemed to work for a lot of other users. Come back to this thread and let us know if this helps.However, many more ended up just reinstalling (try repair first).MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2009 4:19pm

Besides Cdobbs's suggestion, you can also try the following steps. 1. Perform a Clean Boot to check the result. If the issue disappears in the Clean Boot environment, we can use a 50/50 approach to quickly narrow down which entry is causing the issue. 2. Save the following key on another Windows 7 machine which Event Log service is started normally, and then copy it to the problematic machine. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog Thanks,Novak
December 23rd, 2009 5:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics