ANAVEM
Languagefr
Fix Windows Event Log Error 36887 – Windows 10/11 2026
Fix Guide36887Windows Event Log

Fix Windows Event Log Error 36887 – Windows 10/11 2026

Windows Event Log error 36887 occurs when the Event Log service fails to initialize or access log files. This comprehensive guide provides five proven methods to restore Event Log functionality on Windows 10 and 11.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
March 17, 2026 12 min 0
36887Windows Event Log 5 methods 12 min
Instant Solution

The fastest solution is to restart the Windows Event Log service. Open Services (services.msc), locate Windows Event Log, right-click and select Restart. If this fails, run sfc /scannow in an elevated Command Prompt to repair corrupted system files.

Understanding Windows Event Log Error 36887

Windows Event Log error 36887 represents a critical system service failure that affects the core logging infrastructure of Windows 10 and Windows 11 systems. This error typically manifests when the Windows Event Log service encounters initialization problems, permission conflicts, or corrupted system files that prevent proper event logging functionality.

The Event Log service is fundamental to Windows operation, recording system events, application errors, security audits, and performance data that administrators and troubleshooting tools rely on. When error 36887 occurs, it can cascade into broader system stability issues, failed Windows Updates, and application crashes that depend on event logging capabilities.

This error has become more prevalent in 2026 following recent Windows updates that modified event logging architecture for enhanced security and performance. The issue particularly affects systems that have undergone major feature updates, experienced disk space constraints, or have been infected with malware targeting system services.

Understanding the root causes and implementing the correct fix is crucial for maintaining system stability and ensuring proper logging functionality for both built-in Windows components and third-party applications that rely on the Windows Event Log infrastructure.

Related: Fix Windows Event ID 41 – Unexpected Shutdown Error 2026

Related: Fix Service Control Manager Error 7023 – Windows 10/11 2026

Diagnostic

Symptoms

  • Event Viewer fails to open or displays blank entries
  • Applications report inability to write to event logs
  • System performance monitoring tools show missing data
  • Error messages stating "The Event Log service is unavailable"
  • Windows Update may fail due to logging issues
  • Third-party applications crash when attempting to log events
  • System stability issues and unexpected shutdowns
Analysis

Root Causes

  • Corrupted Event Log service files or registry entries
  • Insufficient permissions on Event Log directories
  • Damaged or full event log files (.evtx files)
  • Windows Update installation conflicts
  • Third-party security software interfering with logging
  • Disk space issues preventing log file creation
  • Registry corruption affecting Event Log service configuration
  • Malware infection targeting system logging capabilities
Resolution Methods

Solutions

01

Restart Windows Event Log Service

The Event Log service may have stopped or become unresponsive. Restarting it often resolves temporary issues.

  1. Press Windows + R, type services.msc and press Enter
  2. Scroll down and locate Windows Event Log
  3. Right-click on the service and select Properties
  4. Note the current status. If stopped, click Start
  5. If running, click Stop, wait 10 seconds, then click Start
  6. Set Startup type to Automatic
  7. Click Apply and OK

Alternative command line method:

net stop eventlog
net start eventlog

Verification: Open Event Viewer by pressing Windows + X and selecting Event Viewer. Navigate to Windows LogsSystem and verify recent entries are visible.

02

Run System File Checker and DISM

Corrupted system files often cause Event Log service failures. SFC and DISM can repair these files.

  1. Press Windows + X and select Windows Terminal (Admin)
  2. Run the DISM command first to prepare the system:
DISM /Online /Cleanup-Image /RestoreHealth
  1. Wait for completion (may take 15-30 minutes)
  2. Run System File Checker:
sfc /scannow
  1. Restart your computer after both commands complete
  2. Check the SFC log for details:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
Pro tip: If SFC finds violations but cannot fix them, run sfc /scannow again after DISM completes.

Verification: After restart, open Event Viewer and check if new system events are being logged properly.

03

Reset Event Log File Permissions

Incorrect permissions on Event Log directories can prevent the service from functioning. This method resets permissions to default values.

Warning: Always run these commands as Administrator to avoid permission errors.
  1. Open Windows Terminal (Admin)
  2. Navigate to the Event Log directory:
cd /d %SystemRoot%\System32\winevt\Logs
  1. Take ownership of the Logs folder:
takeown /f . /r /d y
  1. Reset permissions using icacls:
icacls . /reset /t /c /l
  1. Grant specific permissions to Event Log service:
icacls . /grant "NT SERVICE\EventLog":F /t
icacls . /grant "SYSTEM":F /t
icacls . /grant "Administrators":F /t
  1. Restart the Event Log service:
net stop eventlog && net start eventlog

Verification: Run icacls %SystemRoot%\System32\winevt\Logs to confirm permissions are correctly set.

04

Clear and Rebuild Event Log Files

Corrupted .evtx files can cause the Event Log service to fail. This method safely clears and rebuilds the log files.

Warning: This method will clear existing event logs. Export important logs before proceeding.
  1. Stop the Event Log service:
net stop eventlog
  1. Navigate to the Event Log directory:
cd /d %SystemRoot%\System32\winevt\Logs
  1. Create a backup folder and move existing logs:
mkdir C:\EventLogBackup
move *.evtx C:\EventLogBackup\
  1. Clear the Event Log registry cache:
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\EventLog" /v "File" /f
  1. Restart the Event Log service:
