Question KB5034441 error 0x80070643 resize recovery Part for WinRE update

[yoji]

[Moderator note: Moving thread from Windows 10 to Storage. More applicable.]

Todays MS updates.. both my and my wifes machines failed the kb5034441 update with a 0x80070643 error
linking to the MS article for the update.. says the error if your recovery partition to small.. and links to this article to manually extend it.
https://support.microsoft.com/en-gb...e-update-400faa27-9343-461c-ada9-24c8229763bf
Trouble is... I cant see how that will work... what am i misunderstanding?
My concern is re point 4.g/h... where it has shrunk the OS partition to make room to extend the recovery partition.
but then deletes the current recovery partition.
It then create a whole new recovery partition...
but surely, whatever was in the original partition you deleted is now lost? so just creating a new partition does nothing... its just empty?
I did try it... and sure enough.. it does not work.. if you use the "reagentc /info" command it says it disabled and has no location for it.. and if you try "reagentc /enable" .. nothing happens..
So what have I missuderstood about this... how can/should I extend my recovery partition?
SO I recovered my whole C drive, and am back to square one... with a working recovery drive.. but still to small for th eupdate. to install 🙁

Thanks in advance for any insight.

 

[Ralston18]

The link provides the instructions for resizing the recovery partition.

Before doing anything open Disk Management.

Expand the window so all can be seen and take a screenshot.

Do that for both computers and post the screenshots here via imgur (www.imgur.com)

Be sure to indentify each screenshot with respect to whose machine it is. Nothing personal - just "Mine" and "Wife" will work.

Objective being to get a full understanding of the current partitioning.

I am also going to move this thread from Windows 10 to Storage. More applicable - especially if help is required with the partitioning process.

 

[ronczap]

There are several Youtube videos about this issue
Windows 10 22H2 Fails to install KB5034441 ignore for now fix will be there soon

Resizing the Recovery Partition sounds risky...

I ran the Windows Show/Hide tool to hide this particular update for now...

 

[Neelfy]

Looks like MS have messed up. Either way you should not have to mess around with partitions to get it to install. ***

[Mod edit to remove profane acronym. Remember this is a family friendly Forum.]

My recovery partition is more than double the size of the "Required" recovery partition size and it still fails. Have also heard of others who have followed the instruction from MS and it has still failed. Guessing they will realize the [mistake] and produce a fix.
So proably best to leave alone for now and see what they come up with in next couple of days.

 

[Ralston18]

Take a look at the partioning via Powershell's Get-Partition cmdlet.

Results from my computer:


PS C:\WINDOWS\system32> Get-Partition


DiskPath: \\?\scsi#disk&ven_ata&prod_samsung_ssd_870#6&3af99ce4&4&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

PartitionNumber DriveLetter Offset Size Type
--------------- ----------- ------ ---- ----
1 17408 15.98 MB Reserved
2 T 16777216 931.5 GB Basic


DiskPath: \\?\scsi#disk&ven_nvme&prod_kbg30zms256g_nvm#4&381e1525&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

PartitionNumber DriveLetter Offset Size Type
--------------- ----------- ------ ---- ----
1 1048576 650 MB System
2 682622976 128 MB Reserved
3 C 816840704 224 GB Basic
4 241339203584 990 MB Recovery
5 242377293824 11.66 GB Recovery
6 254897291264 1.07 GB Recovery


DiskPath: \\?\scsi#disk&ven_samsung&prod_ssd#4&381e1525&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

PartitionNumber DriveLetter Offset Size Type
--------------- ----------- ------ ---- ----
1 1048576 128 MB Reserved
2 D 135266304 465.63 GB Basic

The results may prove useful for further troubleshooting or reference purposes.

 

[SETSERO70]

[Moderator note: Moving thread from Windows 10 to Storage. More applicable.]

