Forum Discussion
in-place upgrade fails from b29574 to latest vnext b29595
Hi all,
is anyone facing the same issue IPU fails on a fresh b29574 upgrading to latest using WU?
provided more information in feedback hub. Thanks for sharing your experience.
as a next attempt I will mount ISO and upgrade. mind b29574 was the base bare metal installation so no previous IPUs involved.
related feedback https://aka.ms/AA11g03n
Tested Upgrade Paths
| Baseline | TargetOS | Result |
| 29574 | 29595 | fails |
| 29574 | 29602 | fails |
| 29595 | 29602 | fails |
Installed roles:
- Hyper-V
Specialities:
- tried SysWOW64 removal but failed to do so https://aka.ms/AA11eyy5
- OS Drive is ReFS, potientially related https://aka.ms/AA11eyy8
<?xml version="1.0" encoding="utf-16"?>
<SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag">
<Version>1.7.0.0</Version>
<ProfileName>FindRollbackFailure</ProfileName>
<ProfileGuid>3A43C9B5-05B3-4F7C-A955-88F991BB5A48</ProfileGuid>
<FailureData>0xc1900101-0x20017 Error: SetupDiag reports rollback failure found.Last Phase = FinalizeLast Operation = Cleanup external drivers after installationError = 0xC1900101-0x20017</FailureData>
<FailureData>LogEntry: </FailureData>
<FailureData>Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.</FailureData>
<FailureDetails>RollbackErrorCode = 0xC1900101, ExtendedCode = 0x20017, LastOperation = Cleanup external drivers after installation, LastPhase = Finalize</FailureDetails>
<Setup360Result>0xc1900101</Setup360Result>
<Setup360Extended>0x20017</Setup360Extended>
<SetupPhaseInfo>
<PhaseName>Finalize</PhaseName>
<PhaseStartTime>06/06/2026 13:16:53</PhaseStartTime>
<PhaseEndTime>06/06/2026 13:17:35</PhaseEndTime>
<PhaseTimeDelta>0:00:00:42.0000000</PhaseTimeDelta>
<CompletedSuccessfully>true</CompletedSuccessfully>
</SetupPhaseInfo>
<SetupOperationInfo>
<OperationName>Cleanup external drivers after installation</OperationName>
<OperationStartTime>06/06/2026 13:17:35</OperationStartTime>
<OperationEndTime>06/06/2026 13:17:35</OperationEndTime>
<OperationTimeDelta>0:00:00:00.0000000</OperationTimeDelta>
<CompletedSuccessfully>true</CompletedSuccessfully>
</SetupOperationInfo>
</SetupDiag>
also noticing uncommon links in root as if I were using FAT32.
13 Replies
realy, Microsoft is more on AI integration than stability and user ergonomy. With every new update my machine is slower.
Hi WS Insiders, has anyone tested the scenario of in-place upgrades (VM or harware) with later builds than b29595 yet?
Important: make sure your OS drive is formatted ReFS, to comply with the issue report and scope.Hi Karl-WE I was trying to replicate this, but using b26085 thinking to target to b29621 wich are the only available previews right now.
However, b26085 failed to install using ReFs.
If you need I have number of ISOs I could provide via OneDrive. Let me know if you need a slightly older one than b29621. The 26000 build might not have ReFS OS boot.
Cannot remember when this has been released.
Many thanks.
There is a new feedback item and collection for this
added a zipped Windows.BT folder without the payload for better investigation.
All right, it seems you just have to link your Microsoft account in the Windows insider settings in Windows Update. Once you do, it will it’ll pull the latest build for IPU
Actually this still didn’t work. It went all the way through the installation but then reverted changes at the end and did not update. Ah well. At least I’m not the only one
I also have been unable to in place upgrade on any of these 295 builds.
I’m seeing the same issue here. Looks like the rollback is happening during driver cleanup (0xC1900101-0x20017). Since you’re on ReFS + Hyper-V, that could definitely be related. Trying the ISO upgrade sounds like a good next step — please update if it works.
Nandlapro4232 was about testing IPU with ReFS from 29595 to 29602 but it is not offered.
Hi Nandlapro4232 for me neither way worked, tested ISO and Windows Update.
If you are using ReFS on drive C please upvote the feedback links.
Can also add log as zip from c:\Windows\panther or $Windows.BT
same issue using ISO and setup.exe
Worse, setup.exe of b29595 will be blocked by smartscreen.
