KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 Win Update

@Pentagon

I found your solution very concise, however...

With my first try I wound up with 2 Recovery partitions of 518mb.
had to go back and run diskpart
sel par 3
delete partition override
sel par 4
delete partition override

Also my partition type is MBR not GPT but found the correct diskpart commands to substitute.

In the end we were successful and I was able to install that pesky KB.
Thank you.
Al

einstein1969 said:

We finally won!

Code:

C:\WINDOWS\system32>Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\winre.wim /index:1

Strumento Gestione e manutenzione immagini distribuzione
Versione: 10.0.19041.3636

Dettagli per l'immagine: \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\winre.wim

Indice: 1
Nome: Microsoft Windows Recovery Environment (x64)
Descrizione: Microsoft Windows Recovery Environment (x64)
Dimensioni: 2.304.888.863 byte
WIM avviabile: No
Architettura: x64
HAL: <non definite>
Versione: 10.0.19041
Build Service Pack: 3920
Livello Service Pack: 0
Edizione: WindowsPE
Installazione: WindowsPE
Tipo prodotto: WinNT
Famiglia di prodotti:
Radice sistema: WINDOWS
Directory: 3694
File: 16738
Data creazione: 07/12/2019 - 14:58:12
Data modifica: 24/01/2024 - 20:52:44
Lingue:
        it-IT (valore predefinito)
Operazione completata.

C:\WINDOWS\system32>dir e:Recovery\WindowsRE\ /a
 Il volume nell'unità E non ha etichetta.
 Numero di serie del volume: BED7-2BC8

 Directory di E:\Recovery\WindowsRE

24/01/2024  20:52    <DIR>          .
24/01/2024  20:52    <DIR>          ..
07/12/2019  10:08         3.170.304 boot.sdi
22/01/2024  19:39             1.110 ReAgent.xml
24/01/2024  20:52       483.434.149 winre.wim
               3 File    486.605.563 byte
               2 Directory   1.211.678.720 byte disponibili

I had already uninstalled the update, I changed the key, restarted and update.

Another restart and the key has been updated and all right.

I have to thank you to all of you for the patience you have had.

@Pentagon

I found your solution very concise, however...

With my first try I wound up with 2 Recovery partitions of 518mb.
had to go back and run diskpart and run both

sel par 4
delete partition override

sel par 3
delete partition override

Also my partition type is MBR not GPT but found the correct diskpart commands to substitute.

In the end we were successful and I was able to install that pesky KB.
Thank you.
Al

Pentagon said:

@Emer

step by step copy & paste
watch the system response after each step

reagentc /disable
diskpart
sel disk 0
sel part 5
delete partition override
create partition primary
format quick fs=ntfs label="Recovery"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes =0x8000000000000001
exit
reagentc /enable
You are ready
reagentc /info

Run your Windows Update again
run
reagentc /boottore
and start a normal reboot to check the new Recovery Environment

I performed Windows Update again yesterday, and everything seems to be good.



However, when I checked disk management, the recovery partition was empty (100% free space).



My question is: where was KB5034441 installed? And why does partition 1 (450MB) have 96% free space? What is 4%?

Thank you very much for your help

@Emer
I bet that it is installed in partition 5
To find out if it was successful:
1. run PowerShell> Get-Hotfix
2. cmd> Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\winre.wim /index:1
should be Build Service Pack: 3920 (see post # 531)
3. cmd> reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /t REG_SZ /v WinREVersion
you get this: WinREVersion REG_SZ 10.0.19041.3920
4. Partition 1 is now a "Standard" Partition without any drive letter. It has Windows stuff:hidden $Recycle.bin and a System Volume Information folder. It's not useful, but it's better to keep it than to delete it. When you run Backup&Recovery the next time you can ignore/delete it without any risk.

Hello all!

I have the same error, can not install KB5034441 on my laptop. And here my disk management:



Which partition should be expanded, and how? Thankyou!

gibran said:

Hello all!

I have the same error, can not install KB5034441 on my laptop. And here my disk management:

Which partition should be expanded, and how? Thankyou!

The KB5034441 is definitely not your problem!
3xRecovery and 2x EFI!
4% free on (C:)!
disable fast boot in Windows
run cmd> POWERCFG /H OFF
delete all restore points

Well I ran the fix from How to fix Windows 10 KB5034441 failing to install with 0x80070643 error - It SEEMED to work.

But... it DOWNLOADS the update, but I still get 0x80070643 when trying to install it. So all I need to do is make the WinRE partition bigger? I'm loathe to alter my system partition because my W10 has it's boot partition on my D drive. I havent been able to move the installation to a new drive because of that, Migration thinks my system drive is 4 TB when it is only 500G.

@XweAponX
You did not provide a single information that can be used to give you an instruction!
In this thread you find many useful examples for that.

Pentagon said:

@XweAponX
You did not provide a single information that can be used to give you an instruction!
In this thread you find many useful examples for that.

Yes, I know. I didn’t need to. I had already run that fix and it did not work, so, after reading through this entire thread, I saw that a possible solution would be to increase my winRE partition size to 1gb.

Which is what I just did, I was kind of worried about doing that. With my boot partition not actually residing on my system Drive, it causes a lot of problems that I just don’t want to get into here.

I have a Lenovo Thinkcentre M92p, it ran fairly well originally until I got hit with ransomware. This forced me to reinstall windows, but I neglected to remove my 4 TB storage drive, so, obviously, my windows installation spans two Drives where it should actually be only on one. And I have found a couple of fixes for this, but they require complicated command lines, I can do it, but the instructions that I found were totally unclear.

So I’m not really worried about this issue here. I was worried, mostly about resizing my partition. Which I did, it’s 998 MB now.

If I keep having problems with installing, I will give a lot more information, certainly. But I can’t provide any images or screenshots from my computer because I’m working on it right now and I’m using my phone to post in here. apologies.

I am trying to install, once again, the update downloaded. Which it was not doing originally, but what happens now is that it sits at 0% installing and then, after about 10 minutes, it fails and gives me the same error that I listed above.

If it succeeds this time, I will edit this post, but I don’t think it will. This is a totally recreated recovery partition. Yep, it’s failed to install, so I’ll have to come back here later and find out from you guys why it would not be installing even though I have plenty of space.

Do you concur that my recovery partition is probably corrupted and I should run the fix again? Because I can do that no problem but I’ve got other things to do today. I’m not worried about this update yet.


EDIT! EDIT! EDIT! EDIT!

Whaaa? YAY! It went in The second time I tried to run it




So thanks… you don’t need to make the partition 2 GB, 998 MB should be fine. As long as you had run the fix that recreates a corrupted recovery partition, it should work

I will make a post somewhere about my inability to migrate my system. Drive to my solid-state drive, I’ve tried about four different migration, software packages.

It’ll be after the first though.