Fixing an Unbootable Windows 11 OS

• A week ago, I booted my PC normally on the SSD running Windows 11 (Version 22631.4751). I then realised that I actually want to access my dormant Windows 10 installation running on a second SSD. I assess this Win10 OS infrequently and up until now it has been running fine.
• I restart, enter BIOS and force the system to boot into the SSD running Win10, as I've done several times before. The OS loads very slowly, I manage to log in, but I'm presented with a black screen. The mouse is still visible, and I can open task manager with Ctrl+Alt+Delete. I restart and this time the system doesn't boot past the windows logo loading screen.
• I restart back into BIOS and select the Win11 SSD to boot from. As Windows was loading, I remember seeing a repair message down the bottom of the screen informing me that it was copying files to one of my SSDs. After this, windows progressed to, and hung on a black screen which didn't accept any input from me. Rebooting gets me as far as a few seconds of the windows loading screen and then black. From my notes I think I also received a NTFS File System BSOD at some point in this process, but I can't remember the order and it hasn't appeared since.
• After a hasty google I ran the bootrec /fixboot, bootrec /scanos, bootrec /rebuildbcd, bootrec /FixMbr commands into command prompt from the recovery environment. This did nothing because, as I later found out, they don't work with a GTP disk. I also made some unwise bcdedits to the Boot Loader, changing the device field as I thought it was pointing to the wrong disk. As a result, I lost access to the recovery partition (nice ). After this, when it tries to access the recovery partition I get error codes: 0xc000000e (referring to winload.efi), 0xc0000225, 0xc000000f (referring to winload.efi), 0xc0000001.
  
  
• Now accessing command prompt from a USB I created with the windows media creation tool (Windows version: 26100.2033), I attempted to fix the Boot Manager.
  • I followed this guide, which ultimately had me running the command, 'bcdboot C:\Windows /l en-us /s k: /f ALL'. The boot manager looked correct after this, but windows still presented a couple of seconds of logo and loading screen, then eternal black.
  • I then followed this guide which had me format the system partition and then rebuild it with a similar command to the above one. Afterwards, there was no change and windows still booted to a black screen.

• I then tried to boot into safe mode by editing the Boot Loader with the command 'bcdedit /set {default} safeboot minimal'. Windows no longer boots into a black screen but instead displays the windows logo and loading circle for eternity (at least 45min).
  
  
• I tried to enter boot debugging but I don't have the required USB cable and apparently my NIC isn't supported by my Win11 version.
  
  
• At some point I troubleshooted my hardware by:
  • Disconnecting all external devices except for the keyboard, mouse and monitor.
  • Disconnecting the win10 SSD
  • Removing the GPU and using integrated graphics instead.
  • Testing with only one RAM stick installed at a time.
  • Running the NVMe test in the BIOS
  • Loading default BIOS settings.

• I then ran the System File Checker using the command, "sfc /scannow /offbootdir=c: /offwindir=c:\windows" from this guide.
  • This found corrupt files but was unable to fix some of them.

• I ran Check Disk was the command, chkdsk c: /f.
  • This found no problems.

• I then tried to fix the problem using DISM using this guide, this one and info from all over the place.
  • I ran Checkhealth with, "dism /image:d:\ /cleanup-image /checkhealth".
    • I get, "the component store is repairable."
  • I ran Scanhealth with, "dism /image:d:\ /cleanup-image /checkhealth".
    • I get, "the component store is repairable."
  • I ran Restorehealth with, "dism /Image:\ /Cleanup-Image /Restorehealth".
    • I get Error: 0x800f081f the source files could not be found.
  • To rectify this I've tried:
    • dism /image:c:\ /cleanup-image /restorehealth /source:d:\sources\install.esd (d:\ being the USB with the 26100.2033 install)
    • dism /image:c:\ /cleanup-image /restorehealth /source:d:\sources\install.esd /limitaccess
    • dism /image:c:\ /cleanup-image /startcomponentcleanup
      • I haven't tried /ResetBase yet, if that will make any difference?
    • dism /image:c:\ /cleanup-image /revertpendingactions
    • Downloading from UUP Dump, an ISO with the same version as the problem win11 (22631.4751) and attempting the same commands above.
    • This downloaded as a wim file so I then tried this command:
      • dism /image:c:\ /cleanup-image /restorehealth /source:wim:d:\sources\install.wim:1 /limitaccess
    • Downloading an ISO containing the latest build of 23H2 (22631.4890) and attempting the commands above.
    • All received the same error.

