First off, from the screenshot you posted of SFC, I may be blind but I do NOT that SFC was run nor any results.
Please run SFC again using
sfc /scannow
This 24h2 upgrade is an entirely different beast than we've seen in the past causing havoc for a lot of people with all different kinds of problems either during the upgrade, or afterwards. For some it takes a clean install to get it. You might want to hang tight and stay on 23h2 for a while. If you pursue the upgrade, I strongly suggest you make a full system image before you go any further.
One known reason for upgrade failure is WD drives. Do you have Western Digital drives? If so that could be the problem since certain WD drives require a firmware update from WD before upgrading to 24h2.
To try to get more direction of the failure you would need to look at the failure logs to see the cause of your failure. Depending on where in the install the failure occurs, the log can be in multiple places.
The following log files are created when an upgrade fails during installation
before the computer restarts for the second time. You have to look at these logs to get an idea of why the upgrade failed. Naturally, the logs are in MS speak but they might give you a place to start.
- C:\$Windows.~BT\Sources\panther\setupact.log
- C:\$Windows.~BT\Sources\panther\miglog.xml
- C:\Windows\setupapi.log
- [Windows 10:] C:\Windows\Logs\MoSetup\BlueBox.log
- C:\Windows\inf\setupapi.app.log
- C:\Windows\inf\setupapi.dev.log
- C:\Windows\panther\PreGatherPnPList.log
- C:\Windows\panther\PostApplyPnPList.log
- C:\Windows\memory.dmp
The following log files are created when an upgrade fails, and then you restore the desktop:
- C:\$Windows.~BT\Sources\panther\setupact.log
- C:\$Windows.~BT\Sources\panther\miglog.xml
- C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log
- C:\$Windows.~BT\sources\panther\setupapi\setupapi.app.log
- C:\Windows\memory.dmp
The following log files are created when
an upgrade fails, and the installation rollback is initiated:
- C:\$Windows.~BT\Sources\Rollback\setupact.log
- C:\$Windows.~BT\Sources\Rollback\setupact.err
Mine rolled back so I found mine in the last 2 logs..
If logfiles do not direct you to what caused the error, I advice anyone to not waste his time. Either stay where you are and wait for MS to work this mess out or Bite the bullet and do a clean install. 24h2 will have you chasing your tail for days.
You can also run through these general WU troubleshooting steps to fix corruption within WU itself.
1. Run troubleshooter-settings-system-troubleshoot-other troubleshooters-windows update-RUN.
2. Reset Windows update using Brink's tutorial Reset Windows Update in Windows 11 Tutorial
3. Run sfc after resetting update components. Open a command prompt as administrator and type sfc /scannow
Pay attention to the scan results to see if SFC found anything it could not repair. If it found corruption it could not fix followup with this command (note the spaces)
dism /online /cleanup-image /restorehealth
Restart computer
4. CLEAN UP COMPONENT STORE - dism /online /cleanup-image /startcomponentcleanup
Analyze and Clean Up Component Store (WinSxS folder) in Windows 11 Tutorial
The upgrade can also be applied manually. You can download the 24h2 iso and attempt to install 24h2 with an In-place Upgrade , but don't bet your paycheck it will work. You might get lucky. Although an in-place upgrade is done from within windows, I suggest you create a usb installation drive from the downloaded iso in case you need it to do a clean install.The media creation tool can do that or IMO the preferred method is to download the ISO and use Rufus to create the usb drive. The portable version of Rufus works fine for this purpose..
tutorial
Repair Install Windows 11 with an In-place Upgrade
iso download
Download Windows 11
Rufus
Rufus - Create bootable USB drives the easy way