Todays MS updates.. both my and my wifes machines failed the kb5034441 update with a 0x80070643 error
linking to the MS article for the update.. says the error if your recovery partition to small.. and links to this article to manually extend it.
https://support.microsoft.com/en-gb...e-update-400faa27-9343-461c-ada9-24c8229763bf
Trouble is... I cant see how that will work... what am i misunderstanding?
My concern is re point 4.g/h... where it has shrunk the OS partition to make room to extend the recovery partition.
but then deletes the current recovery partition.
It then create a whole new recovery partition...
but surely, whatever was in the original partition you deleted is now lost? so just creating a new partition does nothing... its just empty?
I did try it... and sure enough.. it does not work.. if you use the "reagentc /info" command it says it disabled and has no location for it.. and if you try "reagentc /enable" .. nothing happens..
So what have I missuderstood about this... how can/should I extend my recovery partition?
SO I recovered my whole C drive, and am back to square one... with a working recovery drive.. but still to small for th eupdate. to install 🙁

Thanks in advance for any insight.

I followed the tutorial you sent and everything went as expected, the partition was deleted and recreated and I restarted the PC just to be sure, after turning it on I went to Windows update and clicked on try again and it went fine, are u sure that u followed it right? now the recovery partition is with 700mb, follow the image

https://imgur.com/a/DXkmx9V

View: https://imgur.com/a/DXkmx9V

 

[yoji]

The link provides the instructions for resizing the recovery partition.

Before doing anything open Disk Management.

Expand the window so all can be seen and take a screenshot.

Do that for both computers and post the screenshots here via imgur (www.imgur.com)

Be sure to indentify each screenshot with respect to whose machine it is. Nothing personal - just "Mine" and "Wife" will work.

Objective being to get a full understanding of the current partitioning.

I am also going to move this thread from Windows 10 to Storage. More applicable - especially if help is required with the partitioning process.

Thanks... Looks like consensus is to wait.. as lots of people have problem so we can probably expect a fix from MS.. but for fun.. here is my storage config (my PC).. It does look strange (since the full recovery of my C drive from backup) as no partitions are tagged as "recovery" (they were before restored). And there were 2 the 449mb and the 571mb one.. I guess at some point MS expanded storage, so the 449mb is redundant.. and the 571 is the active one (see the CMD output at bottom of screen shot)...
Also, just to say.. the 23gb unallocated is deliberate.. its a Samsung SSD, so its the 10% over provisioning that is recommended. Anyway - Any questions... just shout.
Screen shot ---> https://1drv.ms/i/s!Asw-ZJYHTEcTgtRz0SNp3bKQpRayZA?e=KcoCva

 

[Ralston18]

Waiting seems to be a good option for the moment.

Trying to do something in the meantime may interfere with a forthcoming fix.

= = = =

One side note - the G: drive Backups has only 26% of free space.

A rough rule of thumb is to maintain 20-30% free space on any given drive.

I do not know the size of the backups nor what settings are in place to delete older backups as the disk space fills.

Is that 119 GB of space enough for the next backup?

Not an immediate concern per se: just something to keep in mind as well.

 

[yoji]

Waiting seems to be a good option for the moment.

Trying to do something in the meantime may interfere with a forthcoming fix.

= = = =

One side note - the G: drive Backups has only 26% of free space.

A rough rule of thumb is to maintain 20-30% free space on any given drive.

I do not know the size of the backups nor what settings are in place to delete older backups as the disk space fills.

Is that 119 GB of space enough for the next backup?

Not an immediate concern per se: just something to keep in mind as well.

Thanks.. its all good..
its mostly 200gb of data which just grows by about 10gb a year... which is there as a source to sync to cloud for safe keeping.
my iphone backup of about 25gb
and the actual backup is a 10GB backup from my NAS... that has a weekly incremental of about 500MB... has 4 weekly incremental.. then a full.. with 2 chains. so plenty of space..
It has been a bit of a dump of some short term crap... so had a tidy up.. and now about 207GB free.

 

[Ralston18]

👍

 

[yoji]

