Comments on: Microsoft Patches BitLocker Bypass Vulnerability With KB5034441 For Windows 10; Fails To Install With Error Code 0x80070643

By: Usman Khurshid

Usman Khurshid — Thu, 23 May 2024 11:08:42 +0000

In reply to Anonymous. It seems like the arguments you gave are not valid. Please try this. First, create a primary partition. and then set its id to 27.

create partition primary size=

set id=27 I hope this will resolve your issue.

By: Anonymous

Anonymous — Wed, 22 May 2024 23:15:45 +0000

I have followed all the steps but when I try to run the following command: “create partition primary id=27”.
I get this error: “The arguments specified for this command are not valid.
For more information about the command, type: HELP CREATE PARTITION PRIMARY”.
Any solution pls.

By: Anonymous

Anonymous — Thu, 07 Mar 2024 09:29:27 +0000

Hi
I have followed all the instructions and everything was perfect until I tried to install the update and it still gave me an error. I try again and this time I increase the size of the recovery partition to 1.26 GB and it still gives me an error when trying to install the update. I tried it for the third time and this time I increased the partition to 2.24 GB and it still gives me an error when installing the update. Any ideas? Thx

By: Subhan Zafar

Subhan Zafar — Tue, 20 Feb 2024 10:10:03 +0000

In reply to Ever.

Hi,
I I understand correctly, you have created a new Windows Recovery Environment on the wrong partition. In steps 7 through 10 above, we selected the disk and the volume that corresponded with the information we got from the “reagentc /info” command.
It seems like you selected the wrong partition and performed the steps remaining steps on it.
If this is true, then your system will currently have 2 Recovery Environments on it. Additionally, you may have accidentally overridden your data.
I suggest that you restore your PC to an earlier state and undo the changes. If your PC does not have a system store point, then you can delete the Recovery Environment you just created and try recovering the lost data using third-party tools. After that, you may perform the steps above again, and this time, correctly select the same partition as the Recovery Environment.

By: Ever

Ever — Mon, 19 Feb 2024 22:53:39 +0000

I have followed the instructions but now I have a drive D: drive with WinRE tools and the RE is pointing to another drive before:

C:\Windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

After:
C:\Windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE

Now, the Restore is allowed on C: (Partition3) instead of Partition4 …

Please let me know.. what I’ve done wrong…

By: Subhan Zafar

Subhan Zafar — Mon, 12 Feb 2024 08:49:38 +0000

In reply to George.

Hello,
After researching the internet, it appears that this issue has occurred with several users. It seems that the issue only occurs on relatively older laptops, especially Lenovos. One of the possible solutions for this issue is trying to update your firmware. Please check whether a BIOS update is available for your PC, and install it if it is. Since you can’t boot into the PC, I recommend downloading it from another computer and using the manufacturer-provided instructions to install it.
If that doesn’t work, you can uninstall the troublesome update directly from the Windows Recovery Environment. The following article gives a step-by-step guide on how to uninstall a Windows Update:
https://itechtics.com/uninstall-windows-11-update/

By: George

George — Wed, 07 Feb 2024 14:40:21 +0000

Does anyone know of any reports KB5034441 causing their computer from booting? After this failed update, my ASUS computer no longer boots!

By: Anonymous

Anonymous — Fri, 12 Jan 2024 09:55:27 +0000

Resizing the partition to 1GB does not fix the issue, even after a reinstal, the issue is still present.
Buggy update that needs to be fixed, once more, Micostoft hits the bas strike

By: Subhan Zafar

Subhan Zafar — Fri, 12 Jan 2024 05:24:52 +0000

In reply to Anonymous.

Hi,
You are absolutely right – the update has in fact been pulled from WSUS. However, I would like to add that the KB article has also been removed from the Microsoft Update Catalog. Now, KB5034441 is only available through Windows Update.
Seems like Microsoft is regretting rolling out a critical security update.

By: Anonymous

Anonymous — Thu, 11 Jan 2024 17:42:45 +0000

it looks like KB5034441 has been pulled from the WSUS channel. The KB lists the update as available only from WU and MU – and no longer from WSUS. Yesterday when I was looking in WSUS, the KB was not present in WSUS – and today the KB article has been updated to say “No” for WSUS channel