• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended
HP ENVY Desktop PC TE01-4000i (6V9A5AV)
Microsoft Windows 11

Problem:

I have the HP Envy TE01-4254 model Desktop computer.

I have been getting the 24H2 Windows update via Windows update since November 2024.

Every month around the 11th or so, it downloads and attempts to install 24H2, then asking for a reboot.

7 attempts have been made over the last seven months through Windows update. 4 attempts were made manually by downloading the update from Microsoft and manually installing it that way.

All 11 attempts failed with my HP Envy TE01-4000i getting to 63% then several reboots and then finally, a notice with the HP logo stating that "changes to my system are being undone" that white spinning circle stays on screen until my system reboots back into Windows 11 23H2.

I have looked through Windows update logs and Event Viewer logs extensively. What I see in the Event Viewer is

Event 20 WindowsUpdateClient

Installation Failure: Windows failed to install the following update with error 0xC1900101: Windows 11, version 24H2

 

I have disconnected all external hardware right down to just mouse and the keyboard, no go, Windows update 24H2 isn't completing.

Now, I happen to own 3 HP desktop computers, each with a different model number, a TE01-0034 and a M01-F1014 both with Windows 11 Home Edition. Both of those systems updated to 24H2 with no issues. Only the HP Envy TE01-4254 (TE01-4000i) desktop computer refuses to install 24H2 and fails at 63% each time..

All of my HP drivers are up-to-date and my Nvidia RTX-3050 drivers are up-to-date.

I have made sure no virus software is running during the update, it appears this failure takes place when the OS is in an out of the OS state, Only the HP boot logo with a spinning white circle is on the screen. I briefly noticed a command prompt window flash on screen at about 63% complete into the update, that is where the issue starts to begin and that notice of we are undoing changes to your computer system begins.

 

Upon completion, my system is back to 23H2 again.

Anyone have a clue what is going on here? My three separate HP computer systems are not set up differently from one another.

 

OS: Windows Home Edition 64bit Operating System

 

Bruce.

1 ACCEPTED SOLUTION

Accepted Solutions
HP Recommended

@MrBruce1959,

 

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:

 

  1. Run regedit.exe

  2. Navigate to:

 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ {4D36E965-E325-11CE-BFC1-08002BE10318}
  1. 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:

 

  1. Review any setuperr.log you might find

  2. Help create a SetupDiagResults.log file using the SetupDiag tool offline

  3. Suggest upgrade mitigation steps (e.g. clean boot + staged upgrade + SafeOS workaround)

  4. Parse any recent BlueBox.log (if rollback triggered by compat fail)

 

Kind Regards,

 

NonSequitur777


View solution in original post

17 REPLIES 17
HP Recommended

@MrBruce1959,

 

Welcome to our HP Community forum!

 

Thank you for the detailed explanation and for being a multi-HP system owner -your troubleshooting so far has been thorough, methodical and very helpful for understanding the situation.

 

Based on the behavior you've described, especially the consistent rollback at 63% during the 24H2 install, and the error code 0xC1900101, the problem is likely related to a driver conflict or low-level hardware/BIOS compatibility issue, often triggered during the “out-of-OS” (pre-boot) phase of the update.

 

Here are a few steps you can try:


Recommended Troubleshooting Steps:

 

  1. Check for Updated BIOS & Drivers:

  2. Disable/uninstall Security Software Completely (temporarily):

    • You've already tried disabling them -next, try fully uninstalling or disabling any third-party antivirus, including trial versions (e.g., McAfee, Norton), as they can interfere during pre-boot update stages.

  3. Clean Boot + Windows Update Install:

    • Boot into a clean Windows environment (type msconfig, go to Services > Hide all Microsoft services > Disable all).

    • Reboot, then retry the update from Windows Update or use the standalone ISO method.

  4. Try the 24H2 ISO Instead of Windows Update:

  5. Run SetupDiag:

    • Download Microsoft’s SetupDiag tool and run it after a failed upgrade. It creates a detailed log that can pinpoint the exact blocking driver or component.

  6. Disconnect Additional Internal Drives (If Any):

    • If you have multiple internal drives (e.g., an HDD in addition to an SSD), disconnect all but the system drive during the upgrade process.


Additional Notes:

 

  • Error 0xC1900101 is broadly a driver-related issue -typically storage, graphics, or network.

  • The command prompt window flashing at 63% is a sign that a driver install script or upgrade task is failing silently.


If All Else Fails:

 

If all else fails, you may want to consider performing a clean install of Windows 11 version 24H2, since it's now officially available. Be sure to back up your data, then download the 24H2 ISO or use the Media Creation Tool to create a USB installer.


Let me know how it goes -or if you can share error logs from SetupDiag, I’d be happy to take a closer look!

 

Kind Regards,

 

NonSequitur777


HP Recommended

Hello, thanks for replying to my thread.

I do have HP support assistant installed and operational, it has been for quite some time now.

