Fix for Event Log Service Startup Error 1079

When you start the Event Viewer, the following error message may be shown.

Event Log service is unavailable. Verify that the service is running.

Any attempts to start the Event Log service results in the following error:

Windows could not start the Windows Event Log service on Local Computer.
Error 1079: The account specified for this service is different from the account specified for other services running in the same process.

As the Windows Event Log service isn’t running, starting Task Scheduler results in the following error:

Windows could not start the Task Scheduler service on Local Computer.
Error 1068: The dependency service or group failed to start.

Fix for Event Log Service Startup Error 1079

This problem was reported by one of our readers via email, and it has been fixed. Service startup error 1079 occurs if the logon account for the service is incorrectly set. Usually, this is resolved by fixing the service logon account (via the Log On tab in the Property sheet) via the Services MMC (services.msc)

This can’t be done in the case of Windows Event Log, where the Log On tab controls remain grayed out by default.



So, we need to alter the ObjectName registry value in the service’s registry branch:

  1. Start the Registry Editor (regedit.exe) and navigate to the following branch:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog
  2. Double-click ObjectName
  3. Set its data as “NT AUTHORITY\LocalService
  4. Restart Windows.

This fixes the event log service error 1079.


One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

9 thoughts on “Fix for Event Log Service Startup Error 1079”

  1. I have the problem described above on my Windows 7 system but when I followed the steps described to fix it, I found the registry setting for the eventlog was already set as described, but I still have the problem.

    The problems seem to be spreading, now I can’t run disk defrag or windows update. HELP

  2. I have have the same problem and get the same errors described by Ramesh. I followed the same steps and as happened to Dana, I found the registry setting for the eventlog was already set as described, but I still have the problem.

    I still can run Disk Defrag tho. But the errors still there.:(

    MY OS is Windows Vista 64bit

    What to do next???

  3. I had a problem with Task Scheduler. I was unable to create a local basic task because access was grayed out. I downloaded the zip file, ran the Win 7 fix, restarted and now I have access.

    Additionally, I have had to manually start Windows Audio and all the dependent services (ever since a Microsoft engineer fixed other problems on my ThinkPad a few weeks ago but those issues have been fixed too it seems.

    Thank goodness for Windows techies who are willing to share!

  4. I use this script to fix Audio Service not starting, and RAS service to fix Sonicwall VPN connection issues. This script is like gold!

    Now if only I knew what kept replacing the logon information

  5. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\audiosrv

    change key regdword “start” to value 1

Comments are closed.