| Event Id | 25 |
| Source | Microsoft-Windows-Eventlog |
| Description | The event logging service encountered a corrupt log file for channel %1. The log was renamed with a .corrupt extension |
| Event Information | According to Microsoft : Cause : This event is logged when the event logging service encountered a corrupt log file for channel. Resolution : Shutdown the computer properly or repair the hard disk The most likely reason for a corrupt event log is that the computer was incorrectly shut down. The remedy for this is to always shut down the system correctly and to have backup power to avoid having the power shut off from the computer while the computer is turned on. Another cause for a corrupt event log file is when a problem occurs with the hard disk drive that contains the event log. To resolve this problem, repair or replace the hard disk drive if required. Verify : Use the Event Viewer to read the affected log on the local computer after the computer has been restarted, and verify that events 20, 23, 25, 26, or 40 did not appear in the event log after the system was restarted. |
| Reference Links | Event ID 25 from Microsoft-Windows-Eventlog |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.