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
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

86 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-01-24T00:55:18+00:00

    What you are describing is one physical drive with 5 partitions, yes?

    If so, it sounds like your recovery partition is 1st, and your OS partition is the the 3rd (the boot drive). You would need to move your recovery partition from it's 1st spot and situate it immediately to the right of your boot partition (in addition to resizing it so that it's larger than 750 MB). It can be done pretty easily with third-party tools like the MiniTool Partition Wizard, and with much more difficulty without.

    Was this answer helpful?

    0 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
  3. Anonymous
    2024-01-24T15:18:59+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?

    0 comments
  4. 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