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

Thanks so much for sharing this info. Based on what I've read the entire security update is focused on patching a security flaw in Bitlocker. Since I don't use Bitlocker, I don't think its worth the trouble (and the risk) of increasing the WRE partition size. So, I'm just going to ignore the update error (not the first time) and wait for Microsoft to push out an update that actually works on all machines. Especially since they are the ones that created the issue with the partition size.

Create a new Recovery partition as per the instructions step 5. Create a new recovery partition. First, check if the disk partition style is a GUID Partition Table (GPT) or a Master Boot Record (MBR). To do that, run list disk. Check if there is an asterisk character (*) in the “Gpt” column. If there is an asterisk character (*), then the drive is GPT. Otherwise, the drive is MBR. If your disk is GPT, run create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the command gpt attributes =0x8000000000000001 If your disk is MBR, run create partition primary id=27 To format the partition, run format quick fs=ntfs label=”Windows RE tools” To confirm that the WinRE partition is created, run list vol To exit from diskpart, run exit To re-enable WinRE, run reagentc /enable To confirm where WinRE is installed, run reagentc /info Just so you know - this will generally fail as written if you're using MBR (and I suspect GPT as well) The issue is - the steps for MBR are slightly out of order. When you run create partition primary id=27 , then do the format quick fs=ntfs label=”Windows RE tools” step, your partition will be reset to NTFS id of 07. Your reagentc.exe won't be able to find your new recovery partition. At least it didn't on my computer. I recommend resetting the primary id back to 27 with a step 1.5: set id=27 Then - you should be good to go. You can verify that the recovery partition is set correctly by using Window's Disk Management tool.

Unfortuntely, still same message ! I'll wait the Microsoft Fix !

Wont install on all of my 4 pcs.

@Chililock wrote: the only way to enter recovery is from Media Creation Tool USB. Not true. More than 2 consecutive restarts, or a Windows crash quickly after restarting should start into the Recovery Console. Should I try using System Restore and restore to a system point on Jan 7th, prior to the updates? That is an excellent idea. After, if the update fails, it fails, but your system should still restart normally. A general note : before Microsoft released this security update, your computer was vulnerable to an exploit of the security issue. It still is vulnerable, but has that created an issue that now causes you sleepless nights? If there is exploit code "in the wild", and given the wave of publicity about this update, do you hope that your anti-virus software supplier will have updated their software to block that exploit from running on your computer? Does that hope let you sleep soundly?

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

Anonymous

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

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

194 answers

Anonymous

2024-01-11T22:36:14+00:00

Thanks so much for sharing this info. Based on what I've read the entire security update is focused on patching a security flaw in Bitlocker. Since I don't use Bitlocker, I don't think its worth the trouble (and the risk) of increasing the WRE partition size. So, I'm just going to ignore the update error (not the first time) and wait for Microsoft to push out an update that actually works on all machines. Especially since they are the ones that created the issue with the partition size.
Was this answer helpful?

0 comments No comments
Anonymous

2024-01-11T22:35:28+00:00
Create a new Recovery partition as per the instructions step 5.

Create a new recovery partition.

First, check if the disk partition style is a GUID Partition Table (GPT) or a Master Boot Record (MBR). To do that, run list disk. Check if there is an asterisk character (*) in the “Gpt” column. If there is an asterisk character (*), then the drive is GPT. Otherwise, the drive is MBR.

If your disk is GPT, run create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the command gpt attributes =0x8000000000000001

If your disk is MBR, run create partition primary id=27

To format the partition, run format quick fs=ntfs label=”Windows RE tools”

To confirm that the WinRE partition is created, run list vol

To exit from diskpart, run exit

To re-enable WinRE, run reagentc /enable

To confirm where WinRE is installed, run reagentc /info
Just so you know - this will generally fail as written if you're using MBR (and I suspect GPT as well)

The issue is - the steps for MBR are slightly out of order.

When you run create partition primary id=27, then do the format quick fs=ntfs label=”Windows RE tools” step, your partition will be reset to NTFS id of 07. Your reagentc.exe won't be able to find your new recovery partition. At least it didn't on my computer.

I recommend resetting the primary id back to 27 with a step 1.5: set id=27

Then - you should be good to go. You can verify that the recovery partition is set correctly by using Window's Disk Management tool.
Was this answer helpful?

0 comments No comments
Anonymous

2024-01-11T21:50:04+00:00

Unfortuntely, still same message ! I'll wait the Microsoft Fix !
Was this answer helpful?

0 comments No comments
Anonymous

2024-01-11T21:42:36+00:00

Wont install on all of my 4 pcs.
Was this answer helpful?

0 comments No comments
Anonymous

2024-01-11T21:22:09+00:00

@Chililock wrote: the only way to enter recovery is from Media Creation Tool USB.

Not true. More than 2 consecutive restarts, or a Windows crash quickly after restarting should start into the Recovery Console.

Should I try using System Restore and restore to a system point on Jan 7th, prior to the updates?

That is an excellent idea. After, if the update fails, it fails, but your system should still restart normally.

A general note: before Microsoft released this security update, your computer was vulnerable to an exploit of the security issue. It still is vulnerable, but has that created an issue that now causes you sleepless nights?

If there is exploit code "in the wild", and given the wave of publicity about this update, do you hope that your anti-virus software supplier will have updated their software to block that exploit from running on your computer? Does that hope let you sleep soundly?
Was this answer helpful?

0 comments No comments