Windows 11 26H2 upgrade rolls back after reboot when using Windows11UpdateAssistant

Ajay Vernekar 0 Reputation points
2026-11-19T08:40:41.9466667+00:00

Over the last couple of days, I have been attempting to install Windows 11 26H2 on multiple systems using Windows11UpdateAssistant.exe. The tool completes successfully, displays a success message, and automatically reboots the device after approximately 30 minutes. However, during the reboot phase, the installation fails and Windows rolls back to the previous version.

Setupact.log and setuperr.log errors:

2026-11-14 12:40:25, Error SP CAddCbsPackage::DoExecute: Failed to add package Add [2] package C:$WINDOWS.~BT\DUImageSandbox\metadata\Windows11.0-KB5043080-x64 to C:$WINDOWS.~BT\NewOS. Error: 0x80070057

2026-11-14 12:40:26, Error SP Operation failed: Add [2] package C:$WINDOWS.~BT\DUImageSandbox\metadata\Windows11.0-KB5043080-x64 to C:$WINDOWS.~BT\NewOS. Error: 0x80070057 [gle=0x000000b7]

 setuperr.log

It seems to be issue with Windows11UpdateAssistant.exe setup. last week we tried installation, it worked fine, but from last couple days we are facing this issue. Not sure but the issue seems to be occurred after November Patch Tuesday.  

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade

3 answers

Sort by: Most helpful
  1. Petrichor 0 Reputation points
    2026-11-20T15:05:03.3833333+00:00

    I did successfully fix this after I spent two days wrestling with this issue using Claude/Opus 5.5 though I was trying to update from 23H2 after manually halting the upgrade process due to fear of the Recall Function, and found that at every attempt, the process would roll back right before completion.  Because Claude utilized help online to find similar issues and used that info to troubleshoot, I wanted to add the fix for others that may be facing similar issues... Below is Claude's summary...

    Confirming a workaround for this. I had the same failure: the Installation Assistant rolled back with 0xC1900101, and SetupDiag showed 0x80070057-0x20003 in the Safe OS phase while adding DUImageSandbox\metadata\Windows11.0-KB5043080-x64.

    What worked (upgrading from 23H2 Home, Nov 19, 2026): I made a USB with the Media Creation Tool, ran setup.exe from it inside Windows, clicked “Change how Setup downloads updates” and chose “Not right now” (which turns off Dynamic Update), and kept personal files and apps. It upgraded from 23H2 to 26H2 on the first try.

    Background, in case it helps someone:

    • Lenovo laptop. I had recently cloned Windows onto a new 2 TB SSD, and the old SSD is now a data drive. The clone left the recovery image (winre.wim) missing, but that didn’t block the upgrade, and the successful upgrade restored it (reagentc /info now says Enabled). Since others hit this same error without any cloned drive, I don’t think the clone caused it.
    • Earlier attempts through Windows Update (25H2, then 26H2) also rolled back. There, setup had failed to download Dynamic Update and then crashed in MigStore.dll (ACCESS_VIOLATION) during the final restart. So Dynamic Update was involved in every failure, either failing to download or delivering a package that wouldn’t install.
    • Things that didn’t fix it: sfc /scannow, DISM /RestoreHealth, chkdsk, removing an old Windows Update policy key, uninstalling Malwarebytes, and ruling out USB devices and drivers. All came back clean, and none of them changed the result.
    • With Dynamic Update turned off, setup skips the last-minute updates, so run Windows Update afterwards.

    Was this answer helpful?

    0 comments No comments

  2. Ajay Vernekar 0 Reputation points
    2026-11-19T10:28:01.2333333+00:00

    Was this answer helpful?

    0 comments No comments

  3. Harry Phan 36,850 Reputation points Independent Advisor
    2026-11-19T09:19:57.55+00:00

    Hello Ajay,

    Based on the logs, the upgrade fails during the Dynamic Update servicing phase when Setup attempts to add the KB5043080 package to the new Windows image. Error 0x80070057 indicates an invalid parameter, but it does not necessarily mean Windows Update Assistant itself is defective.

    I recommend checking the component store first by running:

    DISM /Online /Cleanup-Image /RestoreHealth

    sfc /scannow

    Then, run SetupDiag to identify the actual rollback cause and review C:\$WINDOWS.~BT\Sources\Panther and C:\$WINDOWS.~BT\Sources\Rollback for additional errors.

    As a workaround, try performing the upgrade using an official Windows 11 ISO instead of the Update Assistant. If the issue persists across multiple devices, compare their SetupDiag results to determine whether they share the same servicing failure.

    Please share the SetupDiag output and relevant Panther logs for further investigation.

    Best regards,

    Harry P.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.