Windows 11 Pro: Windows Update Fails at 98% and Repair Install Fails at 88%

zbook said:

There is a pay product that advertises moving apps.

After the latest troubleshooting steps a failed in place upgrade may report new failure information.

Click to expand...

zbook said:

1) To view the installed language:

dism /online /Get-Intl





2) The newest iso/mct

Download Official Windows 11 ISO file from Microsoft

This tutorial will show you how to download an official Windows Server or Windows 11 64-bit or ARM64 ISO file from Microsoft. Microsoft provides ISO files for Windows Server and Windows 11 to download. You can use these ISO files to clean install or in-place upgrade Windows 11. The Flight Hub...

www.elevenforum.com

Download Windows 11

3) Place the computer into clean boot.

Perform a Clean Boot in Windows 11 to Troubleshoot Software Conflicts

This tutorial will show you how to perform a clean boot to start Windows 10 or Windows 11 using a minimal set of drivers and startup programs for troubleshooting application conflicts. Troubleshooting Windows can be a complex process due to the many different drivers, settings, and programs...

www.elevenforum.com

4) Disconnect from the internet (ethernet and wifi)




5) Disconnect all non-Windows drives

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 154.9 GB
Total Space: 228.1 GB
File System: NTFS
      Model: KINGSTON SHSS37A240G

      Drive: D:
 Free Space: 172.9 GB
Total Space: 228.9 GB
File System: NTFS
      Model: KINGSTON SHSS37A240G

      Drive: E:
 Free Space: 864.0 GB
Total Space: 1717.2 GB
File System: NTFS
      Model: Samsung SSD 870 EVO 4TB

      Drive: F:
 Free Space: 710.9 GB
Total Space: 915.7 GB
File System: NTFS
      Model: KINGSTON SUV400S37960G

      Drive: G:
 Free Space: 453.7 GB
Total Space: 476.9 GB
File System: NTFS
      Model: Samsung SSD 850 EVO 500GB

      Drive: H:
 Free Space: 252.3 GB
Total Space: 2098.2 GB
File System: NTFS
      Model: Samsung SSD 870 EVO 4TB

      Drive: I:
 Free Space: 704.1 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: CT2000BX500SSD1

6) Make sure it is an in place upgrade repair using the iso (not upgrade assistant):

Create Windows 11 Bootable USB Installation Media

This tutorial will show you how to create a bootable USB flash drive used to install Windows 11 with UEFI support. You can use a Windows 11 installation USB flash drive to clean install, upgrade, reset, or repair Windows 11. The installation USB can also be used as a recovery drive to boot to...

www.elevenforum.com

Repair Install Windows 11 with an In-place Upgrade

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

7) Post new failure log share links for troubleshooting:




a) Upgrade_failure_info.bat > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/353454d1638278360-batch-files-use-bsod-debugging-upgrade_failure_info.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

b) V2 log collector




c) Post share links:

C:\Windows\Logs\CBS\CBS.log

C:\Windows\Logs\CBS\CbsPersist

Click to expand...

zbook said:

