Windows 10 22h2 security update [KB5034441] fails to install with code: 0x80070643

Anonymous
2024-01-09T19:42:37+00:00

* * Mod note on 1/12/24. * *

Please see: https://www.yourwindowsguide.com/2024/01/fix-error-0x80070643-for-windows-10-kb5034441-update.html 


The latest update downloads and then fails to install.

  • OS Build # 19045.3930.
  • Update Troubleshoot tool repair but it does not help.
  • MS Windows Update Catalog does not have the update.
  • Other updates all went through without any trouble.

This is a brand new update. Is this a known issue? Is there a resolution specific to this update? (Please do not copy and paste standard procedure)

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

194 answers

Sort by: Most helpful
  1. Anonymous
    2024-01-11T03:23:54+00:00

    Don't worry this is easily solvable. Just follow the instructions and the update will install.

    ...

    Just take your time and follow the instructions step by step. Copy paste is recommended to avoid typos.

    Oh sure... it's easily solvable on a singe computer. When you have ~6,000 domain-joined workstations that are exhibiting the same problem, it becomes a little less easily solvable.

    I understand your frustration with Microsoft. How about leveraging the weight those 6000 licenses brings with Microsoft instead of at individuals who are just trying to help each other.

    Share mitigation tips with other corporate users with many licenses.

    FWIW I vote for a working automated fix from MS too.

    I have personally seen MS take a lot of flak for sitting on security fixes for much too long. That's no excuse for shipping this poorly tested update though.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-01-11T02:10:30+00:00

    You are having a similar issue as me. One of my boot partitions (EFI stuff) is out of order causing lots of headaches.

    In your case I think the only way to solve it is to follow the guide and make sure you activate your new partion as Recovery.

    From the guide:

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

    this command tells windows that this is the new Recovery partition.

    gpt attributes =0x8000000000000001

    this command removes the drive letter recquirement so it doesnt show up in Disk manager for no reason.

    The old Recovery partion you can delete override as per the guide. You will have that old Recovery space now sitting as unallocated.

    Your layout will be thus:

    1. Reserved (128MB) unallocated (529MB)
    2. EFI (100MB)
    3. OS (475GB)
    4. Recovery (1125MB) *after resizing it

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-01-11T01:45:29+00:00

    this does not help microsoft screwed up the update needs to be pulled https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5034441-security-update-fails-with-0x80070643-errors/ here's the error they made the recover portion is to small

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-01-11T01:45:08+00:00

    Older version of Win10 installed the Recovery partition first. Newer versions install it last, which is preferable.

    Partition 1 - System - The EFI System partition that contains the NTLDR, HAL, Boot.txt, and other files that are needed to boot the system, such as drivers.
    Partition 2 - MSR - The Microsoft Reserved (MSR) partition that reserves space on each disk drive for subsequent use by operating system software.
    Partition 3 - Primary - Where Windows is to be installed to.
    Partition 4 - Recovery -

    Windows 10 version 2004 and higher

    , the "Recovery Partition" partition will be created at the final stages of Windows Setup.

    Windows 10 version 1909 and lower

    , the "Recovery Partition" partition will be created as partition 1 instead.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-01-11T01:18:24+00:00

    To be honest I'm just gonna wait till microsoft fixes it themselves. I ain't in a rush since I don't use bitlocker, but if you have read my post before this one you would know i'm kinda pissed off at microsoft. So it might work for other but right now i'm just gonna sit tight until microsoft fixes it themselves.

    Was this answer helpful?

    0 comments No comments