2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441) error (0x80070643) a known issue?

Anonymous
2024-01-09T21:04:12+00:00

I keep trying install this update yet it keeps failing. I already ran troubleshooter said it resolved the issue but the error persists. I also disabled my antivirus and tried again still did not work And I keep getting error (0x80070643) Is this a known issue? All the other updates installed fine without issue.

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

163 answers

Sort by: Oldest
  1. Anonymous
    2024-01-10T15:18:08+00:00

    This worked for me if you are not comfortable with using cmd diskpart . ghacks and i recommend that you create a system backup before you make any changes to the system. Microsoft's workaround requires deleting and resizing partitions.

    https://www.ghacks.net/2024/01/10/fix-0x80070643-error-install-failure-when-trying-to-install-windows-update/

    Thank you ghacks.

    First, check if WinRE is available:

    1. Open Start, type CMD, and select "run as administrator" to launch an elevated command prompt window.
    2. Run the command reagentc /info. If you see path information, WinRE is enabled. Note the number behind harddisk and partition in the path, these are needed later on.
    3. Run reagentc /disable to disable WinRE for the operation.

    Now shrink the OS partition to create a new recovery partition:

    1. Run diskpart.
    2. Run list disk to get a list of all hard disks connected to the computer.
    3. To select the operating system disk, run the command sel disk <OS disk index>. Replace >OS disk index" with the harddisk value.
    4. List all partitions by running list part. Check for the primary partition there. It is usually the largest.
    5. Select the (primary) operating system partition with the command sel part <OS partition index>.
    6. Run shrink desired=250 minimum=250. This shrinks the operating system partition by 250 MB.
    7. Run sel part <WinRE partition index> to select the recovery partition. Use the partition number that you got when you ran the first command at the top.
    8. Delete the partition by running delete partition override.
    9. Type list disk again and check if there is an asterisk character (*) in the GPT column of the drive.
      1. If the disk with Windows on it is GPT, run the following commands:
        1. create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
        2. gpt attributes =0x8000000000000001
      2. If the disk is MBR, run the following command:
        1. create partition primary id=27
    10. To format the partition, run the command format quick fs=ntfs label=”Windows RE tools”.
    11. Run the command list vol to verify that the Recovery Partition is available again.
    12. Type exit to exit diskpart.
    13. Run reagentc /enable to enable the recovery environment again.
    14. Make sure that this is the case by running reagentc /info.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  2. 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

  3. Anonymous
    2024-01-10T15:28:08+00:00

    Same problem here on a Surface Pro 7... Please fix!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-01-10T15:54:27+00:00

    Same problem, win10 here, disk partition 1gb/1gb. Of all the solutions I have seen so far, it requires a little more knowledge on Windows and making a backup of my disk because I could damage my entire system if I f*** up ..... and nope.... I am not willing to do that at the moment. The question is for Windows if they are going to make a fix for this because on my system I tried everything possible (troubleshooting, restart, disable all the applications from the start up, etc. ), but nothing works. And I'm not going to modify everything by CMD risking all the system!! I'm sorry.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-01-10T15:58:22+00:00

    Shrink with 250MB is to little. My old was 400Mb and it was not enough. :( I did my with 2G and it works nice.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments