Skip to contentGo to the directory tree
Windows Directory Tree
  1. C:
  2. Windows
  3. setuperr.log
LogRisk: Safe

setuperr.log C:\Windows\setuperr.log

Errors-only log of setup components, at the root of C:\Windows; counterpart of setupact.log, distinct from Panther\setuperr.log. Often empty.

Updated on By AltF4 Formation

What it’s for

C:\Windows\setuperr.log receives errors from setup components, while its counterpart setupact.log records every action. Since it keeps errors only, an empty file is normal, and a good sign.

Do not confuse it with C:\Windows\Panther\setuperr.log, which isolates the errors of the Setup program itself and is the first file to open when diagnosing an upgrade.

What it contains

  • Timestamped error lines, with the emitting component and the code.
  • Often nothing at all on a healthy machine.

Risks and best practices

  • No effect on Windows. You can delete it, but you lose a trace that may be useful.
  • An old line says nothing about the current state: check its date first, then find the context in setupact.log at the same time.
  • It can cite paths and computer names: review it before sharing.

Useful commands

Fenêtre de terminal
# Where the setup error logs are on this machine
Get-ChildItem "$env:windir", "$env:windir\Panther", 'C:\$WINDOWS.~BT\Sources\Panther' -Filter setuperr.log -ErrorAction SilentlyContinue |
    Select-Object FullName, Length, LastWriteTime


# Content (the file is usually short)
Get-Content "$env:windir\setuperr.log"

Format

Plain text: one line per error, with the date and time, the level (Error), the component and the message.

Rotation and archiving

Copy it along with setupact.log if you are documenting a deployment.

How to read it

Read each line’s date to tell whether it comes from the initial installation or a recent operation, then open setupact.log around the same time to see what Setup was doing.

Report a mistake