net start eventlog
  1. Rebuild the Event Log database:
wevtutil el | ForEach-Object {wevtutil cl $_}

Verification: Open Event Viewer and confirm that new log files are being created and events are being recorded.

05

Registry Repair and Service Reconfiguration

Deep registry corruption may require manual repair of Event Log service configuration.

Warning: Back up your registry before making changes. Incorrect registry modifications can cause system instability.
  1. Create a registry backup:
reg export HKLM\SYSTEM\CurrentControlSet\Services\EventLog C:\EventLog_Registry_Backup.reg
  1. Open Registry Editor as Administrator:
regedit
  1. Navigate to: HKLM\SYSTEM\CurrentControlSet\Services\EventLog
  2. Verify the following values exist and are correct:
  3. DisplayName (REG_SZ): Windows Event Log
  4. ImagePath (REG_EXPAND_SZ): %SystemRoot%\System32\svchost.exe -k LocalServiceNetworkRestricted -p
  5. Start (REG_DWORD): 2 (Automatic)
  6. Type (REG_DWORD): 32
  7. If any values are missing or incorrect, right-click in the right pane, select New, and create the appropriate value type
  8. Navigate to: HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Parameters
  9. Ensure ServiceDll (REG_EXPAND_SZ) is set to: %SystemRoot%\System32\wevtsvc.dll
  10. Close Registry Editor and restart the computer

Verification: After restart, check Services.msc to confirm the Event Log service starts automatically and Event Viewer functions normally.

Validation

Verification

To confirm the Event Log service is working correctly:

  1. Open Event Viewer by pressing Windows + X and selecting Event Viewer
  2. Navigate to Windows LogsSystem
  3. Verify recent events are visible with current timestamps
  4. Check service status: sc query eventlog
  5. Test event creation: eventcreate /T INFORMATION /ID 1000 /L SYSTEM /SO TestApp /D "Event Log test message"
  6. Refresh Event Viewer and confirm the test event appears
  7. Verify application logs are also functioning by checking Windows LogsApplication
If it still fails

Advanced Troubleshooting

If the above methods didn't resolve error 36887:

  1. Check disk space: Ensure at least 1GB free space on the system drive. Event logs require adequate space to function.
  2. Scan for malware: Run Windows Defender full scan or use Microsoft Safety Scanner to check for malware targeting system services.
  3. Disable third-party security software temporarily: Some antivirus programs interfere with Event Log service. Temporarily disable and test.
  4. Check Windows Update: Install pending updates as Microsoft regularly releases fixes for Event Log issues.
  5. Run Windows Memory Diagnostic: Press Windows + R, type mdsched, and restart to check for memory issues.
  6. Perform System Restore: If the error started recently, restore to a point before the issue began.
  7. Reset Windows (keep files): As a last resort, use SettingsUpdate & SecurityRecoveryReset this PC with the "Keep my files" option.
Pro tip: Monitor Event Viewer regularly after fixing to ensure the issue doesn't recur. Set up custom views for critical system events.

Frequently Asked Questions

What does Windows Event Log error 36887 specifically indicate?+
Error 36887 indicates that the Windows Event Log service failed to initialize properly, typically due to corrupted service files, permission issues, or damaged event log databases. This error prevents the system from recording events, which can affect system monitoring, troubleshooting capabilities, and applications that depend on event logging. The error often appears in conjunction with Event Viewer being unable to display logs or applications reporting logging failures.
Can error 36887 cause other Windows services to fail?+
Yes, error 36887 can cause cascading failures in other Windows services and applications. Many system components and third-party applications depend on the Event Log service for recording operational data, errors, and security events. When the Event Log service fails, Windows Update may fail to install updates, security software may not function properly, and system performance monitoring tools will lose functionality. Additionally, some services that require event logging for compliance or audit purposes may stop working entirely.
Is it safe to delete event log files to fix error 36887?+
Deleting event log files (.evtx files) is generally safe from a system stability perspective, but you will lose historical event data that may be valuable for troubleshooting or compliance purposes. Before deleting, always create backups of important logs, especially Security and System logs. The recommended approach is to stop the Event Log service first, move the files to a backup location rather than deleting them, then restart the service to allow Windows to create fresh log files. This preserves your data while resolving corruption issues.
Why does error 36887 occur more frequently after Windows updates?+
Windows updates can trigger error 36887 because they modify system files, registry entries, and service configurations related to event logging. Major feature updates particularly affect the Event Log service as Microsoft enhances security and performance features. Updates may also change file permissions, relocate log files, or modify service dependencies. Additionally, if an update process is interrupted or fails partially, it can leave the Event Log service in an inconsistent state, requiring manual repair using the methods outlined in this guide.
How can I prevent error 36887 from recurring after fixing it?+
To prevent error 36887 from recurring, maintain adequate free disk space (at least 1GB on the system drive), keep Windows updated with the latest patches, run regular system file checks using SFC and DISM, avoid forcefully shutting down the computer during updates, and ensure third-party security software is compatible with your Windows version. Additionally, monitor Event Viewer regularly for early warning signs, create system restore points before major changes, and consider setting up automated maintenance tasks to clear old event logs and prevent log file corruption from accumulating over time.
Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...