If you post the log share links (upgrade failure etc.) with the error code 0xC1900101 - 0x4000D (post #123) I'll scan them in the evening.




See earlier in the thread Windows Driver Verifier (WDV).

Click to expand...

lafargeotte said:

Any suggestions to transfer apps from old to new windows please?

Click to expand...

lafargeotte said:

CBS: Microsoft OneDrive

WDV to follow.

Click to expand...

zbook said:

If you post the log share links (upgrade failure etc.) with the error code 0xC1900101 - 0x4000D (post #123) I'll scan them in the evening.




See earlier in the thread Windows Driver Verifier (WDV).






0xC1900101 - 0x4000D







Code------------------Mitigation------------------------------------------------------------------------Cause

0xC1900101 - 0x4000D

Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors. Review the rollback log and determine the stop code. The rollback log is located in the $Windows.~BT\Sources\Rollback folder. An example analysis is shown below. This example isn't representative of all cases: Info SP Crash 0x0000007E detected Info SP Module name : Info SP Bugcheck parameter 1: 0xFFFFFFFFC0000005 Info SP Bugcheck parameter 2: 0xFFFFF8015BC0036A Info SP Bugcheck parameter 3: 0xFFFFD000E5D23728 Info SP Bugcheck parameter 4: 0xFFFFD000E5D22F40 Info SP Can't recover the system. Info SP Rollback: Showing splash window with restoring text: Restoring your previous version of Windows. Typically, there's a dump file for the crash to analyze. If you aren't equipped to debug the dump, then attempt the following basic troubleshooting procedures: 1. Make sure you have enough disk space. 2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. 3. Try changing video adapters. 4. Check with your hardware vendor for any BIOS updates. 5. Disable BIOS memory options such as caching or shadowing.

A rollback occurred due to a driver configuration issue. Installation failed during the second boot phase while attempting the MIGRATE_DATA operation. This can occur because of incompatible drivers.

Click to expand...

zbook said:

Was setup.exe ran from the iso?

This is what is needed: $Windows.~BT\Sources\Rollback folder.

For failed in place upgrade repair with rollback this script will collect it if the failed in place upgrade created it:

a) Upgrade_failure_info.bat > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/353454d1638278360-batch-files-use-bsod-debugging-upgrade_failure_info.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Click to expand...

lafargeotte said:

Unfortunately the Repair Install hung at 83% and I had to roll back to image taken just before I started.

The only thing I was able to get was:
0xC1900101 - 0x4000D
The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation

Click to expand...

0xC1900101​

• The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp
• Event logs: $Windows.~bt\Sources\Rollback*.evtx
• The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

zbook said:

Microsoft:

0xC1900101​

A frequently observed result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the downlevel phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as:

• The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp
• Event logs: $Windows.~bt\Sources\Rollback*.evtx
• The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

The device install log is helpful if rollback occurs during the sysprep operation (extend code 0x30018).

To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a clean boot before initiating the upgrade process.

See the following general troubleshooting procedures associated with a result code of 0xC1900101: (post #125)


There were no $Windows.~BT\Sources panther/rollback files posted/available for troubleshooting.

Click to expand...

hader said:

That is not possible. As soon a new install is finished all programs are gone and the registry contain no formers apps info. I know of a program that moves any program to another disk and change the registry to reflect the new location. In this case? Worthless. During a new install an empty registry with basic program and driver is made. The connection to the other location is just gone.

New installation. Done this 10+ times. In the end you realize you had to much unwanted programs anyways. Make a list of what you really need to be re-installed. Ik have a separate USB stick where all my installed programs I want to see newly installed again are located. Reinstalling them is not the main issue here; your personal data is so much more important. Re-installing programs is the least of the problems, searching for forgotten missing personal data is!!!

Make sure that you make a Hasleo backup of your complete C-disk first! You can later on forgotten files back with the restore files function.
Make a copy of your C:\Users\<Username> to another disk (check the size on the C-drive and check there is enough space at the Backup location)
Instead of using explorer for this (It will give you a bunch of errors and headache because of hidden files, inaccessible directory's, locked files etc.)

I have placed a .txt file in the attachment. You can download this .txt file (because this site is cautious with things that can be executed.) Download it and rename it to a .cmd file. Copy it to any location you want. You have to edit at the top of this file and replace <BackupDrivePath> with a driveletter:\Path and <Username> with your name.

If Robocopy encounters locked files? It's clever enough to skip them. There is no need to copy these locked files. They are locked by Windows current running processes and are useless in a new installation. The new installation will just create new ones that are valid. Those old files belongs to the old Windows installation!

The /L switch now is just a simulation and will be done within a few seconds. It does not copy files. Inspect the <BackupDrivePath>\Logs\copy_userdir.log for any errors. If this is OK you can then remove that /L switch for the real copy run.
This script makes a <BackupDrivePath> dir and \Logs. Change the name of the path if it should be called something else.....

This script leaves directory's behind that are useless. History, Temp Files, Hidden files. Worthless info after a new installation. Those files will be there again as soon as you start to use Windows. Just don't copy the backup back again blindly. The backup (C:\Users\<Username>\Appdata\ Local, Locallow and Roaming.) it is filled with directory's that programs made during the installation. If you do not install these programs again; those extra dir's are additional garbage......

It's to bad that Windows don't keep a trace on them once you de-install a program...... It will not remove those directory's! (Once in a while I look at these dirs. Some are visible related to a program others not (unfortunately) I see a known dir of a program that I de-installed some time again: Delete!!!)

I just adjust this Robocopy script on my machine and ran it... Success..... The 1st initial run takes a "long" time; 70Gb in 1:51 min. Benefit of having fast NMVe disks. (69Gb without Hidden, History and Temp files) Duration depends how large that <Username> dir is and how fast your disks are.

After a real first run a 2nd run will finish in matter of seconds. Robocopy checks for changes. Add new files or delete deleted files at the copy location since the previous run. So in the end: Data of C:\Users\<Username> will always = backup location every time you run this script....
So you can use this script in the attachment if you want......

Start this script with explorer with "Run as administrator".... *rename it first from "Copy-Users_General instr.txt" into "Copy_<Username>.cmd"*

Click to expand...

lafargeotte said:

I installed a clean windows 11 now.

Click to expand...

Ghot said:

Probably a good time to make a fresh backup. ^^

Click to expand...

lafargeotte said:

Already have, thank you.

Click to expand...

Megahertz said:

Please mark this thread as Solved

Click to expand...

lafargeotte said:

The actual thread has not solved anything, has it?

Click to expand...

Ghot said:

Well, you solved it. So that counts as solved.

Click to expand...