[SOLVED] Cannot install 2024-04 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5036893) Update. Error code 0x800705b9

LifeGood

Active member
My Windows 11 PC cannot install 2024-04 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5036893). I will get error code 0x800705b9.

I have tried these solutions:
MSConfig then disable all 3rd party services
Turn off my antivirus and antivirus built in firewall
Sfc/scannow
Dism /Online /Cleanup-Image /RestoreHealth
Reset Windows 11 through here >> Reset Windows Update in Windows 11 Tutorial
Repair Windows 11 OS without losing data using option two in here: Repair Install Windows 11 with an In-place Upgrade Tutorial

So far, I can't get this update to install. It will show up " Something didn't go as planned.." When the update progress hit 95%. When I tried to repair Windows 11 through ISO, I will get " Windows 11 has failed to installed" something like that. Please help.
 

Attachments

  • ComponentsScanner.txt
    722 bytes · Views: 2
  • CBS.zip
    15.7 MB · Views: 6
Hi and welcome to Sysnative,

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

  • Fixlist.txt
    983 bytes · Views: 3
Please don't quote my previous post.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool (English) again.

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  • Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
  • Note: Ensure that the List BCD check box is checked at the bottom of the form within the Optional Scan area.
    65467fa1d5e07-637796067a7b1-list-bcd.png
  • Press the Scan button.
  • Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
  • Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
Oh sorry about this

Here are the files requested
 

Attachments

  • Addition.txt
    133.4 KB · Views: 5
  • FRST.txt
    78 KB · Views: 2
Rich (BB code):
2024-04-19 12:28:41, Info                  CSI    00000c99 BFSVC: 'Copying boot files CopyBootManager(Yes) C:\WINDOWS\boot\EFI -> \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot '
2024-04-19 12:28:41, Info                  CSI    00000c9a BFSVC: 'Error creating \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot\bg-BG\ path! Last Error = 0xb7'
2024-04-19 12:28:41, Info                  CSI    00000c9b BFSVC: 'Error copying boot files from C:\WINDOWS\boot\EFI to \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot! Last Error = 0xb7'

This is not an issue with Windows Update, but an issue with your partition layout and/or other drives as it seems.

Rich (BB code):
Windows Boot Loader
-------------------
identifier              {0ac19b96-6ea2-11ee-bb61-04d4c457db91}
device                  ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{0ac19b97-6ea2-11ee-bb61-04d4c457db91}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{0ac19b97-6ea2-11ee-bb61-04d4c457db91}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Rich (BB code):
==================== Drives ================================

Drive c: (OS) (Fixed) (Total:464.49 GB) (Free:258.42 GB) (Model: Samsung SSD 970 EVO Plus 500GB) NTFS
Drive d: (Entertainment Storage) (Fixed) (Total:232.87 GB) (Free:166.59 GB) (Model: Samsung SSD 840 EVO 250GB) NTFS
Drive e: (Entertainment Storage) (Fixed) (Total:2794.5 GB) (Free:710.45 GB) (Model: WDC WD3003FZEX-00Z4SA0) NTFS
Drive f: (Entertainment Storage) (Fixed) (Total:931.51 GB) (Free:533.79 GB) (Model: ST1000DM003-1CH162) NTFS
Drive g: (Storage) (Fixed) (Total:931.5 GB) (Free:43.59 GB) (Model: CT1000MX500SSD1) NTFS
Drive h: (Storage 2) (Fixed) (Total:232.87 GB) (Free:43.88 GB) (Model: Samsung SSD 850 EVO 250GB) NTFS

\\?\Volume{cd31a8b6-cdd9-41a6-bf86-6011ef8f906e}\ (Recovery) (Fixed) (Total:0.51 GB) (Free:0.5 GB) NTFS
\\?\Volume{7d7c7267-e8bd-429f-a7b5-6c7d24e12dfd}\ () (Fixed) (Total:0.64 GB) (Free:0.07 GB) NTFS
\\?\Volume{aa3e22d5-19ba-402a-ab95-a3974a8aa900}\ () (Fixed) (Total:0.09 GB) (Free:0.07 GB) FAT32
 
What do you mean issue with partition layout?

I don't mess with my os drive partitions when I installed Windows 10 os then upgraded to Windows 11 to current state.

Is there a way to fix this?
 
Please post a screenshot of Disk Management, you can open it from the start menu with the command diskmgmt.msc.

Maximize this window - take a screenshot and attach it to your next post.
 
Another pictures
 

Attachments

  • mmc_hjpnRSNr6J.png
    mmc_hjpnRSNr6J.png
    27.2 KB · Views: 8
  • mmc_4a1zGlGZup.png
    mmc_4a1zGlGZup.png
    16.5 KB · Views: 7
  • mmc_QKA7HKm13G.png
    mmc_QKA7HKm13G.png
    16.6 KB · Views: 7
Hi,

Please make a full system image and follow the instructions below to re-create the EFI partition.

Boot the computer using a USB-stick into the RE environment and open the command prompt.

1. Run the following commands.
2. Replace 0 with the actual number for the HDD/SSD where your Windows is installed.
Rich (BB code):
diskpart
list disk
select disk 0
list partition
3. Then run the following command and replace 1 with the actual number for the Windows OS partition.
Rich (BB code):
select partition 1
4. The following commands will resize the Windows OS partition and create a new EFI partition.
Rich (BB code):
shrink desired=100
create partition efi size=100
format quick fs=fat32
assign letter=w
5. Run the following commands
Code:
list partition
list volume
6. Note the drive letter where the Windows OS is installed, which is displayed after running list volume.
7. Close diskpart with the following command
Code:
exit
8. Run the following command: Replace X with the volume letter of the Windows OS partition.
Code:
bcdboot X:\windows /s W:
9. Now the BCDBoot copies the boot files from the Windows partition into the EFI System partition and re-create the BCD store in the same partition.
 
Done
Now I have 2 EFI System Partition in my Disk 5? Disk 5 is where Windows OS installed.

Attached 2 new pictures
 

Attachments

  • Screenshot 2024-04-21 162053.png
    Screenshot 2024-04-21 162053.png
    108.5 KB · Views: 1
  • Screenshot 2024-04-21 161734.png
    Screenshot 2024-04-21 161734.png
    35.5 KB · Views: 1
Did I do the step right? There are two efi partition now. I plug in new windows 11 bootable usb then repair my computer option then command prompts then type in the codes you provided.
 
Hi,

We can remove the other EFI partition later, please try to perform a repair install again and let me know if it was successful or not this time.
 
@Maxstar

I still can't perform windows os repair through windows 11 iso. It will give this error when the progress hit 100% and try to restart the system.
" Windows 11 installation has failed "
 
Hi,

Download and run SetupDiag from Microsoft
  • Download
    60e45c659164d-SetupDiag.png
    SetupDiag to your desktop.
  • Right-click on SetupDiag.exe and select Run as administrator.
  • When completed the following files are created: "Logs.zip, SetupDiag.exe.config and SetupDiagResults.log"
  • Attach SetupDiagResults.log and Logs.zip to your next reply.
 
Back
Top