"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in 64-bit W10 Pro.

Anonymous
2024-01-09T18:58:13+00:00
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

119 answers

Sort by: Newest
  1. Anonymous
    2024-01-11T22:06:39+00:00

    I had this problem on 3 PC's and so far I've fixed 2 by following the procedure in KB5028997. However I resized the WinRE partition to ~950MB from 563MB as after increasing it by 250MB it still failed. Also 1 PC had a partition style of GPT and the procedure worked perfectly, however 2 others have MBR style and this gave rise to another problem.

    After re-enabling WinRE with the new partition created it seems to be pointing to the wrong partition i.e. I now have reagentc /info returning:

    Windows RE status: Enabled

    Windows RE location: \?\GLOBALROOT\device\harddisk1*partition2\Recovery\WindowsRE*

    Boot Configuration Data (BCD) identifier: 503ab989-affc-11ee-b443-50e549b23526

    Whereas before it was \?\GLOBALROOT\device\harddisk1*partition3\Recovery\WindowsRE*

    and partition 3 is where LIST PART displays the "Windows RE tools".

    I've now found the solution to this. It seems that the command

    create partition primary id=27

    doesn't assign id 27 although it does create the partition and name it. I found the id was 7. So there are 2 commands to help with this:

    detail part - shows the currently selected partition details e.g. 7 instead of 27

    set id=27 - this works!

    detail part - should show correct id

    After re-enabling reagentc I got the correct partition assigned!

    So in my experience the KB5028997 procedure solves the KB5034441 installation failure in Windows 10 provided the above 2 amendments are included. The only scenario not covered is where there is another partition between the OS and WinRE ones.

    Hopefully MS are working on a proper fix for this as having a major Windows security flaw permitting Bitlocker encrypted file access renders it useless. On the other hand anyone caught by a ransomware attack has a solution to recover their system without paying the hackers!!! :p

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-01-11T04:17:50+00:00

    I fix this problem with MiniTool Partition Wizard, extend recovery partition from 512 to 809

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-10T20:22:31+00:00

    Well, the manual partition reshuffling detailed on the KB article would work, if I wouldn't have the UEFI partition *between* the Windows and the Recovery partition. Just gonna ignore it for now, too late and tired to mess around with partitions at home too (had to fix at work already).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-01-10T19:18:07+00:00

    Same error code here (0x80070643). Windows 10 Home 64 bit in a up-to-date healthy machine that is qualified for Windows 11 installation. Tried multiple workarounds with no success, then proceeded to a full Windows 10 restore that led to no success in finishing the installation of this update.

    2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)

    This (0x80070643) error happens everytime i try to install this update. And only this update.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-01-10T19:05:58+00:00

    Having the same problem! Everything else updated just fine and no way am I tampering with the partition settings! I do not see millions of amateurs do it either! Microsoft dropped the ball on this one!

    I'm just going to wait for the Microsoft programmers in the windowless basement fed on Mountain Dew and cigarettes to get around to recalling this update or offering a fix.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments