Microsoft-Windows-CorruptedFileRecovery-Server

17 events across 2 channels

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

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

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

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
AppName

Event ID 2 — The system file %1 is corrupted, which may have caused the application %2 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
AppName

Event ID 3 — The system file %1 may be corrupted, which may have caused the application %2 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
AppName

Event ID 4 — The system file %1 is corrupted, which may have caused the application %2 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 did not attempt to repair this file because a repair attempt is already underway for the same file.

Fields

NameDescription
FileName
AppName

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

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

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
AppName

Event ID 6 — The system file %1 was corrupted, which may have caused the application %2 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
AppName
ErrorCode

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

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
Operational

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
AppName

Event ID 8 — The system file %1 was corrupted, which may have caused the application %2 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 attempted to repair the file. A reboot is required to finish this repair.

Fields

NameDescription
FileName
AppName

Event ID 9 — The system file %1 may be corrupted, which may have caused the application %2 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
AppName

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

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
AppName
ErrorCode

Event ID 11 — The system file %1 is corrupted, which may have caused the application %2 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
AppName

Event ID 12 — Windows detected that program file %1 is corrupted, causing application %2 to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

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
AppName
ProductName
ProductVersion

Event ID 13 — The program file %1 was reported as being possibly corrupted, causing application %2 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 actually damaged.

Fields

NameDescription
FileName
AppName

Event ID 14 — The file %1 may be corrupted, which may have caused the application %2 to stop working.

Provider
Microsoft-Windows-CorruptedFileRecovery-Server
Channel
System

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
AppName

Event ID 15 — Windows detected that program file %1 is corrupted, causing application %2 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
AppName
ProductName
ProductVersion

Event ID 16 — Windows detected that program file %1 is corrupted, causing application %2 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
AppName
ProductName
ProductVersion

Event ID 17 — The program file %1 was reported as being possibly corrupted, causing application %2 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
AppName