Event ID 1108 Event logging service encountered an error

If Event ID 1108: The event logging service encountered an error continues to bother you, this post may help you. When this error occurs, your computer may behave abnormally or show a blue screen of death. A notification will also appear with the journal name, source, event ID, etc. Fortunately, there are a few simple steps you can take to fix this error.

This event is generated when the Event Logging service encounters an error while processing an incoming event. It is usually generated when the logging service is unable to correctly log an event to the event log, or some parameters were not passed to the logging service to log the event correctly. You will usually see a defective or incorrect event by 1108.

Event ID 1108 The event logging service encountered an error

What causes Event ID 1108?

Event ID 1108 often occurs when the logging service needs help to write the event correctly to the event log, or when certain parameters have not been provided to the logging service. You will usually see a defective or incorrect event by 1108.

Fix event ID 1108, the event logging service encountered an error

Follow these suggestions if The Event Logging service encountered an error while processing an incoming event on your Windows device:

  1. Restart the Windows Event Log service
  2. Make changes in the registry editor
  3. Remove the subkey for the DFSR service
  4. Perform a system restore
  5. Repair Windows using the installation media

Now let’s look at them in detail.

1]Restart the Windows Event Log service

event registration service

Before you start using various troubleshooting methods to fix this error, try restarting the Windows Event Log service to fix the problem. Here’s how you can do it:

  1. Click Windows key + R to open Run dialog box.
  2. Type services.msc and hit Sign in.
  3. Search Windows Event Log Serviceright click on it and select Restart.

2]Make changes in the registry editor

regedit event start

You can also fix event ID 1108 by making some changes in the registry editor. This will verify that the event log service is enabled. Here’s how:

Click Windows key + R to open Run dialog box.

Type regedit and hit Sign in.

After opening the registry editor, navigate to the following path:

HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > EventLog

Right-click Start in the right pane and select Modify.

Install Data value how 1 and click Good to save the changes.

Create a restore point as one mistake in the editor can crash your device.

3]Remove subkey for DFSR service

This problem can also occur if the connection registry value in the DFSR service is invalid. To fix this, you need to follow these steps:

Type regedit and hit Sign in.

After opening the registry editor, navigate to the following path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfsr\Restore

There will be a subkey called year-date-time with which the recovery was made with two values. One of these values ​​will be the network name used to perform the remote restore.

Now backup and delete restore connect

Once complete, open Services and restart DFS Replication Service.

Once done, reboot your device and Event ID 1108 should now be fixed.

4]Perform a system restore

Performing a system restore will restore the device’s default settings to a point where the problem did not exist. It will also restore your Windows environment by reinstalling the files and settings saved in the restore point. Here’s how to perform a system restore. Note that this can only be done if you have previously created a system restore point.

Read: The Windows Event Log service is not starting or is not available.

5]Repair Windows using installation media

repair Windows settings on the computer

If none of these methods worked for you, repair Windows using the installation media. Here’s how you can do it:

  1. Download the Windows ISO and create a bootable USB or DVD drive
  2. Boot from media and select Repair your computer.
  3. Under Advanced troubleshooting, select Advanced options > Troubleshooting.
  4. Now click on Startup repair and follow the instructions on the screen.

Fix: Failed to start Task Scheduler, Event ID 101

What is a Microsoft Security Audit?

Security auditing is a feature of Microsoft Windows that helps keep computers secure on private and corporate networks. It analyzes user activity, performs foreign analysis, investigates error codes, and resolves them. With Microsoft Security Auditing, users can implement security policies in their environment to meet corporate and government requirements.

What is Event ID 40?

Event ID 40 indicates that the logon event encountered errors while trying to apply some policy settings. To fix this, change the Group Policy settings and clear the syslog events that cause this error. If that doesn’t work, consider updating your motherboard’s BIOS.

How to check login history in Windows Server?

When a user logs in or out, the information is written to an event in the Windows Security Log. To view the history, open Event Viewer, go to Windows Logs, and select Security. You will find detailed information about all events and tasks performed recently on your device.

Can TeamViewer track activity?

A built-in report log captures all remote session activity and management activity. Everything, including who did what, when and for how long for each incoming and outgoing connection, is tracked in the report log.