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.

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.
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
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
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
Solutions
Restart Windows Event Log Service
The Event Log service may have stopped or become unresponsive. Restarting it often resolves temporary issues.
- Press Windows + R, type
services.mscand press Enter - Scroll down and locate Windows Event Log
- Right-click on the service and select Properties
- Note the current status. If stopped, click Start
- If running, click Stop, wait 10 seconds, then click Start
- Set Startup type to Automatic
- Click Apply and OK
Alternative command line method:
net stop eventlog
net start eventlogVerification: Open Event Viewer by pressing Windows + X and selecting Event Viewer. Navigate to Windows Logs → System and verify recent entries are visible.
Run System File Checker and DISM
Corrupted system files often cause Event Log service failures. SFC and DISM can repair these files.
- Press Windows + X and select Windows Terminal (Admin)
- Run the DISM command first to prepare the system:
DISM /Online /Cleanup-Image /RestoreHealth- Wait for completion (may take 15-30 minutes)
- Run System File Checker:
sfc /scannow- Restart your computer after both commands complete
- Check the SFC log for details:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.logsfc /scannow again after DISM completes.Verification: After restart, open Event Viewer and check if new system events are being logged properly.
Reset Event Log File Permissions
Incorrect permissions on Event Log directories can prevent the service from functioning. This method resets permissions to default values.
- Open Windows Terminal (Admin)
- Navigate to the Event Log directory:
cd /d %SystemRoot%\System32\winevt\Logs- Take ownership of the Logs folder:
takeown /f . /r /d y- Reset permissions using icacls:
icacls . /reset /t /c /l- Grant specific permissions to Event Log service:
icacls . /grant "NT SERVICE\EventLog":F /t
icacls . /grant "SYSTEM":F /t
icacls . /grant "Administrators":F /t- Restart the Event Log service:
net stop eventlog && net start eventlogVerification: Run icacls %SystemRoot%\System32\winevt\Logs to confirm permissions are correctly set.
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.
- Stop the Event Log service:
net stop eventlog- Navigate to the Event Log directory:
cd /d %SystemRoot%\System32\winevt\Logs- Create a backup folder and move existing logs:
mkdir C:\EventLogBackup
move *.evtx C:\EventLogBackup\- Clear the Event Log registry cache:
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\EventLog" /v "File" /f- Restart the Event Log service:
net start eventlog- 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.
Registry Repair and Service Reconfiguration
Deep registry corruption may require manual repair of Event Log service configuration.
- Create a registry backup:
reg export HKLM\SYSTEM\CurrentControlSet\Services\EventLog C:\EventLog_Registry_Backup.reg- Open Registry Editor as Administrator:
regedit- Navigate to:
HKLM\SYSTEM\CurrentControlSet\Services\EventLog - Verify the following values exist and are correct:
- DisplayName (REG_SZ):
Windows Event Log - ImagePath (REG_EXPAND_SZ):
%SystemRoot%\System32\svchost.exe -k LocalServiceNetworkRestricted -p - Start (REG_DWORD):
2(Automatic) - Type (REG_DWORD):
32 - If any values are missing or incorrect, right-click in the right pane, select New, and create the appropriate value type
- Navigate to:
HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Parameters - Ensure ServiceDll (REG_EXPAND_SZ) is set to:
%SystemRoot%\System32\wevtsvc.dll - 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.
Verification
To confirm the Event Log service is working correctly:
- Open Event Viewer by pressing Windows + X and selecting Event Viewer
- Navigate to Windows Logs → System
- Verify recent events are visible with current timestamps
- Check service status:
sc query eventlog - Test event creation:
eventcreate /T INFORMATION /ID 1000 /L SYSTEM /SO TestApp /D "Event Log test message" - Refresh Event Viewer and confirm the test event appears
- Verify application logs are also functioning by checking Windows Logs → Application
Advanced Troubleshooting
If the above methods didn't resolve error 36887:
- Check disk space: Ensure at least 1GB free space on the system drive. Event logs require adequate space to function.
- Scan for malware: Run Windows Defender full scan or use Microsoft Safety Scanner to check for malware targeting system services.
- Disable third-party security software temporarily: Some antivirus programs interfere with Event Log service. Temporarily disable and test.
- Check Windows Update: Install pending updates as Microsoft regularly releases fixes for Event Log issues.
- Run Windows Memory Diagnostic: Press Windows + R, type
mdsched, and restart to check for memory issues. - Perform System Restore: If the error started recently, restore to a point before the issue began.
- Reset Windows (keep files): As a last resort, use Settings → Update & Security → Recovery → Reset this PC with the "Keep my files" option.
Frequently Asked Questions
What does Windows Event Log error 36887 specifically indicate?+
Can error 36887 cause other Windows services to fail?+
Is it safe to delete event log files to fix error 36887?+
Why does error 36887 occur more frequently after Windows updates?+
How can I prevent error 36887 from recurring after fixing it?+
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.
Further Intelligence
Deepen your knowledge with related resources
Discussion
Share your thoughts and insights
You must be logged in to comment.


