KB5034441 error 0x80070643

Windows 10 Home supports file encryption but not Bitlocker.

Gotcha, I thought it was basically Bitlocker labeled as File Encryption, maybe stripped of some of it's goodies.  Just looked it up and see what you are saying.  

Susan Bradley (widely regarded as *THE* Windows Update guru) has issued a rare MS-DEFCON Level 1 warning for this patch:

https://www.askwoody.com/

I followed the steps in the below link to remove the downloaded update. Then used the Microsoft tool to hide the update. When I checked settings > update it still showed the error until I said check for updates again. After the check it said everything was up to date and the error was gone thank God.

 

https://www.thewindowsclub.com/delete-downloaded-failed-pending-windows-updates

Update:

 

https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-script-to-update-windows-10-winre-with-bitlocker-fixes/

 

Perhaps a step in the right direction?

 

{What could go wrong?}

While annoying, this is easy to fix. Forget the MS instructions,

Download the free MiniTool Partition Wizard 12.8. Great tool, I've been using it forever.

 

https://www.partitionwizard.com/free-partition-manager.html

 

Then just use the instructions from the inimitable Daisy at MiniTool:

 

https://www.minitool.com/news/kb5034441-fails-to-install-with-code-0x80070643.html

 

Then write Microslob a REALLY nasty letter.

Edited by Quantumleap, 12 January 2024 - 01:18 PM.

[snipped]

The only problem is that on a clean install the Windows RE is at the front of the OS partition, at least it is on my one Windows 10 computer. Edit: In

fact, my Windows RE partition is at the front of the EFI partition.

[/snipped]

Sort of. Up to 1909, the recovery partition was at the beginning of the disk, if you just installed with the default partition layout.

In 2004, the recovery partition was moved to the end of the disk, although it still defaulted to about 500 MB.

 

But Microsoft says in OEM docs, "We recommend that you place this partition immediately after the Windows partition. This allows Windows to modify and recreate the partition later if future updates require a larger recovery image."

 

And, "If manufacturer's [sic] want to use a custom DISKPART script to create partitions, the recommended minimum partition size is 990MB with a minimum of 250MB of free space."

 

Indeed, the docs for Windows 8/8.1 say,

 

"The size of this partition must include space for the Windows recovery image (at least 2 GB), plus enough free space so that the partition can be captured by backup utilities:

• It must have at least 320 MB of free space.

• We recommend that it should have at least 1 GB free.

We recommend that you place this partition after all other partitions. [emphasis is mine]"

 

So while they didn't default to the correct layout order until Windows 10 2004, they've been saying create larger RE partitions for a long time. The RE partition is still too small in the default layout though.

Edited by pseymour, 12 January 2024 - 07:50 AM.

Thanks p, that was interesting!

Thanks for that info.

 

I wonder if you downloaded the latest iso with the MCT it would create the correct RE partition size during the install?

I installed 22H2 this morning, using the latest MS ISO, and the partition was in the correct spot, but still about 500 MB.

Hopefully Microsoft changes that soon.

I installed 22H2 this morning, using the latest MS ISO, and the partition was in the correct spot, but still about 500 MB.

I did a clean install using the MS online tool a couple of years ago. The RE partition is at the end of the list after the Windows partition but is, as has been said, about 500MB.

 

However it does seem MS have now pulled the troublesome KB 5034441which Home users don't actually need.

some folks are worried about Defender not updating but mine update fine today according to the logs.

@aldfort:

Good news that MS has pulled KB5034441, at least for us mere-mortal home users.
For my own edification, do you have a link about that?

Thanks!


(I've been holding off patching both my OEM Win11 PRO boxes. I always wait several days after Black Tuesday. This time, I'm really glad I did. Data backups notwithstanding, I'm not excited about the MS PS script. "What could go wrong???")

@aldfort:

Good news that MS has pulled KB5034441, at least for us mere-mortal home users.
For my own edification, do you have a link about that?

Thanks!


(I've been holding off patching both my OEM Win11 PRO boxes. I always wait several days after Black Tuesday. This time, I'm really glad I did. Data backups notwithstanding, I'm not excited about the MS PS script. "What could go wrong???")

As said in other post there is no KB5034441 in the MS update catalog. I don't know how else to check MS pulled it.

@aldfort

Thanks!

Hmmm You're likely correct.

But the plot thickens a bit?
I wonder if it has (yet) been officially pulled?

MS clearly acknowledges the problem and promises a real fix (not a just-in-time DIY PS script) with a future update:
https://support.microsoft.com/en-gb/topic/kb5034441-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024-62c04204-aaa5-4fee-a02a-2fdea17075a8

And you are indeed correct: it is not available in the WU catalog for Win11 when I checked just now. (Good tip!)

But, curiously, according to Susan Bradley, KB5034441 is " for some unknown reason " not available either through WSUS or the WU Catalog:
https://www.askwoody.com/forums/topic/kb5034441-not-installing/#post-2623089
Of all people, she would know the official scoop.

>>> So, perhaps, it has indeed been pulled?

Another Black Tuesday for MS. I haven't had any serious issues with Windows Updates with either Win11 box thus far until now. This dredges up traumatic memories of the bad old days with XP, Vista & 7.

((WinRE is enabled on both of my systems & the default Recovery partitions are too small. But the Bitlocker bypass vulnerability does not apply. So, I'm going to wait this out a bit longer before jumping hoops to risk bricking my computers. Sigh.))

This is a very good method for fixing the issue if the WinRE is after the System Partition. Unfortunately, my WinRE is at the beginning of the disk, before the EFI and System Partitions. I could shrink the System partition, move the EFI and MSR partitions, then expand the WinRE partition using a partition manager but I don't use Bitlocker. I'm not going to take the chance something gets borked so I just hid the update.

 

Edit: The post I was responding was deleted.

Edited by JohnC_21, 13 January 2024 - 03:29 PM.