Windows update (KB5034441) Error (0x80070643)

Might want to try a CLEAN Win 10 install with a thumb drive created ESD made from Windows Recovery. You will loose all your programs and data so back up your Personal Info first. Good luck. Windows will erase your hard drive, format it, and re-partition it also. Might want to make sure you do not have any SSD optimization going on like Overprovisioning or Momentum Cache. I try to leave at least 20 GB of the OS Drive Unallocated. This allows for increasing partition size if needed. FYI: This update is really not worth the effort. It has no effect on performance, and does nothing for a non-bitlocked drive. Might want to just ignore it or bypass it like so many others have done. Perhaps one day Microsoft will fix it, but given the complexity and reduced interest in Win 10 it is not likely.

Who said anything about resizing?

Erm wasn't that you?

i can't even resize the recovery partition there. It wont go past 529 MB

Please post an image of disk management.

hi community

when Microsoift will fix this ongoing issue?

I read your different posts about resizing parts but still failing

so my unique question when Microsoft will issue new patch for this updae since that the only one getting the error message

I assume Microsoft can take bit responsability for their own failure

Anyone can advise?

thank you all

Did this, worked, and now I can eventually jump out of this nightmare.

You go to https://www.microsoft.com/en-us/software-download/windows10

Create Windows 10 installation Media

Download Now

I DID NOT DO A CLEAN INSTALL . I opted to keep my files.

My case is funny. My system (HP laptop) was upgraded from 8.1.

DISKPART> list part 

  Partition ###  Type              Size     Offset 

  -------------  ----------------  -------  ------- 

  Partition 1    Recovery          400 MB   1024 KB 

  Partition 2    System            260 MB   401 MB 

  Partition 3    Reserved          128 MB   661 MB 

  Partition 4    Primary           908 GB   789 MB 

  Partition 5    Recovery          2048 MB  909 GB 

  Partition 6    Primary           20 GB    911 GB  

DISKPART>
DISKPART> list vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD-ROM         0 B  No Media
  Volume 1     C                NTFS   Partition    908 GB  Healthy    Boot
  Volume 2         RECOVERY     NTFS   Partition     20 GB  Healthy
  Volume 3                      NTFS   Partition    400 MB  Healthy    Hidden
  Volume 4                      FAT32  Partition    260 MB  Healthy    System
* Volume 5         WINRE        NTFS   Partition   2048 MB  Healthy    Hidden
DISKPART>

Because recovery partition is located even prior of system the Upgrade created a new one for W10 but somehow failed there.

I found no winre.wim on the partition 5, only the old 8.1 one on partition 1.

I extracted W10 winre.wim from distribution .iso and copied it to recovery\windowsre on partition 5 manually. Below are old and new winre.wim -s to compare.

04.12.2023  03:30       474 223 495 winre.wim 

08.11.2012  12:59       213 949 909 winre.wim.old

I resized partition 5 to 2GB as you can see above. RE is enabled.

Windows RE status:         Enabled

Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: df43008f-078f-11ed-bf0a-e4313577db01
Recovery image location:
Recovery image index:      0
Custom image location:
Custom image index:        0

But the update repeatedly fails. Obvious guess is that to be successfully installed it does need the very first recovery partition 1 to be large enough, not the configured and set as active RE partition 5. And this scenario is something related not only to me but many other users with recovery partitions located prior system/boot one. diskpart can not resize it and creates a new one, which is not getting identified by update process as it tries to use only first one and why it fails.

Worth to mention I found and deleted obsolete recovery boot entry in BCD store, it did not help to solve the update issue.