KB5034441 update problem, error (0x80070643).

Anonymous
2024-01-10T15:18:19+00:00

I have tried to update and I get error 0x80070643 with update KB5034441. I have tried uninstalling the Windows update, restarting the Windows Uptade service, deleting the update files and I have also run the following commands:

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

DISM /Online /cleanup-image /startcomponentcleanup

sfc /scannow

chkdsk C: /f

But nothing has fixed the problem

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
Answer accepted by question author
Anonymous
2024-01-11T18:16:15+00:00

The update KB5034441 failed with a fatal error when staging the WIM. This is due to a lack of free space in the WinRE partition. KB5034441: Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: January 9, 2024 - Microsoft Support

Resizing the Recovery partition to 750 MB resolves the issue. That applies if you use the Windows-default winre.wim.

For OEM-supplied winre.wim (which has additional drivers and packages), ensure the Recovery partition's size is atleast 100 MB more than the size of the custom wim.

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

 

Note: The above MS article works only if your Recovery partition is situated next to (i.e., right side) the OS partition. You can check the disk layout by opening Disk Management.

 

(Based on what I've noticed on the forums, many users have decided to skip/hide the KB5034441 update and wait and see if Microsoft releases a fix.)

After command SFC /scannow
& resize of WinRE to 1GB, managed to get this update working. 👍

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

86 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-01-30T11:33:31+00:00

    New Preview came out on 23rd Jan 2024 (https://support.microsoft.com/en-us/topic/january-23-2024-kb5034203-os-build-19045-3996-preview-d9540687-af96-46ba-9192-88fe44833561) which shows as one of its fixes:

    This update addresses a known issue that affects BitLocker data-only encryption. A mobile device management (MDM) service, such as Microsoft Intune, might not get the right data. This occurs when you use the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node.

    Can anyone confirm if this is actually the problem we are all going through?

    We have installed it on an affected machine to test, where the update took close to 30 minutes, and when the machine became available, went into Windows Update and the Retry button was still showing for the old problemed kb5034441. Would have imagined that this would have disappeared?

    Has anyone else tried this? Is anyone else experiencing the same behaviour?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-01-24T09:26:29+00:00

    Changing my partitions, because Micro$oft can't get an update sorted within a reasonable size restriction? Are you serious?! It seems resizing the partition does not solve the problem either.

    Mirco$oft:

    Get.

    It.

    Fixed.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-20T19:31:27+00:00

    Was speaking in general not specially you. Just all the YT fixes which many of us can do. When it comes to partitions most of us (90%) users are not even going to attempt this procedure. Just people that user their PC for search, downloads and everyday type of things. Not messing with the programs/files that could cause more problems with a mistake. If MS can make this type of mistake then many PC users will make even more. What you have pointed out will work for 10% of users. The rest of us can't comprehend all of that or putting in 20 lines of instructions. We want MS to fix this problem they put on our PC's . 10+ days later there are no automatic updates to rid PC of this error. Many are stopping updates totally because of it and miss the 3-4 updates that come each day for Defender Antivirus.

    You have done well for PC users that are technically sound working into Windows programs and files. The rest of us will wait to see if MS will fix.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-01-20T14:23:59+00:00

    DO NOT CALL ME A "HOT SHOT".

    I told you of an omission in the Microsoft instructions. The act of formatting the newly created recovery partition - per Microsoft's instructions - changes the partition type from recovery to primary. After the format command, you need to do an additional command, "set id=27", to restore the partition type to recovery.

    I documented this in the post.

    This is why some people using the Microsoft instruction are still having problems. If you don't want to use Microsoft's work-around, fine, then don't. But do not insult people who are trying to share what they have found to work.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments