Regarding KB5034441 with 0x80070643 Error

YES: reagentc /boottore
Just normal reboot and you are there.
When the PC doesn't boot 3 times it automatically launches the Recovery Environment.

Cool.
Thank you.


From this article:
7 Ways to Boot Into the Windows Recovery Environment
it seems that the Shortcut Key during BIOS changes between manufacturers.


You would expext there would be some Shortcut Key that is not affected by BIOS,
that can be pressed right before Windows is about to start booting,
the same way we have F8, to enter Safe Mode.
(in this point in time, the pressed key goes to windows, not to the BIOS,
and so it can be the same key for everyone, no matter what your PC manufacturer is)

Hi Folks

I have a similar problem except I have 2 Recovery partitions:



What do I do? Delete both partitions and create a new one?

Cheers
Aztrix

@aztrix
You only have to know how to run "Command Prompt" as Administrator.
when you see this:
C:\WINDOWS\system32>
you are on the right way.

Then copy the following commands and paste into command prompt:
step by step
reagentc /disable
diskpart
sel disk 1
sel par 5
delete partition override
sel par 4
extend
shrink minimum=1024
create partition primary
format quick fs=ntfs label="Recovery"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
exit
reagentc /enable

Run Windows Update and enjoy!

to disable the 1st Recovery Partition just this:
diskpart
sel disk 1
sel par 1
gpt attributes=0x8000000000000000
exit

Pentagon said:

@aztrix
You only have to know how to run "Command Prompt" as Administrator.
when you see this:
C:\WINDOWS\system32>
you are on the right way.

Then copy the following commands and paste into command prompt:
step by step
reagentc /disable
diskpart
sel disk 1
sel par 5
delete partition override
sel par 4
extend
shrink minimum=1024
create partition primary
format quick fs=ntfs label="Recovery"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
exit
reagentc /enable

Run Windows Update and enjoy!

to disable the 1st Recovery Partition just this:
diskpart
sel disk 1
sel par 1
gpt attributes=0x8000000000000000
exit

OK, so what would the steps be with this Disk Management arrangement?:

Copy the following commands and paste into command prompt:
step by step
reagentc /disable
diskpart
sel disk 0
sel par 1
set id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
gpt attributes=0x8000000000000000
sel par 4
shrink minimum=1024
create partition primary
format quick fs=ntfs label="Recovery"
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes=0x8000000000000001
exit
reagentc /enable

Pentagon said:

Copy the following commands and paste into command prompt:
step by step
reagentc /disable
diskpart
sel disk 0
sel par 1
set id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
gpt attributes=0x8000000000000000
sel par 4
shrink minimum=1024
create partition primary
format quick fs=ntfs label="Recovery"
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes=0x8000000000000001
exit
reagentc /enable

Hey Pentagon, thanks for the reply. I didn't see your message until today. Hopefully I'll get a chance to try this this weekend.
Crossing my fingers that it works.
If it does, I'll take a screen shot of my other Disk Management on my other Windows 10 PC and post that here for your advice.

Thanks again,
Steve.

I have the same issue with the update. I also have two recovery partitions. So, I looked into the recovery partition size as the cause. Turns out that Disc Manager and MiniTool show different setups and drive status.

For one, MiniTool shows an "Other" partition that that is missing from Disc Manager. MiniTool also shows that the two recovery partitions have significant used space where Disc Manager says that they are empty.




My questions are:

1. Can I trust MiniTool's assessment?
2. Can I safely delete either of the recovery partitions with MiniTool?
3. What is the "Other" partition and can I move or delete it?

FTNR21 said:

I have the same issue with the update. I also have two recovery partitions. So, I looked into the recovery partition size as the cause. Turns out that Disc Manager and MiniTool show different setups and drive status.

For one, MiniTool shows an "Other" partition that that is missing from Disc Manager. MiniTool also shows that the two recovery partitions have significant used space where Disc Manager says that they are empty.




My questions are:

1. Can I trust MiniTool's assessment?
2. Can I safely delete either of the recovery partitions with MiniTool?
3. What is the "Other" partition and can I move or delete it?

The "Other" partition is technically called "MSR" (Microsoft System Reserved) and it's not shown by Windows Disk Management by design. A characteristic of it is that It either doesn't have format or has a non-standard format (it's one of the two, but Idk which one). Sometimes it's detected as "unallocated space" (disk space that doesn't belong to any partition). In rough terms it's a non-standard mess that only MS knows well about. Basic norm: leave it alone (I suppose this is why Disk Management omits it, but 3rd party utilities apply the "nihil prius fide" criterion -nothing before truth, or fidelity understood as precise and inconditional concordance with reality-).

From those 2 Recovery partitions, most likely the partition 5 is the real one (you can check it running "reagentc /info" from an elevated command prompt) because it's larger and in the "modern" position (ancient enough Win10 versions placed the Recovery partition as first partition, and when Windows moved it to the modern position just after C: itself, it left the ancient Recovery partition alone, even with the "Recovery partition id" -id is a number or long hex that identifies the partition's use-). Deleting the other is more "ordered" but in case it's possible at all, it's extremely tricky and complicated and Idk if it has tangible outcome. I've seen one case in which an installed app relied on it instead of the "modern and official one".

Answers:

1: MiniTool is more trustable and precise in the layout itself, although not all 3rd party apps show the "id" of a partition, the number/hexcode itself or its meaning, if it shows it or not might depend on if it's a free or paid version, in this MBR Win7 system MiniTool PW free shows the id number in right-click -> Properties.

2. I wouldn't delete any. If I'm right in that partition 1 is a remnant (and if you are ready to cope with some app using it and having to reconfigure or reinstall the app) you would want to move EFI and MSR partitions to the left so that you benefit those 300MB and get a more ordered layout, whatever the positive outcome may be. I have no clue about how to do it safely. If I'm right in that partition 5 is the real Recovery partition, you would lose its functions. In this case you'd need an ordered Windows reconfiguration that is tricky and complicated, although the partition management part would be easier.

3. It's the so called MSR partition not shown by Windows Disk Management as told above.

If you're having problems with KB5034441, the shorter and easiest path in your case is extending partition 5 to the right (provided "reagentc /info" says it's the real Recovery partition). My own experience with this update is it's irrational, a lottery, a can of worms and a minefield, so let me not giving precise directions and stating "at your own risk" (and I strongly advise backupping beforewards with an imaging tool). I did not have unallocated space at the right so I shrunk C: maneuvering as advised by MS, doing a 2 GB Recovery partition (given my disk layout, it could have well over 100 GB if needed, I did all kinds of attempts including such "ultra-big" recovery partition). I finally succeeded with the downloadable "dynamic updates" version of KB5034441 and a script done by very expert people. The whole process is here (but you need a bigger Recovery partition beforewards, I did this with a 2 GB one) KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 .