OK.. update...
My OCD kicks in if my PC/Windows install is not working 100%...
and the fact that my "disk Management" was screwy (with 2 x recovery.. but not showing correctly (see above posts)) means I could not leave it alone... so did a fresh install of Win 10 "over the top"
That went through fine... but did not resolve the issue with disk management not identifying the recovery partition correctly.
So... confirming via the "reagentc /info" command that it was saying the 551MB partition was the recovery partition, I deleted the old 449mb partition (on assumption windows was getting confused with 2x recovery partitions)...
I then rechecked "windows update" and it then successfully installed all updates...
SO I am fully up to date, with no update errors 😊😊

 

[Gobbo89]

Waiting seems to be a good option for the moment.

Trying to do something in the meantime may interfere with a forthcoming fix.

= = = =

(...)

I didn't like the idea to mess with my partitions, so I waited. As of today the issue is still there.
Should we still wait or is there any other suggestion?
ty

 

[Ralston18]

Agree - do not mess with the partitions.

Three things:

1) Run Disk Manager again and open the window so all can be fully seen. Take a screen shot and post here via imgur.

2) Run Powershell as Admin and again run Get-Partition per Post # 5. Copy and also post the results.

3) Wait.

Premise being that nothing is really wrong and that windows "knows" what it needs. Even if the partition sizes are not as might be expected.

1 & 2 above are mostly just a "sanity check". If anything is out of line and truly a problem (potential or otherwise) then that may become apparent. Need updated results based on the current installation and configuration.

And there are some very knowledgeable folks regarding disks, drives, partitions who may then comment accordingly.

If your systems are currently performing well and remaining stable then apply the following rule:

"If it ain't broke, don't fix it".

 

[yoji]

I didn't like the idea to mess with my partitions, so I waited. As of today the issue is still there.
Should we still wait or is there any other suggestion?
ty

My update... per my above post.. I did manage to fix my situation... deleting the extra/old redundant 449mb recovery partition seemed to clear the issue.. and the update applied OK (to the 571mb active recovery partition).
HOWEVER... I tried the same fix on my wifes machine.. (i.e. deleting an old/small/redundant recovery partition) but it did not fix... and she still has the issue (her active recovery partition is smaller than mine at 533MB... not sure if that significant). So I am now waiting for MS to address... which I am not really expecting until next months update cycle..

 

[Gobbo89]

Agree - do not mess with the partitions.

(...)

If your systems are currently performing well and remaining stable then apply the following rule:

"If it ain't broke, don't fix it".

Thank you.
Partition look just fine. Like others I do have two partitions marked as Recovery (one smaller than the other) which might be the issue.

I agree "If it ain't broke, don't fix it", however security is also a concern, and this being a security update makes the whole situation unpleasant. I will wait 🙄

My update... per my above post.. I did manage to fix my situation... deleting the extra/old redundant 449mb recovery partition seemed to clear the issue.. and the update applied OK (to the 571mb active recovery partition).
HOWEVER... I tried the same fix on my wifes machine.. (i.e. deleting an old/small/redundant recovery partition) but it did not fix... and she still has the issue (her active recovery partition is smaller than mine at 533MB... not sure if that significant). So I am now waiting for MS to address... which I am not really expecting until next months update cycle..

I also have one 450 MB and one 505 MB recovery partitions, Windows RE is located on the 505 MB one.
As I said, I really don't feel like messing around with that. Happy it fixed it for you, even though your wife PC is still stuck with the issue. I'm wondering what might be the difference, beside smaller size.
Anyway it sucks, because waiting one month or more to be able and apply a security update should never be the case.

 

[MarcCouture]

Easy fix for noobs: use Windows's Disk Management tool to shrink your main partition (say, by 500mb), install Minitool Partition Manager free edition (or another partitioning tool), resize your existing recovery partition by including the space you recovered in the previous step, apply changes, save and reboot the PC. The update will then install just fine.

Most users will definitely not be comfortable doing this, and they should wait for a fix from the source that will automate everything.

 

[yoji]

