![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
You need to use Disk Management to see the size of your Recovery Partition. You can also use File Manager to see what is on the Recovery Partition (show hidden files must be active). If your Partition is empty, and there are no files then you DO NOT have the needed files there. There are some good suggestions from Page 39 to Page 44. You should read them.
Here is some suggested actions, and it will explain some questions about reagent. If this does not work download the Windows OS to a Thumb Drive and reload the whole OS.
First, I was able to get all my Win 10 machines to accept this update with several steps completed. I agree with many others that this update does not seem to have any significant effect on operation or speed or anything that I can see.
You may want to open (from Windows) Disk Management by typing in the Search Bar "Create and Format Hard Disk Partitions" This should open the Disk Management plug-in. Look and see what you have on your OS drive - Usually Disk 0. You will need a larger Windows Recovery Partition (Win RE). One of a size of 800KB to 1024KB is needed. You can follow KB5028997 or the video https://www.youtube.com/watch?v=hlNtLcFqfOo (search on how to create a Windows Recovery Partition).
KB5028997: Instructions to manually resize your partition to install the WinRE update
Windows 10 Windows 10, version 1607, all editions More...
Summary
Microsoft has changed how it updates PCs that run the Windows Recovery Environment (WinRE). WinRE will be updated using the monthly cumulative update. This change only applies to PCs that get updates from Windows Update (WU) and Windows Server Update Services (WSUS). This change starts on June 27, 2023, for the Windows 11, version 22H2 cumulative update.
Some PCs might not have a recovery partition that is large enough to complete this update. Because of this, the update for WinRE might fail. You will receive the error message, "Windows Recovery Environment servicing failed.” To help you recover from this failure, this article provides instructions to manually resize your recovery partition if you get a system ErrorPhase of 2. This requires your device to have the recovery partition after the OS partition. Use the steps below to verify this.
Manually resize your partition by 250 MB
- Open a Command Prompt window (cmd) as admin.
- 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.
- To disable the WinRE, run reagentc /disable
- Shrink the OS partition and prepare the disk for a new recovery partition.
- To shrink the OS, run diskpart
- Run list disk
- To select the OS disk, run sel disk<OS disk index> This should be the same disk index as WinRE.
- To check the partition under the OS disk and find the OS partition, run list part
- To select the OS partition, run sel part*<OS partition index>*
- Run shrink desired=250 minimum=250
- To select the WinRE partition, run sel part*<WinRE partition index>*
- To delete the WinRE partition, run delete partition override
- Create a new recovery partition.
- 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.
- If your disk is GPT, run create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the command gpt attributes =0x8000000000000001
- If your disk is MBR, run create partition primary id=27
- To format the partition, run format quick fs=ntfs label=”Windows RE tools”
- 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.
- To confirm that the WinRE partition is created, run list vol
- To exit from diskpart, run exit
- To re-enable WinRE, run reagentc /enable
- To confirm where WinRE is installed, run reagentc /info
Note If creation failed or you do not want to extend the WinRE partition, run reagentc /enable to re-enable WinRE.
"KB5028997: Instructions to manually resize your partition to install the WinRE update" is pretty good, and will give you some written directions.
Changes: I shrunk the OS (main) partition from its present size to a smaller size from (600 to1024KB) to allow for the increase of the Windows Recovery Partition. You will have to test your drive capability from Diskpart CMD to see what is allowed. Here is the quote from KB5028997: Run: shrink desired=250 minimum=250. You might not have this space available to change the amount to 600KB or 1024KB and have to go with a smaller shrink size, depending on your drive size and your OS Partition. You will need to do this first.
Next is to follow the directions in KB5028997 to delete and create your Windows Recovery Partition depending on your disk type MBR (older machines) or GPT newer UEFI machines. Follow the directions to create (specify) the Partition Primary ID,
Problem: I was unable to use the "Quick Format and Label commands for some reason. Came back with an error every time. I used: FORMAT fs=ntfs
IMPORTANT: Make sure you are still pointed at the RIGHT PARTITION in Volume 0 BEFORE you do this! - The new Partition you just made will likely be Partition 3 or 4 or 5, you do not want to FORMAT your OS Partition.
Note: If you want to label this partition you can or use the partial freeware: Mini Partition Wizard or AOMEI Partition Assistant if you want, it is not necessary, but might make you feel better. This part of the job is free, no need to buy the farm.
Follow the directions and check to see that you now have a Recovery Partition of the proper size, nice to have 800 to 1500KB if you have it available.
With my PC's that would not complete this update I found the reagentc was disabled, and had no recovery partition location present. I believe the loss of a Windows Recovery location starts with your PC updates to a new Hard Drive or from a HDD to an SSD upgrade.
It is required that you have a working reagentc or the Windows Update will not complete - hence the error we all have.
Check to see if it is active:
Run Command Prompt as administrator
Run: reagentc /info
See if the reagent is ENABLED (Active). If it is not, and there is no Recovery location shown, you will need to make one. There are some good videos on how to do this. This one is good and safe: https://www.youtube.com/watch?v=hlNtLcFqfOo
Follow the directions in this video exactly. You will need to change, or fix, or copy the needed files from another PC that has completed the update and has reagentc enabled.
In File Manager, Go to:
Windows > System32 > Recovery
As the youtube Video states, you will need to check (or change) the file settings to VIEW "Hidden Items" and then in Folder Options uncheck "Hide protected operating system files" to see all the files in this folder.
Note: You will be prompted with a warning not to do this, but do it anyway and bypass the warning. Then click Apply to Folders (or Apply). Hopefully this will then show the following required files in the directory above:
$PBR_Diskpart.txt
$PBR_ResetConfig.xml
Reagent.xml
Winre.wim
FYI: Doing all this fixed three Win 10 PCs I have that would never complete the Update.
The file that is likely missing is Winre.wim and that is the one you will need and must have. NOTE: If your reagentc is working and enabled you will NOT see this file. (I believe ever / never). If your reagentc is not enabled and active you should see this file.
If reagentc is not (enabled) working you will need to have these files to make it work. You will need to borrow them from a working machine with a Windows OS exactly like yours. Copy all the files from the working machine to a thumb drive. Copy the file(s) over to the location above.
IMPORTANT: It must be the same version of Windows 10 as is on your problem machine. Read comments on files below:
Example of my working machine that I borrowed the Winre.wim file from another PC I have:
OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
If you want to hide the system files and hidden files when you are done, then uncheck them so accidents do not happen.
Next, you may want EXIT out of CMD, File Manager and everything else.
Restart your PC.
Open up a CMD Window in Admin mode and run:
reagentc /info This should show if reagentc is working properly
See what happens, if it is not working then Run:
reagentc /enable
Verify it is now working with:
reagentc /info
The command should come back as "Operation Successful" and reagentc will be enabled. It is now working as it has found the Recovery files it needs from the file(s) you copied into Windows > System32 > Recovery
Now you can run the Windows Update. I believe it will take a few minutes to complete, but should not come back with the Red Error 0x80070643
I am curious what kind of Win OS Drive do you have? Is it GPT or MBR. This is important. It sounds like you have a MBR. If you follow the directions given for an MBR Drive to the letter the Partition is not ID'd properly. Also I assume you are NOT using Bitlocker. Also assume you do not have a Over Partitioning SSD active or a Momentum Cache active on SSD. Please read through all this first.
By your screen shot it looks like reagentc is working properly and is pointed at Partition 4. Likely you are on DISK 0. Your size is plenty big, unless you want it to be 1024 (this will equal 1000MB).
Before you start run reagentc /disable.
Wish you had a screen shot of Disk Management screen.
I believe you just have not ID'd the Partition 4 properly to either the MBR Disk ( ID=27) To do this using DISKPART just navigate to your Windows Recovery Partition for example: Partition 4 and then use the command SET ID=27
Exit and
reagentc /enabled
Exit again.
Restart the PC
For the GPT Drive if you have it (ID=de94bba4-06d1-4d40-a16a-bfd50179d6ac and followed by the command gpt attributes =0x8000000000000001 This is 0x8 with 14 zero's and a 1. This is straight out of KB5028997. You can go to CMD ADMIN then DISKPART then use, for example: SEL DISK 0 and SEL PART 4 and DET PART (this will give you details of the partition) to be sure you are looking at the right partition. If you see the above ID in the TYPE: then do nothing. If you see the above ATTRIB code then do nothing. Otherwise, you need to use SET ID= (the code above no spaces and enter) then set ATTRIBUTES= (the code above no spaces and enter) You can check your work with DET PART and look at the details of the partition. Should look like this:
Partition : 4
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Attrib : 0x8000000000000001
Offset in Bytes: (A huge number)
Now type exit (out of DISKPART).
now type reagentc /enable
It should come back with a normal Operation Successful reagentc
Exit again.
Restart your PC.
If this is too much, just start over with the deleting and creation of your Partition 4. The directions from Microsoft do work if followed for the GPT Drive Type.
Read Below, watch the video.
When you are done, you should not see this hidden partition in File Manager, you will see it in Disk Management, and it will be identified as a Healthy Recovery Partition.
Not sure you looked at my earlier post, but you can download the Mini Tool Partition Wizard (Free). You can LABEL the Partition if you want. Windows will know where it is and what it is by the ID.
If you like videos this one on Creating a Recovery Partition is very good: https://www.youtube.com/watch?v=hlNtLcFqfOo
Follow the directions EXACTLY.
PS: One person said the Windows Recovery Partition is always 4. This is not quite right, on my machines it is usually 4, but can be 3 or 7 or others, or it could be one of two Recovery Partitions (this is what my Win 11 machine has. and one of my Win 10 PCs). PS: Win 11 machine did this update with no trouble.
With my older MBR PC I did need to go back and ID the Partition with the SET ID=27 command. Pretty sure most people who do all this stuff have to do the same thing.
Windows update (KB5034441) Error (0x80070643)
When I tried to install the windows update "2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" I received the error code (0x80070643).
I have already tried, restarting my computer, waiting a bit before retrying, running a memory diagnostic check, checking all my drivers for updates, installing optional updates, and running a malware scan.
When I tried to run the windows update troubleshooter it said "diagnosing problems" but never fixed them and I was still unable to install the update after running the trouble shooter.
Any help would be appreciated.
Reply
I have the same question (2136)
Subscribe
|
Report abuse
Previous 1 ... 34 35 36 37 38 Next
LE
LEWCARVER
Replied on April 20, 2024
Good advice given for you to start over with the Recovery Partition. You need to make a Recovery Partition as you do not have one.
Reply
Edit
QS
Qstik
Replied on April 20, 2024Report abuse
In reply to LEWCARVER's post on April 20, 2024
OK, I did a repair installation of Windows 11 Pro. An 846 MB Recovery Partition is now in place.
Disk Management now looks like this:
Unallocated space at the ends of SSD devices is Samsung Magician Over-Provisioning (~10%).
Unfortunately, File Explorer still shows a phantom Drive Z. I may hide it as you suggest, or just ignore it.
Thanks for your help and suggestions.
Reply
Was this reply helpful?
Yes No
QS
Qstik
Replied on April 20, 2024Report abuse
In reply to Qstik's post on April 20, 2024
LEWCARVER, I successfully hid my phantom Z drive using MiniTool Partition Wizard.
I'm uncomfortable with using a work-around, but will live with it for now.
Thanks.
Reply
Was this reply helpful?
Yes No
LE
LEWCARVER
Replied on April 20, 2024
QSTIK. You may want to shut off Samsung Magician Overprovisioning (and whatever else is offered to upspeed your SSD). There are some warnings to shut down these SSD upspeeds in this Microsoft post to get Update KB5034441 to run and complete. I shut mine down (Crucial SSD) and other PCs that I have worked on for this problem. Likely the Magician is using the 84.19 GB Unallocated block of the drive (it is not really unallocated - yes it is Magic). It also may be the source of your mysterious Z Drive. If you don't want to see Z , hide it. It will not harm anything. Pretty sure it will be gone from File Manager / My Computer. It will still be visible in Disk Management.
Note: Running these SSD upspeeds IS a proven cause of trouble with completing the MS KB5034441 update. Hope the update is working for you now.
Not sure why you have so many Partitions. I have seen some users put their OS on a small SSD for speed improvements. There may be some kind of increase in speed that I don't know about or some file size limitations in the root of the drive that requires you to put your data in its own Partition? It is pretty unusual.
I have not had any noticeable increase in speed using these Magician / Mysterioso SSD upspeeds. They are Voodoo. Many others agree they are not worth the trouble.
Reply
Edit
QS
Qstik
Replied on April 21, 2024Report abuse
In reply to LEWCARVER's post on April 20, 2024
LEWCARVER - As far as I know, Samsung Over Provisioning assists in wear leveling for extended SSD life and "garbage collection" (I'm not really sure what that means to an SSD). However, I don't have Samsung Magician set to do any RAM caching, which I think is your concern. I now have 84 GB of unallocated space beyond a 846 MB recovery Partition on my Boot Drive for over provisioning. I hid the Z phantom drive per your suggestion. At this point, I'm good to continue as is.
Thanks again for your help.
Reply
Was this reply helpful?
Yes No
VA
vayvanne
Replied on April 22, 2024Report abuse
In reply to Qstik's post on April 21, 2024
Hi Qstik. My replies are getting jammed. Sorry for a delay with response. You got impressive and curious storage setup. Over-provisioning space is why the standard Microsoft’s resize script with shrink operation did not work for you. AFAIK over-provisioning soace does not have to be specifically unpartitioned but just not in use.
I suggest moving RE into a separate recovery partition as you will be able to use it even in case of issues with C: drive. Just use option size= with create partition primary to create it because by default it will use all space unpartitioned.
And I would allocate free space to system partition as it is overkill and all modern SSDs does over-provisioning in firmware.
Reply
Was this reply helpful?
Yes No
MR
Mount Redoubt
Replied on April 22, 2024Report abuse
In reply to LEWCARVER's post on April 20, 2024
This finally what worked for me (I read a lot and tried a lot of methods).
Download Windows 22H2 from the Microsoft website. You can either create an ISO or a USB with the media creation tool (the next steps will be easier with a USB). If you use an ISO you will have to mount it virtually.
Find the install.ESD file (usually in the root directory of the ISO or USB). Convert it to install.WIM following these steps.
Create a directory for the install.ESD and copy the file you located above.
From that directory, enter:
Check the status of recovery
reagentc /info
Disable windows recovery
reagentc /disable
dism /Get-WimInfo /WimFile:install.esd
dism /export-image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity
Open the install.wim with 7zip (or peazip) and scout through the directory trees to locate folder winre.wim (including reagent.xml
copy the contents of the folder into C:\Windows\System32\Recovery (while in 7zip or peazip)
Then resize your recovery partition using the steps outlined here:
diskpart
list disk
sel disk<OS disk index of your windows boot drive, usually it is zero>
diskpart
list part
(note from the list, information will be provided that the disk is GPT or MBR, I will address GPT)
select part*<WinRE partition index>*
shrink desired=250 minimum=250
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes =0x8000000000000001
format quick fs=ntfs label=”Windows RE tools”
list vol
exit (from diskpart)
Finally, run:
reagentc /enable
run the problem update (took a long time on my computer)
A video of the partition resize procedure is here:
https://www.youtube.com/watch?v=7J_wPCampdU&t=323s
Reply
Great! Thanks for your feedback.
How satisfied are you with this reply?
Reply
Reply with quote
Standard
This is an excellent summary of the issues that are stopping this Microsoft Update from being completed. It will resolve all the issues, that I am aware of, and allow completion of the update. That annoying red warning should be eliminated. That is. if you follow the directed actions. If you are familiar with working with the Command Line and Diskpart you can complete the steps properly. I would recommend using an OS Partition shrink size of 1024MB (this will give you a 1000MB Recovery Partition size - much like what is used, or created, with Win 11 PCs.
The use of the Microsoft Windows 22H2 Update to extract the install.esd to install.wim is very creative and will work to get the needed Recovery Files (mainly Winre.wim) that are required. It will work if done as you have directed.
The directions do focus on a GPT file system, as you noted, and they cover many of the machines experiencing problems. If you have an older MBR PC or Drive you will need to follow the directions for that machine to set up your Recovery Partition Properly. The hardest PCs to get this update to complete on are MBR (my opinion).
Some advice: If you can't get the Windows Update KB5034441 to complete without the error 0x80070643, start over from the beginning. Backup your OS Partitions, carefully delete your Recovery Partitions and run Diskpart reagentc commands as directed. On several PC's that were trouble, I had to place the recovery files in the OS location first: Windows > System32 > Recovery. They will then be placed in the Recovery Partition when reagentc is run successfully.
I don't think Microsoft will create some Update that will cover all the issues and steps covered in this Post. You will have to do this on your own or have someone help you. That is what those IT Nerds do. Good Luck with this MS Adventure.
Notify me when someone responds to this post
VZ
Volume Z
Replied on April 22, 2024Report abuse
In reply to Mount Redoubt's post on April 22, 2024
select part*<WinRE partition index>*
shrink desired=250 minimum=250
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes =0x8000000000000001
format quick fs=ntfs label=”Windows RE tools”
list vol
exit (from diskpart)
You're adding confusion. Recovery partition shrunk (attempted, as it fails) 😲, nothing deleted 😲, install.esd converted when it can be opened in 7-zip 😲, partitions altered when replacing Winre.wim is enough 😲.
Reply
Was this reply helpful?
Yes No
MR
Mount Redoubt
Replied on April 22, 2024Report abuse
In reply to Volume Z's post on April 22, 2024
It actually expands the partition, did you watch the youtube video or read the microsoft workaround page? Methinks you have not.
Reply
Was this reply helpful?
Yes No
VZ
Volume Z
Replied on April 22, 2024Report abuse
In reply to Mount Redoubt's post on April 22, 2024
The video may. You don't.
Reply
Was this reply helpful?
Yes No