-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
Create an account on the HP Community to personalize your profile and ask a question
Your account also allows you to connect with HP support faster, access a personal dashboard to manage all of your devices in one place, view warranty information, case status and more.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended
SetupDiag will only generate output if it finds relevant upgrade log files from a failed Feature Update (e.g., 23H2 ➜ 24H2). If it doesn't find relevant logs, it won’t generate an output file. That’s why nothing was created.
Please check if the following folder exists:
C:\$WINDOWS.~BT\Sources\Panther\
and contains files like setupact.log or setuperr.log.
If not, then SetupDiag.exe has no data to analyze, and it will not create a results file.
If the folder does exist and contains logs, try this:
mkdir C:\SetupDiag C:\SetupDiag.exe /Output:C:\SetupDiag\Results.xml /Format:xml
Let me know what you find!
Kind Regards,
NonSequitur777
9
2
0
HP Recommended
I found the files in the folder you directed me to look for. Sorry it's a elongated photo, but there was a lot of files above it in the same directory.
Before I attempt anything further, there are text in both logs, setuperr,log is the smallest, setupact.log is bigger, you see the file sizes in my photo, so as far as you looking at either log, what is the best log to share and if it's setupact.log how do I share that here? It has a lot text in it and both logs refer to June 21. I believe that is the day 24H2 tried to update,
HP Recommended
You're exactly right -June 21 matches the day Windows 24H2 tried to install, so we’ll want to review the logs from that attempt -I'll do my best!
The setupact.log file is typically the most useful for detailed diagnostics, as it records the step-by-step process of the upgrade and any specific failure points. The setuperr.log is helpful too, but usually much shorter and just summarizes critical errors.
How to Share the setupact.log:
Since this file can be large, please follow one of these options:
Option 1: Upload to a file sharing site:
Copy the setupact.log to your Desktop for easy access.
Go to a trusted file sharing site like WeTransfer, Google Drive, or OneDrive.
Upload the file and generate a shareable link.
Post the link here so I can take a look.
Option 2: Copy/Paste Key Sections:
If you're not comfortable uploading:
Open setupact.log in Notepad.
Scroll to the bottom of the file, and copy the last 100–200 lines, where the failure is usually logged.
Paste that portion directly into your reply here.
Either way is fine -whatever you're most comfortable with!
Kind Regards,
NonSequitur777
9
2
0
HP Recommended
HP Recommended
The system made it all the way through the "Apply New OS" phase:
We can confirm:
SafeOS setup completed
New OS WIM image was applied
Drivers were applied
Recovery image was prepared
Boot sector and entries were updated
Even BitLocker was suspended (if it was active)
So technically, all setup operations were completed successfully.
But the log then jumps into registering rollback operations:
This suggests the failure happened after rebooting into the new OS for the first time, during what’s called the "First Boot" phase or "OOBE/SetupComplete phase."
However, there are no errors, just successful steps. That's typical in cases where:
A driver fails during the boot process into the new OS (especially graphics or storage drivers)
There’s a device/driver conflict, such as legacy USB filters (you have ScpToolkit and PxHlpa64, both common culprits)
Or, SafeOS fails to hand off control properly
Leading Suspicion from This Setup:
One notable line:
2025-06-21 10:25:57, Info SP Filter entry PxHlpa64 should be migrated
PxHlpa64.sys is a Sonic/Roxio CD/DVD Class Filter Driver — very outdated and known to cause Windows Setup rollbacks, especially during in-place upgrades to new builds.
Also present:
2025-06-21 10:25:57, Info SP Binary path: C:\Program Files\Nefarius Software Solutions\ScpToolkit\ScpUpdater.exe
ScpToolkit — a popular but abandoned PS3 controller driver — installs low-level USB filters that can crash SafeOS or the first boot into the new OS.
Recommended Fix Before Retry:
Please do the following before retrying the 24H2 upgrade:
Step 1: Uninstall Known Culprits:
Open Device Manager and:
Enable “View > Show hidden devices”
Look under DVD/CD-ROM drives and Universal Serial Bus controllers
Look for any leftover drivers from:
ScpToolkit (e.g., Bus Driver, Virtual Bus, etc.)
Roxio/Sonic (e.g., PxHlpa64, UpperFilters, LowerFilters)
Use Programs and Features or a tool like Revo Uninstaller to fully remove:
ScpToolkit
Any Roxio/Sonic software
Old Visual Studio components if unused
Step 2: Clean Upper/LowerFilters from Registry:
Run regedit.exe
Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ {4D36E965-E325-11CE-BFC1-08002BE10318}
In the right pane:
If you see UpperFilters or LowerFilters, export the key first (backup), then delete them.
Step 3: Disconnect Unneeded Peripherals:
Unplug any:
Controllers
USB drives
Audio interfaces
Old printers/scanners
Then retry the update.
Summary:
Your diagnostic work shows the upgrade passed through SafeOS and NewOS apply, then rolled back without an error code in setupact.log. That **strongly points to a bad filter driver or kernel.
High-Probability Causes:
1. Legacy or problematic filter drivers:
Already flagged earlier: PxHlpa64.sys and ScpToolkit inject USB/optical filter drivers. These are prime suspects in boot-time crashes during upgrade.
2. Graphics or USB driver crash at first boot:
Since it passes all image and driver apply phases, but fails after reboot, a kernel-mode driver (likely graphics, USB, audio, or storage) is crashing silently. This could cause SafeOS to trigger a rollback.
3. Leftover pending services or startup commands:
Occasionally, older Visual Studio components or custom services (VSInstallerElevationService, VSStandardCollectorService150) interfere with boot transitions.
Summary: Phase Completion – Post-SysPrep Success:
The final log entries show that everything up through the "Post SysPrep" phase completed successfully, including:
WIM image extraction and file relocation
Registry and driver provisioning
Optional components, features-on-demand, and language packs added
Recovery partition backed up and reconfigured
Telemetry, product activation keys, and diagnostics written
Boot configuration entries for rollback and SafeOS set
Boot switch to the new OS environment prepared (likely triggering reboot)
Where it Ends: Ready to Reboot into WinPE / SafeOS:
The process serialized operations for:
Boot WinPE
Set safe OS boot command
Orchestrate OS switch for NewOS with SafeOS and rollback OS
And it logs a clean exit:
2025-06-21 10:25:58, Info SP Execution phase [Post SysPrep] exiting with HRESULT [0x00000000]
This shows the upgrade process successfully reached the transition point — right before the system was supposed to reboot into WinPE/SafeOS to continue with OOBE (Out-of-Box Experience) setup.
Yet... This Was Followed by Rollback?
If you're telling me this system later rolled back to the previous Windows version, then the problem must have occurred after this point, likely:
During the first boot into the new OS
During OOBE setup (user account, privacy, network, etc.)
Possibly a driver failure or service crash that triggered rollback
Suggestions for Next Diagnostic Step:
To get insight into why the rollback happened, you need to check logs from the rollback or rollback trigger phase, particularly in:
C:\$WINDOWS.~BT\Sources\Panther\setupact.log (you've already looked here)
setuperr.log in same Panther directory — if present
Or potentially in:
C:\Windows\Panther\UnattendGC\setupact.log
C:\Windows\Panther\setupact.log (this one logs final first-boot issues)
What Might Be Causing the Rollback?
Based on many 24H2 upgrade issues logged this year, the rollback might be triggered by:
Unsupported or incompatible drivers, especially GPU, audio, or storage
Failed migration of a 3rd-party antivirus, security software, or disk encryption tool
BitLocker/TPM issues if enabled (you mentioned TPM 2.0 issues earlier)
Unexpected failure in the OOBE phase, sometimes triggered by OEM pre-installs or bloatware
Next Step for You?
Let me know if you'd like me to:
Review any setuperr.log you might find
Help create a SetupDiagResults.log file using the SetupDiag tool offline
Suggest upgrade mitigation steps (e.g. clean boot + staged upgrade + SafeOS workaround)
Parse any recent BlueBox.log (if rollback triggered by compat fail)
Kind Regards,
NonSequitur777
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
Didn't find what you were looking for?
Ask the community