Easy fix for noobs: use Windows's Disk Management tool to shrink your main partition (say, by 500mb), install Minitool Partition Manager free edition (or another partitioning tool), resize your existing recovery partition by including the space you recovered in the previous step, apply changes, save and reboot the PC. The update will then install just fine.

Yes.. if you look at my OP.. you can see I was using the official MS solution.. and it didnt work.. I posed a question on how their solution would work.. since it does not seem logical...
no-one has explained why my stated concern is unfounded... From one of my other posts.. I have fixed mine now, but my wifes machine is not fixed.. and I did see another post elsewhere say that just extending does not work... and that the recovery partition has to be at the end of the drive... which would fit with my wifes machine, where the recovery partition is before the main system partition (as you look left to right in the disk management window)
As I am clearly a "noob"... interested in your perspective.

 

[MarcCouture]

I've done this on various machines, all had their recovery partitions at the end of the drive (where it should be), 100% success rate with graphical partitioning tools. I rarely follow Microsoft solutions to anything regarding hardware configuration, most of the time, they skip essential steps or are simply wrong.

 

[yoji]

I've done this on various machines, all had their recovery partitions at the end of the drive (where it should be), 100% success rate with graphical partitioning tools. I rarely follow Microsoft solutions to anything regarding hardware configuration, most of the time, they skip essential steps or are simply wrong.

Interesting.. my wifes machine is very basic, and an old install. I would not have done anything special.. just installed Win 10 without any special config.. yet it did/does have 2 recovery partitions a smaller 450mb one and a larger 530mb one, suggesting that something decided it needed a bigger one at some stage and created it (the 530mb one is the "active" recovery partition according to the "reagent /info" command).
Presume whatever process created it, put it where it is.. as I have not messed with her machine to move anything. The only thing I might have done is use Samsung magician to create the 10% overprovisioning space they recommend for their SSDs. which I suspect just shrinks the main system partition to make space.. so would not move a recovery partition.

Someone above does say they used the MS solution I linked, and it worked... but looking at it.. I cant see how it is supposed to work (for reasons I detail in my original post).. so still interested for someone to explain how that works.

 

[SkyNetRising]

Interesting.. my wifes machine is very basic, and an old install.
yet it did/does have 2 recovery partitions a smaller 450mb one and a larger 530mb one, suggesting that something decided it needed a bigger one at some stage and created it

Can you show Disk Management screenshot from your wife pc?

Someone above does say they used the MS solution I linked, and it worked... but looking at it.. I cant see how it is supposed to work (for reasons I detail in my original post).. so still interested for someone to explain how that works.

What step did you not understand?

Manually resize your partition by 250 MB

1. Open a Command Prompt window (cmd) as admin.
2. To check the WinRE status, run reagentc /info. If the WinRE is installed, there should be a “Windows RE location” with a path to the WinRE directory. An example is, “Windows RE location: [file://%3f/GLOBALROOT/device/harddisk0/partition4/Recovery/WindowsRE]\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE.” Here, the number after “harddisk” and “partition” is the index of the disk and partition WinRE is on.
3. To disable the WinRE, run reagentc /disable
4. Shrink the OS partition and prepare the disk for a new recovery partition.

a) To shrink the OS, run diskpart​

b) Run list disk​

c) To select the OS disk, run sel disk<OS disk index> This should be the same disk index as WinRE.​

d) To check the partition under the OS disk and find the OS partition, run list part​

e) To select the OS partition, run sel part<OS partition index>​

f) Run shrink desired=250 minimum=250​

g) To select the WinRE partition, run sel part<WinRE partition index>​

h) To delete the WinRE partition, run delete partition override​

5. Create a new recovery partition.

a) 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.​

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

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

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

6. To confirm that the WinRE partition is created, run list vol
7. To exit from diskpart, run exit
8. To re-enable WinRE, run reagentc /enable
9. To confirm where WinRE is installed, run reagentc /info

1-3. Disable windows recovery.
4. Shrink OS partition and delete old recovery partition.
5-7. Create/format new larger size recovery partition.
8-9. Re-enable windows recovery.

 