• I also used Hiren's BootCD PE and EaseUS to create a small partition on the Win11 SSD and then install a fresh copy of Windows on it (26100.3194).
  • I now dual boot into this 'workshop' OS (as I'll now call it). It boots normally and since then I've been attempting to fix the original Win11 from here.

• I'm currently up to attempting to manually repair the corrupted manifests that DISM has identified, using the Microsoft guide Fix Windows Update corruptions and installation failures.
  • Some of the manifests have an Update Build Revision (UBR) number of 22621.4751 which appear to come from update KB5050021, but after downloading and unpacking the update I can't find the files inside.
  • Some of the manifests have a UBR number of 22621.4746 and I have no idea where I can get copies of these.
  • I also noticed that some of these manifest list "en-gb" after their UBR number, while some list "en-us" and others "none"
    • I remember reading forum posts where people recommended using English UK installation media to try and avoid the DISM 0x800f081f error. I did try this at the time to no avail, but could these be where some of these files are located?
    • Running the command: DISM /image:d:\ /Get-Intl (d:\ is now the path to the troubled Win11 from the workshop OS I've created)
      • Image Version: 10.0.22631.4751
        
        Reporting offline international settings.
        
        Default system UI language : en-US
        System locale : en-US
        Default time zone : AUS Eastern Standard Time
        User locale for default user : en-AU
        Location : Australia (GEOID = 12)
        Active keyboard(s) : 0409:00020409, 0c09:00000409
        Keyboard layered driver : PC/AT Enhanced Keyboard (101/102-Key)
        
        Installed language(s): en-GB
        Type : Partially localized language, MUI type.
        Fallback Languages en-US
        Installed language(s): en-US
        Type : Fully localized language.
  • My next step along this path is to reinstall the 'workshop' win11 using the 22631.4751 ISO downloaded from UUP Dump and see if I can source replacements for the corrupted files from it.

• I would however really just like DISM to sort this out for me, so any advice on how to get this to work would be most appreciated.
  • To help with troubleshooting this I've attached a DISM log that was generated after running the command:
    • dism /image:d:\ /cleanup-image /restorehealth /source:wim:f:\sources\install.wim:1
      • d:\ being the location of the broken win11
      • f:\ being where the ISO (version 22631.4890) mounted itself after double clicking on it.
      • Index 1 is the only index in the wim file and it's win11 Pro.
  • I have only just started to learn how to read this, but a few lines jump out to me:
    • 2025-02-14 11:07:30, Info CBS Failed to find a matching version for servicing stack: d:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.4740_none_e928b4ac42f6002b\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    • 2025-02-14 11:07:30, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    • 2025-02-14 11:07:30, Info CBS Offline servicing, using stack version from: d:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.4740_none_e928b4ac42f6002b\cbscore.dll
    • 2025-02-14 11:07:30, Info CBS Loaded Servicing Stack v10.0.22621.4740 with Core: d:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.4740_none_e928b4ac42f6002b\cbscore.dll
    • 2025-02-14 11:07:30, Info CBS Setting core mode: CbsCoreModeOffline
      
      
    • 2025-02-14 11:07:31, Info CBS Exec: Addsource called, Session: 46260_135867390, Client: DISM Package Manager Provider, from GPO: No, Path: wim:f:\sources\install.wim:1
    • 2025-02-14 11:07:31, Error CBS Cannot add wim: file source because it is not supported during offline servicing [HRESULT = 0x800f082e - CBS_E_NOT_ALLOWED_OFFLINE]
  • How this reads to complete novice like me, is that CBS is unable to find the correct "servicing stack" until going into "offline servicing", but then later on determines that it can't use the provided wim because "it is not supported during offline servicing". Am I close? Is this a clue or just part of normal ops?

FreeBooter said:

Get yourself the latest Windows 11 bootable media and boot your computer with it and see my video instructions will help.

In this video, i will guide you on how to resolve "The source files could not be found" dism error code 0x800f081f message.

Click to expand...

tecknot said:

Hi Seymour,

I had the same error with my dual boot system too. What I ended up doing was starting from scratch on my Windows 10 boot. I started at Diskpart and ran the "clean" command on the Win10 disk, recreated the Windows 10 install partitions and then reinstalled Windows 10. I then got my system booting properly including my Window 11 drive still intact. So, at that point I restored a backup of Windows 10 and all was well again. It was pretty daunting as you have experienced, I did the same steps in an effort to fix my system. It wasn't until I got desperate that I cleaned my Windows 10 drive.

If you have a backup of your Windows 10 installation, I would strongly suggest you give my solution a shot. If you don't have a backup, then follow zbook's instructions to the letter.

Kind regards,

tecknot

Click to expand...

Seymour Skinner said:

Hi FreeBooter, thanks for getting back to me with that solution. I have seen your video linked in a previous thread and unfortunately it didn't work for me. I'm trying to get my DISM to repair an offline image, which I think is causing it problems in accessing the wim file on my USB.


Cheers zbook, I'll get on it!



Hey tecknot, thanks for the advice. Are you saying that you were originally unable to boot from your win11 and win10 drives? Then after rebuilding your win10 drive only, you were able to access both drives again?

Click to expand...

Seymour Skinner said:

Hi FreeBooter, thanks for getting back to me with that solution. I have seen your video linked in a previous thread and unfortunately it didn't work for me. I'm trying to get my DISM to repair an offline image, which I think is causing it problems in accessing the wim file on my USB.

Click to expand...

zbook said:

1) Find several flash drives that you can format (> or = 8 GB)

2) Find a working Windows computer.

