How to Read SetupDiag Log for a Stuck 24H2 Feature Update on Windows 11

When a Windows 11 24H2 feature update gets stuck during installation, the built-in Windows Update troubleshooter often fails to identify the exact blocking component. The update may hang at a specific percentage, roll back after a reboot, or fail with a generic error code. The root cause is almost always a driver, service, or hardware incompatibility that halts the update process silently.

SetupDiag is a Microsoft tool that analyzes Windows Setup log files to pinpoint the failure. It scans Event Log, CBS logs, and the setupact.log generated during the update attempt. This article explains how to download SetupDiag, run it against a failed 24H2 update, and interpret the output to find the blocking issue.

By the end of this guide, you will know how to extract the exact failure reason from the SetupDiag log and decide whether to remove a driver, disable a service, or uninstall conflicting software before retrying the update.

What SetupDiag Does and Why It Works for 24H2 Stuck Updates

SetupDiag is a command-line diagnostic tool provided by Microsoft for Windows 10 and Windows 11. It does not require installation. You download the executable, run it, and it parses the Windows Setup log files created during a failed feature update. The tool compares log entries against a built-in set of known failure patterns and outputs the most likely cause.

For a 24H2 feature update that is stuck, the relevant logs are located in these folders:

• C:\$Windows.~BT\Sources\Panther – Contains setupact.log and setuperr.log from the running update process.
• C:\Windows\Panther – Contains logs from completed or rolled-back update phases.
• C:\Windows\Logs\CBS – Component-Based Servicing logs that record component and driver operations.

SetupDiag scans these folders automatically when run without parameters. It identifies failures such as driver blocking, service start failures, disk space errors, or critical component corruption. The output is a single text file that names the failing rule and the offending component.

Steps to Run SetupDiag and Read the Log for a Stuck 24H2 Update

Step 1: Download SetupDiag from Microsoft

1. Open a browser and go to the Microsoft SetupDiag download page
   Navigate to learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag. Scroll to the Download SetupDiag section and click the download link. The file is named SetupDiag.exe.
2. Save SetupDiag.exe to a folder on your desktop
   Create a folder named C:\SetupDiag or use the Downloads folder. Do not run the tool from a compressed archive. Extract if needed.

Step 2: Run SetupDiag in Default Mode

1. Open Command Prompt as Administrator
   Press the Start button, type cmd, right-click Command Prompt, and select Run as administrator. Click Yes in the User Account Control prompt.
2. Change directory to the folder containing SetupDiag.exe
   Type cd C:\SetupDiag or the path where you saved the file. Press Enter.
3. Run SetupDiag with no parameters
   Type SetupDiag.exe and press Enter. The tool scans all default log locations. This process takes 30 seconds to 2 minutes depending on log size.
4. Wait for the command to finish
   When complete, the command prompt shows a line similar to: SetupDiag results written to C:\SetupDiag\SetupDiagResults.log. Do not close the window yet.

Step 3: Open and Read the SetupDiagResults.log File

1. Open the log file in Notepad
   In the same Command Prompt window, type notepad SetupDiagResults.log and press Enter. Notepad opens with the log content.
2. Locate the Failure Reason section
   Scroll down past the header lines. Look for a line starting with Failure Reason:. This line states the rule that triggered, such as ComplianceCheckFailed, DriverRejected, or ServiceFailed.
3. Find the Blocking Component
   Below the failure reason, look for Blocking Component: or Problem:. This line names the specific driver, service, or file that caused the failure. For example, Blocking Component: oem123.inf (Intel Display Driver).
4. Read the Log Snippet
   SetupDiag includes a short excerpt from the original log that shows the error. This snippet helps you confirm the context. Look for lines containing Error, Failed, or 0x800xxxxx codes.

Step 4: Run SetupDiag with a Specific Log Path If the Update Rolled Back

1. Identify the log folder from the failed update
   If the update rolled back and you rebooted, the default scan may not find the correct logs. Navigate to C:\$Windows.~BT\Sources\Panther and check the date of setupact.log. This is the folder from the last update attempt.
2. Run SetupDiag with the /LogsPath parameter
   In Command Prompt, type SetupDiag.exe /Scenario:FeatureUpdate /LogsPath:C:\$Windows.~BT\Sources\Panther. Press Enter. This forces SetupDiag to analyze only that folder.
3. Open the new log file
   Type notepad SetupDiagResults.log again. The output now reflects only the logs from the specified path.

Common Failures Found in SetupDiag Logs for 24H2 Updates

DriverRejected: Display or Network Driver Blocking the Update

SetupDiag shows Failure Reason: DriverRejected with a line like Blocking Driver: oem123.inf. This indicates the 24H2 update detected an incompatible driver. The fix is to uninstall the driver from Device Manager, then download the latest version from the hardware vendor. After updating the driver, run Windows Update again.

ServiceFailed: Third-Party Service Preventing Setup

The log may contain Failure Reason: ServiceFailed with a service name such as Veeam Backup Service or McAfee Endpoint Security. These services lock system files during the update. Temporarily disable the service from Services.msc, retry the update, and re-enable the service after the update completes.

ComplianceCheckFailed: Antivirus or Security Software Conflict

SetupDiag reports Failure Reason: ComplianceCheckFailed without a specific component name. This often points to antivirus software that blocks the update. Temporarily disable real-time protection or uninstall the third-party antivirus. Use Microsoft Defender during the update process.

DiskSpace: Insufficient Free Space on the System Drive

The log shows Failure Reason: DiskSpace with the required and available space. The 24H2 update requires at least 20 GB of free space on the system drive. Run Disk Cleanup to remove temporary files, or move large files to an external drive. After freeing space, retry the update.

SetupDiag Default Scan vs Manual Log Path Scan

Item	Default Scan	Manual Log Path Scan
Command	SetupDiag.exe	SetupDiag.exe /Scenario:FeatureUpdate /LogsPath:path
Log sources scanned	$Windows.~BT, Panther, CBS, SetupAPI	Only the folder specified in /LogsPath
Best use case	Update failed and system has not rebooted	Update rolled back and system rebooted
Output file location	Same folder as SetupDiag.exe	Same folder as SetupDiag.exe

SetupDiag is a precise diagnostic tool that eliminates guesswork when a 24H2 feature update gets stuck. After reading the log, you will know exactly which driver, service, or condition caused the failure. Remove the blocking component, free disk space, or disable the conflicting service. Run Windows Update again and the 24H2 update should proceed. For advanced troubleshooting, use the SetupDiag /Verbose parameter to generate a more detailed log that includes every rule check performed.