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

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

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.

Hi Elise!

Your link is right one but that advise there is wrong. On my notebook (win10) with c: d: was 1 "winre" efter 2 patch try I got 3 st "win re" part , they had size about 400M, it's to little. So I used diskpart (if you need shrink do it with at least 2G), delete 3 old "win re" and create 1 win re = 2G size. and after that , patch update did work. Some people said that 1G is OK but I dont want to do the same work in the future.

The same work i did on my win2022 server ... with the size of 2G (win re) everything was OK after that job.

/Best Vlad

This MS-BS occurs because probably you've chosen to decline micro-soft offer to use their cloud for backup your private stuff. In response they require a huge recovery partition so one will be persuaded to give up his private data to big bro. You know what? I'm used to XP and 7 when I've been resolving stuff through the back door and ignoring all their BS including "recommended" updates to protect me from bogey man. Obviously who the bogey man is ... If someone is eager to mess up his system partition and loose three hours to back up his machine I wish him luck and condoleances. I am returning to roots here. Old bad habits. Cheers.