[yoji]

Can you show Disk Management screenshot from your wife pc?

What step did you not understand?



1-3. Disable windows recovery.
4. Shrink OS partition and delete old recovery partition.
5-7. Create/format new larger size recovery partition.
8-9. Re-enable windows recovery.

OK.. now I am going to sound MAD!!!... but seriously.. my wifes machine did have 2 x recovery partitions.. like mine did (see screen shot in one of my above posts).. and I did delete the smaller one (having confirmed that her 533mb one was the active one)... and I did nothing else.. I did not recover/reassign the freed up 450mb... but now.. there is no sign of the old recovery partition!! WTH!!! I cant believe I am that mad.. may be the 450mb was next to the overprovision area.. so just merged when deleted? I dont recall it that way.. but quite possible I am wrong.. its the only logical explanation.
But here is a current screen shot of her disk config (and recovery is now between system partition and the unassigned "overprovision" space for the SSD!!!).. am I going mad? or is there some process that can explain?
my wifes disk config --> https://1drv.ms/i/s!Asw-ZJYHTEcTgqYprCnfvs5kqj-FLQ?e=RON95r
I did try and reapply the kb5034441 update on her machine today .. and it again failed.

As i said in my original post, the bit I dont understand is
1. I assume the recovery partition contains key data.. which is used in the recovery process.
2. So if we delete it.. we destroy the data
3. Creating a new partition.. in a new location on the disk.. also means new partition is empty
4. Formatting will also destroy any data.
5. So unless the reenable actually writes the new system restore data.. its going to be empty/useless?

As i said in OP.. I did try it and it did not work (I didnt do exact...as I didnt shrink system part, as I just ate into the unallocated "overprovision" area, but cant imagine that would be responsible for the failure).

So right now.. I am beginning to doubt my sanity.. .. but any insight appreciated.

 

[SkyNetRising]

the bit I dont understand is
1. I assume the recovery partition contains key data.. which is used in the recovery process.

No. There is no "key data".
It's just windows recovery environment.

2. So if we delete it.. we destroy the data
3. Creating a new partition.. in a new location on the disk.. also means new partition is empty
4. Formatting will also destroy any data.
5. So unless the reenable actually writes the new system restore data.. its going to be empty/useless?

Yes. Re-enabling recovery environment installs recovery environment into recovery partition.

I did try it and it did not work (I didnt do exact...as I didnt shrink system part, as I just ate into the unallocated "overprovision" area, but cant imagine that would be responsible for the failure).
So right now.. I am beginning to doubt my sanity.. .. but any insight appreciated.

Delete old recovery partition and make a new one - 750MB.
(disable windows recovery before this and re-enable after)

 

[yoji]

No. There is no "key data".
It's just windows recovery environment.

Yes. Re-enabling recovery environment installs recovery environment into recovery partition.

Delete old recovery partition and make a new one - 750MB.
(disable windows recovery before this and re-enable after)

Thanks.. you gave me the confidence to try again...
Its hard to know where I went wrong last time.. I think I may have thought the drive was GPT (which my machine is) instead of MBR, so may have taken a wrong turn (but would have thought I would have had/seen an error message if that the case?)
And this time did not go without incident.. as I tweaked the instructions to specify the size of 750mb (as I didnt want it to use all space, as it would have run into the 23gb overprovision space)... but then it didnt seem to respect the id=27 of the command... so I had to do it separately.. or may be I did just type it wrong.. who knows..
Anyway - it was all set up correctly.. so the kb5034441 update applied OK and was happy.. so all done..

Thanks for your help.

 

[SkyNetRising]

Anyway - it was all set up correctly.. so the kb5034441 update applied OK and was happy.. so all done..

Great. 👍

 

[Gobbo89]

(...)

Most users will definitely not be comfortable doing this, and they should wait for a fix from the source that will automate everything.

Well, MS said there won't be any automatic fix:

Source: https://learn.microsoft.com/en-au/windows/release-health/status-windows-10-22h2#3231msgdesc