3) On the working Windows computer create tools that can be used on the problematic computer.


4) Create a bootable Sea Tools flash drive

https://www.seagate.com/content/dam/seagate/migrated-assets/old-support-files/seatools/USBbootSetup-SeaToolsBootable.zip

SeaTools | Seagate US

SeaTools - Quick diagnostic tool that checks the health of your drive.

www.seagate.com

5) Create a bootable Windows 11 Media Creation Tool (MCT) (Windows 11 iso)

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

6) Create a bootable Windows 10 Media Creation Tool (MCT) (Windows 10 iso)

Download Windows 10 ISO File

How to Download Official Windows 10 ISO file from Microsoft

www.tenforums.com

Download Windows 10

7) Run the Sea Tools Long generic test (all drives) > take pictures > post images or share links

8) If the Long generic test result reports fail then backup files and replace the drive

9) If the Long generic test result report pass then boot to the Windows 11 MCT

Option #7:

Boot to Advanced Startup (WinRE) in Windows 11

This tutorial will show you how to boot to the advanced startup (WinRE) in Windows 11. The Windows Recovery Environment (WinRE) is a companion operating system installed alongside Windows 11, typically in a separate partition, that can help with troubleshooting, recovery, or booting from...

www.elevenforum.com

Open command prompt > type or copy and paste:

Code:

notepad
notepad
bcdedit
bcdedit | find "osdevice"

Code:

notepad
notepad
diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel dis 1
det dis
lis par
sel dis 2
det dis
lis par

Click to expand...

FreeBooter said:

Because component store is corrupted does not mean this is the reason Windows 11 won't boot as i have asked do you get any boot error message also did you execute Sfc command?

Click to expand...

• I created a 60GB partition on the original SSD and installed the same version of windows as the problem version (22631.4751).
  • I downloaded the appropriate ISO from UUP Dump.
  • I installed this version of windows without an internet connection (so it wouldn't update itself to the latest version) using this guide.
• Once installed, I booted onto it, turned off automatic updates, and ran the /restorehealth command. For the source, I directed it to the windows folder of the operating system I had just installed. The exact command I used is below:
  • Dism /image:d:\ /cleanup-image /restorehealth /source:c:\windows.
  • d:\ being the broken install of windows and c:\ being the freshly installed one of the same version.
  • This fixed 47 of my 50 corrupted manifests.
  • The source was unable to be found for the last three.
• To fix the remaining three, I checked and googled their names to determine that they were from a language pack (Australian)("en-gb" after their UBR number was a clue) and the SmartScreen security service. To obtain these manifests I did the following:
  • I enabled the SmartScreen service.
  • I installed the Australian language pack through the normal Windows language interface.
• I could now see the last three files in the C:\ partition's manifest folder and ran the above DISM command again, the operation completed successfully.
• Surely there is an easier way to do this by having DISM use the install.wim file as a source, but I couldn't get it to access it while repairing an offline image.

If win11 tries to enter the recovery environment I get the following error codes, 0xc000000e (referring to winload.efi), 0xc0000225, 0xc000000f (referring to winload.efi), 0xc0000001.

Click to expand...

zbook said:

On the working Windows partition please run the V2 log collector > post a share link

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

On the problematic Windows partition please boot to window RE

Type:

bcdedit | find "osdevice"
bootsect /nt60 all

post a share link



type: notepad
type: notepad
type: notepad
(this will open three notepad windows)

click file open

search for these files > if found > save to the windows iso flash drive > move the flash drive to a working computer > post results into this thread using share links

Code:

C:\windows\minidump
C:\windows\memory.dmp
C:\windows\livekernelreports
C:\windows\logs\CBS\CBS.log
C:\windows\logs\CBS\CbsPersist
C:\windows\system32\logfiles\srt\srttrail.txt

or

Code:

%systemroot%\minidump
%systemroot%\memory.dmp
%systemroot%\livekernelreports
%windir%\logs\cbs\cbs.log
%windir%\logs\CBS\CbsPersist
%windir%\System32\LogFiles\Srt\SrtTrail.txt

Click to expand...

FreeBooter said:

In this video, i will guide on how to Fix Winload.efi is Missing or Contains Errors Message.

Click to expand...

• Format “v”: /fs:fat32
• Bcdboot “c”:\windows /s “v”: /f UEFI

Seymour Skinner said:

Hey FreeBooter, I ran the bootrec /fixboot & /rebuildbcd commands at the start of my trouble shooting process without success. I ultimately formatted and rebuilt the system partition using the following:

• Format “v”: /fs:fat32
• Bcdboot “c”:\windows /s “v”: /f UEFI

But this did not resolve my problem, is there anything further that I can do in this area?

Click to expand...