Unable to update (KB5034441) using below links

Anonymous
2024-01-10T05:14:55+00:00

https://support.microsoft.com/en-us/topic/kb5034441-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024-62c04204-aaa5-4fee-a02a-2fdea17075a8

https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf  (I was following steps from this link. I saw that I have 520MB of Healthy Recovery Partition in which I failed to shrink and the error was "you may not shrink OEM, ESPY or recovery partitions, or, offline volumes. The volume you have selected may not be shrunk. Please select another volume and try again.".) (Also when I shrink from C: and then I do not see new partition which suppose to be seen).

So kindly help.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

68 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Ramesh 181.6K Reputation points Volunteer Moderator
    2024-01-23T02:04:32+00:00

    You don't need to expand the WinRE partition because its capacity is 893 MB, which should be sufficient.

    Please start a new thread so that I can post specific instructions for your system.

    Also, see my post below - pasted from another thread:


    Microsoft is working on a fix. Until then, you may ignore the Windows Update error 0x80070643 and wait for an official fix.

    Image


    Important: Follow the workaround only if you're comfortable with the diskpart console tool because it can be a risky procedure. Otherwise, please start a new thread and seek the assistance of an IA or moderator.

    Workaround: Resizing the Recovery partition to 750 MB or more will fix the issue. The error occurs due to a lack of free disk space in the Recovery partition.

    KB5028997: Instructions to manually resize your partition to install the WinRE update - Microsoft Support: https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf

    Caveat: The above Microsoft article assumes the Recovery partition is situated next to the OS partition. That's not necessarily the case in many systems. So, a different approach has to be followed on systems where the Recovery partition is not located near the OS partition. In that case, please start a new thread and seek the assistance of an advisor or volunteer moderator.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-01-22T22:41:04+00:00

    FYI -

    Here are the exact steps I used on many Windows 10 Pro x64 systems to correct this KB5034441 error.

    Open CMD as Administrator:

    Press Windows Key

    Type in "CMD" (without the quotes)

    Click on 'Run as administrator'

    C:>reagentc /info

    Windows Recovery Environment (Windows RE) and system reset configuration

    Information:

    Windows RE status:         Enabled 
    
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE 
    
    Boot Configuration Data (BCD) identifier: 35a5023d-a860-11ee-96cd-f84def5fa1af 
    
    Recovery image location: 
    
    Recovery image index:      0 
    
    Custom image location: 
    
    Custom image index:        0 
    

    REAGENTC.EXE: Operation Successful.

    Note: partition 4 in WinRE.

    C:>reagentc /disable

    REAGENTC.EXE: Operation Successful.

    C:>diskpart

    DISKPART> list disk

    DISKPART> select disk 0

    DISKPART> list partition

    Partition ### Type Size Offset


    Partition 1 System 100 MB 1024 KB

    Partition 2 Reserved 16 MB 101 MB

    Partition 3 Primary 464 GB 117 MB

    Partition 4 Recovery 1007 MB 464 GB

    DISKPART> sel partition 3

    DISKPART> shrink desired=250 minimum=250

    DiskPart successfully shrunk the volume by: 250 MB

    DISKPART> select partition 4

    DISKPART> delete partition override

    DISKPART> create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

    DISKPART> gpt attributes =0x8000000000000001

    DISKPART> format quick fs=ntfs label=”Windows RE tools”

    DISKPART> list vol

    DISKPART> exit

    C:>reagentc /enable

    REAGENTC.EXE: Operation Successful.

    C:>reagentc /info

    Windows Recovery Environment (Windows RE) and system reset configuration

    Information:

    Windows RE status:         Enabled 
    
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE 
    
    Boot Configuration Data (BCD) identifier: 35a5023f-a860-11ee-96cd-f84def5fa1af 
    
    Recovery image location: 
    
    Recovery image index:      0 
    
    Custom image location: 
    
    Custom image index:        0 
    

    REAGENTC.EXE: Operation Successful.

    Restart Windows 10. Install KB5034441 through Windows Update without error.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-01-22T19:52:16+00:00

    Hi Ramesh, after running the command "shrink desired=250 minimum=250", I cannot see any WinRe partition to carry on to the next step:

    To select the WinRE partition, run sel part<WinRE partition index>

    I see only this:

    The shrink command show this in diskpartition (it creates 252mb unallocated space which I can't seem to do anything with now):

    Where is the WinRE index mentioned, and how can I resolve this please?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-01-18T11:33:44+00:00

    Yesterday they said that they are working on this update. We will get an update soon.

    Was this answer helpful?

    0 comments No comments