It often responds with You're up to date with software & drivers.

My system recently performed a BIOS firmware update, and while I cannot give an exact date on when that was performed, it obviously did not help as it has been an issue with Windows Update 24H2 since November of 2024.

My last attempt was on Wednesday May 21, when Windows Update asked for a reboot to install updates. I allowed my computer to reboot, thinking it was just a security update. It was instead another attempt to update to 24H2.

 

I realized this when I had seen that famous message on my screen, stating that my system was undoing changes made to my computer. When my system booted back into 23H2, I did a system restore back up, I then looked at my Windows Update area and seen that notice that Update 24H2 failed to install.

I shut my system down, unplugged any external devices, leaving only my mouse and keyboard plugged in. Upon bootup, I only have Windows Security as my main virus scanner, but I do have MalwareBytes as a backup for on-demand scanning only. I disabled the start with Windows option and exited the program completely.

 

Then I went back into Windows Update and choose: RETRY.

This caused my system to reboot and back to the beginning of another 24H2 update.

I was hoping it would succeed, with the elimination of other external hardware, but once again, at 63% and a command window flash on screen, my system rolled back to 23H2. Then I decided to publish this thread.

 

Last month, during last month's attempt to install Update 24H2 I almost thought I lost my operating system, because, my computer screen went dark for a very, very long period of time, so I rebooted my system, recovery stated it needed to do a repair, then repair stated it could not repair my system, I booted to a Windows 11 ISO on a flash drive setup as an installation media. The same option you suggested above from making a media installation disk from Microsoft. I tried the option to install Windows 11 and keep my programs and files. That failed to work.

 

At some point it stated there was no operating system on the SSD. I used an old Windows DOS trick under the command prompt option within the recovery area. I did a directory of drive C: and it showed all the files that are on Drive C: including the Windows folder which was still there, so the disk, or OS was not wiped, everything was still there.

 

The final outcome was on one of the bootup attempts, and the HP logo screen, my system finally booted back into Windows with everything still there, nothing was deleted., So I got very lucky on that one. But this update sneaks up on me, When I get a Windows update notice that needs a reboot, I do not realize 24H2 is what the update is.

 

Like I said, I tried many options I read online related to this update, including trying to stop it from being offered until something is worked out, but that failed because it was offered to me again yesterday.

In conclusion, I have used HP assistant to update and troubleshoot my system.

I have used the HP website for drivers and software and allowed it to detect my computer system and a list of drivers are then listed for download. But, there are many options offered for the same hardware so, download all of it to have it state this software is not valid for your system, gets to be annoying after trying several of the files I have downloaded, trying to install the right ones the first time.

 

As far as I know I have the latest BIOS firmware installed, I would have to boot into the recovery option to enter my BIOS to see which version it has installed.

Edit: I just checked my UEFI BIOS version is 8B3B F.33 dated 09-23-2024

Hope all of this information is helpful to further diagnose the issue, I would hate to have to format my SSD drive and start with a fresh install of Windows, some programs are a pain to reinstall with software anti-piracy protocols in place in today's software.

 

Bruce

HP Recommended

@MrBruce1959,

 

Yea, this is a tough one, all right.

 

Have you tried running as administrator in CMD:

 

sfc /scannow

 

and:

 

DISM /Online /Cleanup-Image /RestoreHealth

 

And you are sure your PC isn't connected to any peripheral devices whilst the installation is ongoing?


It has been recommended to have at least 64 GB of free space available on your primary (boot) drive for this update without any restrictions.


Please try the following steps and see if that helps:

 

Press Windows key + X key together, then choose Command Prompt (Admin).

 

In the Command prompt window, copy/paste each of the following commands and press Enter after each command. Wait for each process to finish before continuing to the next one.

 

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

 

Once you've finished entering all the commands, close the Command Prompt window and restart your computer.

 

Try this registry (REGEDIT) change. Worked to change Windows 11 Pro release to user version.

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windowsupdate


"TargetReleaseVersion"=dword:00000001
"ProductVersion"="Windows 11"
"TargetReleaseVersionInfo"="24H2"

 

Kind Regards,

 

NonSequitur777


HP Recommended

Okay, I have not left you hanging on this one.

Although Windows 11 likes to use Terminal (Admin), I executed cmd.exe from the system 32 folder of Windows as an administrator and ran sfc\Scannow, I am familiar with that commend. It did find some issues and it repaired them. So far so good.

I am currently looking over the CBS.log at this moment and time looking for clues.

I will reply back once I have finished that process and then I will work through the other suggestions that you have made.

I want to take this one step at a time so as not to make a mess of things executing too many actions at once.

 

Edit: I edited this to add this information in the CBS.log after running the SFC\Scannow command.

2025-05-23 09:10:07, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\BthA2dp.sys
2025-05-23 09:10:07, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthA2dp.sys
2025-05-23 09:10:07, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\BthHfEnum.sys
2025-05-23 09:10:07, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthHfEnum.sys

