Microsoft-Windows-CorruptedFileRecovery-Server

17 events across 2 channels

Event IDTitleChannel
1The file FileName may be corrupted, which may have caused the application …Operational
2The system file FileName is corrupted, which may have caused the application …Operational
3The system file FileName may be corrupted, which may have caused the application …Operational
4The system file FileName is corrupted, which may have caused the application …Operational
5The system file FileName was reported as being corrupted but Windows determined …Operational
6The system file FileName was corrupted, which may have caused the application …System
7The system file FileName was corrupted, which may have caused the application …Operational
8The system file FileName was corrupted, which may have caused the application …System
9The system file FileName may be corrupted, which may have caused the application …Operational
10The system file FileName may be corrupted, but Windows could not determine if …System
11The system file FileName is corrupted, which may have caused the application …System
12Windows detected that program file FilePath is corrupted, causing application …System
13The program file FileName was reported as being possibly corrupted, causing …Operational
14The file FileName may be corrupted, which may have caused the application …System
15Windows detected that program file FilePath is corrupted, causing application …Operational
16Windows detected that program file FilePath is corrupted, causing application …Operational
17The program file FileName was reported as being possibly corrupted, causing …Operational

Event ID 1 — The file FileName may be corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Description

The file FileName may be corrupted, which may have caused the application AppName to stop working. Windows did not attempt to repair FileName because it is not a protected system file.

Message #

The file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair %1 because it is not a protected system file.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 2 — The system file FileName is corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Message #

The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows will not attempt to repair %1 because too many corrupted files have been detected recently.  Frequent corruptions may indicate a problem with the disk on this computer.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 3 — The system file FileName may be corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Message #

The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair this file because the same file has been repaired too many times over a recent period of time.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 4 — The system file FileName is corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Description

The system file FileName is corrupted, which may have caused the application AppName to stop working. Windows did not attempt to repair this file because a repair attempt is already underway for the same file.

Message #

The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair this file because a repair attempt is already underway for the same file.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 5 — The system file FileName was reported as being corrupted but Windows determined that the file is not actually damaged.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Description

The system file FileName was reported as being corrupted but Windows determined that the file is not actually damaged. It may have been repaired already.

Message #

The system file %1 was reported as being corrupted but Windows determined that the file is not actually damaged. It may have been repaired already.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 6 — The system file FileName was corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

Message #

The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows was unable to repair this file (error code %3).  Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString
ErrorCode UInt32

Event ID 7 — The system file FileName was corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Description

The system file FileName was corrupted, which may have caused the application AppName to stop working. Windows successfully repaired the damaged file.

Message #

The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows successfully repaired the damaged file.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 8 — The system file FileName was corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

Description

The system file FileName was corrupted, which may have caused the application AppName to stop working. Windows attempted to repair the file. A reboot is required to finish this repair.

Message #

The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file. A reboot is required to finish this repair.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 9 — The system file FileName may be corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Message #

The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file, but the operation was cancelled before it could be completed.  Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 10 — The system file FileName may be corrupted, but Windows could not determine if the file was actually damaged (error code ErrorCode).

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

Message #

The system file %1 may be corrupted, but Windows could not determine if the file was actually damaged (error code %3). No repair action was taken. Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString
ErrorCode UInt32

Event ID 11 — The system file FileName is corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

Message #

The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows could not attempt to repair %1 because a previous repair operation was pended.  Reboot the computer and run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 12 — Windows detected that program file FilePath is corrupted, causing application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

Description

Windows detected that program file FilePath is corrupted, causing application AppName to stop working. To restore the file, reinstall ProductName version ProductVersion.

Message #

Windows detected that program file %1 is corrupted, causing application %2 to stop working. To restore the file, reinstall %3 version %4.

Fields #

NameDescription
FilePath UnicodeString
AppName UnicodeString
ProductName UnicodeString
ProductVersion UnicodeString

Event ID 13 — The program file FileName was reported as being possibly corrupted, causing application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Description

The program file FileName was reported as being possibly corrupted, causing application AppName to stop working. Windows performed additional diagnostics and determined that the file is not actually damaged.

Message #

The program file %1 was reported as being possibly corrupted, causing application %2 to stop working. Windows performed additional diagnostics and determined that the file is not actually damaged.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 14 — The file FileName may be corrupted, which may have caused the application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

Description

The file FileName may be corrupted, which may have caused the application AppName to stop working. Windows did not attempt to repair FileName because it could not find its corresponding installer package.

Message #

The file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair %1 because it could not find its corresponding installer package.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString

Event ID 15 — Windows detected that program file FilePath is corrupted, causing application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Message #

Windows detected that program file %1 is corrupted, causing application %2 to stop working. Reinstalling %3 version %4 may repair the file. However, Windows is not launching a %3 reinstallation because too many product reinstalls have run recently.

Fields #

NameDescription
FilePath UnicodeString
AppName UnicodeString
ProductName UnicodeString
ProductVersion UnicodeString

Event ID 16 — Windows detected that program file FilePath is corrupted, causing application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Message #

Windows detected that program file %1 is corrupted, causing application %2 to stop working. Reinstalling %3 version %4 may repair the file. However, Windows is not launching a %3 reinstallation because that product has already been reinstalled too many times recently.

Fields #

NameDescription
FilePath UnicodeString
AppName UnicodeString
ProductName UnicodeString
ProductVersion UnicodeString

Event ID 17 — The program file FileName was reported as being possibly corrupted, causing application AppName to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

Message #

The program file %1 was reported as being possibly corrupted, causing application %2 to stop working. Windows performed additional diagnostics and determined that the file is not an executable image. To avoid potential user data loss, Windows will not attempt to repair the file.

Fields #

NameDescription
FileName UnicodeString
AppName UnicodeString