Skip to contentGo to the directory tree
Windows Directory Tree
  1. C:
  2. Windows
  3. INF
  4. setupapi.setup.log
LogRisk: Caution

setupapi.setup.log C:\Windows\INF\setupapi.setup.log

SetupAPI text log for operating system installation and upgrade; traces driver configuration during Setup.

Updated on By AltF4 Formation

What it’s for

setupapi.setup.log is the SetupAPI log for the installation or upgrade of Windows itself. Its two neighbors cover other cases: setupapi.dev.log tracks device installation and setupapi.app.log tracks application installation. It is mostly an archaeology log, handy for understanding what happened during deployment.

What it contains

  • The SetupAPI sections written during Windows installation: processing of INF files and of the drivers in the configuration phase.
  • On a machine installed long ago, content that has been frozen since Setup finished.

Risks and best practices

  • The file is historical, so deleting it changes nothing about how Windows runs.
  • For a current driver problem, open setupapi.dev.log, which is written at every device installation.
  • It names drivers and hardware, so review it before sharing.

Useful commands

Fenêtre de terminal
# Sections that ended in failure
Select-String -Path "$env:windir\INF\setupapi.setup.log" -Pattern 'Exit status: FAILURE' -Context 8,0 | Select-Object -Last 5


# Last lines
Get-Content "$env:windir\INF\setupapi.setup.log" -Tail 60 -ErrorAction SilentlyContinue

Format

Same format as the other SetupAPI logs: a text file organized in sections, each opened by a timestamped >>> line and closed by <<< with the exit status.

Rotation and archiving

The file is written during installation and then kept as it is.

How to read it

Look for Exit status and for lines containing error or fail, then read the surrounding section to find the INF or driver involved. Cross-check with Panther\setupact.log.

Report a mistake