Stay tuned!

Bruce

HP Recommended

@MrBruce1959,

 

Well, let's hope for the best!

 

If nothing works, save your data, reformat your drive and reinstall Windows.

 

Incidentally, I had to do that last night when the gaming PC from one of my sons developed Windows-related cascading "fatal exceptions" issues, and no matter what I tried to "repair" the issue, it just wouldn't let me -it was fighting me all the way, so to speak.

 

Anyway, I digress.

 

Kind Regards,

 

NonSequitur777


HP Recommended

Sorry to hear you had to go through that. I use this computer to play FFXIV Online.

I ran Dism.exe /OnLine /CleanUp-Image /ReStoreHealth

I am going through the DISM.log right now. Lots of scrolling and reading within these logs, but they are created when Windows does certain executions, such as Windows Update.

If I find any key issues, I'll let you know.

Perhaps sfc\scannow fixed whatever issues I was dealing with.

I know HP assistant kept offering me the same  Realtek BlueTooth  driver even after it said it installed it successfully, it offered it again on a rescan.

 

Bruce.

HP Recommended

Just updating this thread.

As of June 21 2025, which is another date Windows Update 24H2 tried to install, it once again failed to update rolling back at 75% complete with we're undoing changes made to your computer.

 

I cannot seem to keep windows at a minimal boot up, it keeps reverting back to full bootup loading drivers. I do not want to just format my hard drive and boot up off of a Windows installation USB drive and install a fresh operating system.

 

As I mentioned earlier, I have two older HP desktop computers that originally had 23H2 that updated to 24H2 as that is what is showing for the system information, 24H2, this one just won't get past 75%!

 

I have worn myself out reading logs, which get extensively long even before I get the stupid UPDATE 100% downloaded and the reboot prompt comes up, so I cannot effectively troubleshoot the logs because of this. This is even the case if I delete all the older logs leaving only the new one.

 

The logs just DO NOT mention anything regarding that a roll-back is taking place. If it even did that, I could pinpoint at which point the process fails.

 

I did the DSIM cleanup restore health command, I did SFC /scannow and SFC found no issues. If it is a driver, I have no idea which one is the issue. My BIOS is updated to the latest version, my video drivers are up-to-date and newly updated. All HP computer drivers are up-to-date per HP support assistant.

 

I ran a program called WhyNotWin11, it gave my system all green results which a pass for windows 11.

 

Without a doubt, Windows 11 24H2 is the latest update for Windows 11 and it was first offered to my system back in November of 2024 and it still refuses to update and install regardless of what I do.

 

So, obviously, I am at wits end here with this here nightmare.

HP Recommended

@MrBruce1959,

 

Windows 11 24H2 has been problematic for a number of users with OEM systems. Since you've already done SFC, DISM, BIOS and driver updates, and the failure is consistently at 75%, the next best steps in my opinion are:

 

  1. Run SetupDiag to pinpoint the failure. 

     

    Steps:

    • Download and run SetupDiag.exe

    • It will generate a report (SetupDiagResults.log)

    • Look for clues such as MOUPG, rollback, or exit code 0xC1900101 (a driver issue)

       

      If the tool shows something like:

       

       
      Error MOUPG UpgradeRollback Failure Error: 0xC1900101 - 0x30018

       

      That almost always means a driver failed during the SYSPREP stage.

     

  2. Temporarily remove any antivirus/security software.

  3. Try a clean boot using msconfig.

  4. Disconnect all USB peripherals.

  5. If needed, mount the 24H2 ISO manually and run setup.exe for a direct upgrade (keeping your files/apps).

 

These steps often resolve silent rollback issues. If it still fails and you don’t urgently need 24H2, waiting a few weeks or months (?) may bring a patched update from Microsoft.

 

Kind Regards,

 

NonSequitur777


HP Recommended

Hi NonSequitur777, thanks for chiming in.

For some reason I am having issues with SetUpDiag.exe.

I already have it on C:\ So I must have tried to run it before, or, perhaps Windows put it there.

 

I used CMD.exe from C:\Windows\system 32\cmd.exe. I did it this way so I could right click CMD.exe and run it as an elevated Administrator account.

 

Once CMD.exe was loaded, I typed in C:\SetupDiag.exe

 

Once I did this cmd.exe outputted:

SetupDiag v1.7.0.0
Copyright (c) Microsoft Corporation. All rights reserved.

 

Then it outputted a bunch of parameters, to which most stated if no parameters were used, SetupDiag.exe would output a default xml file to the same directory, to which in this case would be C:\

 

Unfortunately, no such .xml file exists on C:\.

 

Please see my attached photo.

000.png

 

I even tried this command, still nothing:

C:\WINDOWS\System32>C:\SetupDiag.exe /Output:C:\SetupDiag\Results.xml /Format:xml

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.