Push-Button Reset is a Windows 11 feature that lets you reinstall the operating system while keeping your files or wiping everything clean. When the reset process fails partway through, you may see a generic error message like “There was a problem resetting your PC” with no details about what went wrong. Windows 11 records telemetry logs during every reset attempt, and these logs contain the exact failure point, error codes, and component status. This article shows you how to locate and read those telemetry logs so you can identify the cause of a failed reset and take corrective action.
Key Takeaways: Auditing Push-Button Reset Telemetry Logs
- Event Viewer > Applications and Services Logs > Microsoft > Windows > Setup > Remote Install > Operational: Contains detailed telemetry events for every Push-Button Reset run, including success, failure, and rollback events.
- %windir%\Panther\UnattendGC\setupact.log: A plain-text log file that records every action taken during the reset process, including file copying, driver injection, and registry changes.
- %windir%\Panther\setuperr.log: A companion log that captures only error-level entries from the reset process, making it faster to find the root cause of a failure.
How Push-Button Reset Telemetry Logs Work on Windows 11
Push-Button Reset is built on the Windows Recovery Environment and the same underlying components used by the Windows Setup program. When you initiate a reset from Settings > System > Recovery or from the Windows Recovery Environment, the system runs a series of scripts that mount the recovery image, apply the image to the system partition, inject drivers, and restore default settings. Each step generates structured telemetry data that Windows writes to the Event Viewer log channel Microsoft-Windows-Setup/Operational and to plain-text log files in the %windir%\Panther folder.
The telemetry logs record success and failure codes for each phase of the reset. Common failure points include a corrupted recovery image, insufficient disk space, a missing or damaged driver in the driver store, or a failing hard drive sector. The logs also capture rollback events that occur when an error forces the reset to undo changes and return the system to its previous state. By reading these logs, you can determine exactly which component caused the failure and whether the reset can be retried after fixing the issue.
Steps to Locate and Read Push-Button Reset Telemetry Logs
The following steps guide you through finding the Event Viewer log and the Panther log files. You need administrative privileges to access the Panther folder and to view the Event Viewer channel.
- Open Event Viewer as Administrator
Press Win + R, type eventvwr.msc, and press Enter. If prompted by User Account Control, select Yes. This opens the Event Viewer console with full access to all log channels. - Navigate to the Setup Telemetry Channel
In the left pane, expand Applications and Services Logs, then expand Microsoft, then Windows, then Setup. Under Setup, expand Remote Install and select Operational. This channel records all Push-Button Reset telemetry events. - Filter for Failed Reset Events
In the Actions pane on the right, click Filter Current Log. In the Filter tab, select Error and Warning under Event level. Click OK. Look for events with Event ID 4100 (reset started), 4101 (reset completed), 4102 (reset failed), and 4103 (reset rolled back). Double-click an event to view its Details tab, which contains the error code and phase name. - Open the Panther Log Folder
Press Win + R, type %windir%\Panther, and press Enter. This folder contains setupact.log and setuperr.log from the most recent reset attempt. If multiple reset attempts were made, look for subfolders such as UnattendGC or files with timestamps in the name, like setupact_2025-03-01.log. - Read setupact.log for Detailed Actions
Open setupact.log in Notepad. Each line starts with a timestamp and an action description. Search for the word error or fail using Ctrl+F. The log shows every file copied, every registry key set, and every command run during the reset. The failure line typically includes an HRESULT error code, such as 0x80070070 (insufficient disk space) or 0x80070490 (corrupted image). - Read setuperr.log for a Concise Error List
Open setuperr.log in Notepad. This file contains only error-level entries. If the file is empty, the reset may have succeeded or the errors were not logged to this file. Each entry includes a timestamp, the phase name, and the error code. Use this file to quickly identify the root cause without scanning the full setupact.log. - Check the Windows Recovery Environment Log
If the reset failed during the reboot phase, the log file may be located in the X:\Windows\Panther folder from within the Windows Recovery Environment. Boot into the recovery environment by holding Shift while clicking Restart in the Start menu. Open Command Prompt from Troubleshoot > Advanced Options, then type notepad X:\Windows\Panther\setupact.log to view the log.
Common Failure Patterns and Their Log Signatures
“The system cannot find the file specified” in setupact.log
This error appears when the recovery image file install.wim or install.esd is missing, corrupted, or cannot be accessed. The log shows 0x80070002 in the error code. To fix this, run sfc /scannow from an elevated Command Prompt, then use DISM /Online /Cleanup-Image /RestoreHealth to repair the image. After repair, retry the reset.
“Insufficient system resources exist to complete the API” in setuperr.log
This error corresponds to 0x8007000E and indicates low memory or low disk space during the reset. The log may also show 0x80070070 for explicit disk space failure. Free at least 10 GB on the system drive by running Disk Cleanup or moving personal files to an external drive. After freeing space, retry the reset from Settings > System > Recovery.
“The data is invalid” with Event ID 4102 in Event Viewer
This error code 0x8007000D indicates a corrupted recovery partition or a damaged boot configuration. Open an elevated Command Prompt and run bootrec /fixboot and bootrec /rebuildbcd. If the recovery partition is missing, create a USB recovery drive using the Windows Media Creation Tool and boot from it to run the reset.
| Item | Event Viewer Channel | Panther Log Files |
|---|---|---|
| Description | Structured telemetry events with IDs and error codes | Plain-text action and error logs with timestamps |
| Location | Applications and Services Logs > Microsoft > Windows > Setup > Remote Install > Operational | %windir%\Panther\setupact.log and setuperr.log |
| Best for | Identifying the failure phase and overall outcome | Finding the exact command or file that caused the failure |
| Requires admin rights | Yes | Yes |
| Readable without tools | No, requires Event Viewer | Yes, any text editor |
You can now audit Push-Button Reset telemetry logs after a failed run on Windows 11 by checking the Event Viewer channel for error codes and by reading the Panther log files for detailed action records. After identifying the root cause, repair the underlying issue and retry the reset from Settings > System > Recovery. For advanced scenarios, use the Reset this PC option with the Cloud download feature to bypass a corrupted local recovery image entirely.