Thanks it fixed the issue, I really hate how incompetent Microsoft is. Users shouldn't have to fix what mistakes they did, and its not easy steps either. Smallest mistake can delete your whole computer.
And in a year we are more pestered from the money-mafia Microsoft, that made sure that Windows 11 DID NOT MEET THE MINIMUM OF REQUIREMENT.,.....so our Window 10 computers have to be scrapped, as no support anymore..... Seems like terror!! Why is Window 11 made to use Widows 10 on for instance Lenovo T 60 and 61 UNSUDEABLE - what about compensation. PS. why is this security (0x80070643) not installing, doesnt Microsoft know what they are doing!!! We pay for the program!!
Some media such as Windows Latest or Bleeping Computer are now reporting that Microsoft is aware of the problems and is working on fixing them. Redmond intends to provide further information "shortly". For the majority of those affected, I think it's a case of waiting and seeing what Redmond comes up with.@@nio7620
I was getting this issue on all my new windows 10 installs. This fixed it. For anyone thinking about attempting this fix, I would suggest opening the first link in the description so you can copy and paste commands.
NOTE: if you have MBR format, after you format, the id is lost and it converts back to PRIMARY. So you need to run this afterwards to get back to the same point he had. sel disk sel part set id = 27
at the beginning , when i ran "reagentc / info" , the recovery partition was on part 3 and the primary was on part 2 . I followed everything he did except for the create id because i dont have a gpt format . when i was done i ran "reagentc / info" but it says that the recovery is on part 2 now . I still have 3 partitions and they all show as primary when i run "list part" . Do you have any idea about this ?
i tried setting the id for partition 3 , so now partition 3 looks like its the recovery one , but whenever i run reagentc /info , it still shows that partition 2 is the recovery.
This actually worked! Thank you! This error was so annoying. All the generic troubleshooting guides didnt work, like stopping update service, clearing temp files, chkdsk, system repair, ...
That's weird... I followed the directions to a T and it worked first try. My advice would be to just wait for the next update. If it's not fixed by then, there will be enough people annoyed at Windows which will incentivize them to fix the dang thing. I update my PC once a month and it's ALWAYS something. @@XhitmanXX103
Other option is to ignore this repeated error. MS may find a different solution for this update that does not require so much recovery partition. Also, this change only matter if you are using BitLocker to encrypt your drive(s). If not, this update is not required especially for Windows 10 Home users that can't activate BitLocker; Pro and above versions only. Same code base, however, so they are pushing this change to everyone in case you upgrade your license to Pro or other in the future. Dumb, but it's a just in case CYA move by MS.
Do you think it could be caused by malware? I had my PC infected 10 days ago and day after i got infected i reinstalled the windows and then i thought i got rid of it. My PC no longer finds any threats and i think it's already fine, however this update 10 days later somehow makes me worry if some part of the virus has survived or not.. do you think it could be caused by this?
@@waidi3242 unlikely related in any way. This update issue is MS creating a default recovery partition size (512MB) many many years ago and it now not being large enough to accommodate update requirements. This is not related to malware. Yes. there is a BitLocker vulnerability. Are you running encrypted drives and BitLocker? If not, and this would be true for Home versions (no support for BitLocker), then this driver was not active and the vulnerability also not active. Nothing is impossible, just very unlikely.
@@Bare_Essence Alright then thanks :D I already followed this tutorial and got it fixed and nope, i don't use Bitlocker. So it's all fine i just got paranoid :D (i lately am very paranoid about it..)
If the reagentc.exe and the winre.win disappeared it could certain be malware. The reagentc.exe is a protected by the Trusted Installer process to prevent deletion. A process running at or above Trusted Installer access deleted the exe.
HEY THANK YOU SO MUCH! I am a certified PC Technician and have been in the industry for over 25 years. I was loosing my mind over this and your video was only solution i could find. ODD THING WAS MY RECOVERY part was larger than yours was at the end from the start. i still increased 250mb and it worked on the first try. I was a bit nervous, I never disabled recovery parts in CMD until today. YOUR A LIFE SAVER, I WILL LIKE and Subscribe. HAPPY YEAR
***How to fix*** 1) Open a CMD window and "Run As Administrator" 2) Type DISM.EXE /Online /Cleanup-image /Restorehealth 3) After the DISM.exe command finishes then type 4) SFC /SCANNOW 5) After the SFC command finishes Reboot your computer 6) Run Windows Updates and ensure you are running the latest version of Windows 10 22H2 7) Install and scan your computer with a reputable anti-virus/security suite
If you are getting an error of not being able to shrink the partition, you are probably selecting the wrong partition. I wasn't paying close enough attention and I selected the recovery partition (so for him it was partition 4) before trying the shrink command, but it wouldn't let me. But we are trying to make the recovery partition larger not smaller. So we are selecting a different partition to shrink first so that there is enough space to make the recovery partition larger. I had read an article about this error and thought that for some reason Microsoft needed the recovery partition to be smaller, and I was very confused because that makes no sense. And of course it made no sense, because that wasn't what they wanted you to do haha. You need a larger recovery partition for the update to work.
Everything was going smooth up until the very end, I'm stuck, I can't enable my re agent with the /enable command. I'm met with "REAGENTC.EXE: The Windows RE image was not found. " any ideas? :(
Thanks, this helped a lot! For anyone else still having trouble, the exact instructions in this video / link didn't work for me at first, so I made a larger partition by using 750 instead of 250 and following all of the other instructions exactly as-is. That fixed everything and I'm up to date now.
Been wrestling with this bastard update for over a week. I followed your tutorial to the letter and it worked like a charm first time. Everything happened as it did in your example - just perfect. 👍 I now have no pending updates. Thanks so much for your help. Kindest regards, Andy, London UK. 😊
I keep getting this message when I go to shrink the partition of the primary: "Virtual Disk Service error: The specified shrink size is too big and will cause the volume to be smaller than the minimum volume size."
this was a huge help! followed everystep and had to spell out all the long codes but it was worth it. very easy steps and well spoken directions. thank you for the help man!
Well... That was scary, at some points I thought I did something wrong but I just slowly followed what you did and the problem is solved. Thank you for all your help! :)
Also......if you are going to increase the size of the Recovery Partition (and shrink the OS part), why only do a 250mb increase. It's not like you are going to miss even a 1 GB less disk space on the OS part, and if you increase more than the required 250mb, it may prevent MS screw up and needing more space in the future....Thoughts?
Appears to only work if the partitions are in the right order. When Disk Management shows recovery partition at end all is good but when recovery partition is tat the start the recovery partition does not expand in to the newly created space. I am guessing there is a way to do this by stealing more drive space from the primary and then somehow creating the new recovery in the new empty space but I am not sure of the commands and sequence?
@@raytorflurch9155 If it’s an issue on a new computer/for new images, I’ve fixed it by creating an entirely new image using a .wim file (using DISM in Windows PE) and modifying the “apply-image” batch file to create a partition with 1000MB instead of 500, so that it automatically is able to install the update after creating the partitions at the very beginning of the process. Alternatively, if you’re just looking for a quick fix for one computer, Microsoft has released a powershell script that you can use to manually apply what the security update fixes. I’ll find the link and send it here so you can use it if that’s what you need.
@@stefandothill Hey I get that same problem. Even though I have a new big partition now, when I type "reagentc /enable" I get "REAGENTC.EXE: The Windows RE image was not found." What is the fix that you mentioned that you did?
@@raytorflurch9155 You need to use the partion that's it right to next to the recovery partion to take 250 mb from it not from the OS partion and then when you delete the recovery partion they gonna merge with thease 250mb and from theare you folow the steps.
I needed to get this update for a validation tool before I start a new job and nothing was working until I did this.. thank you so much!! You saved my life! 😊😊
I'd been struggling with this update for months and worried it would damage my computer since it was running into a blue screen here and there with the effort of trying to install. Thank you for posting this, was finally able to get it to install today, really appreciate your help!
Awesome video and help! I greatly appreciate that you explain certain things as you go along (e.g., 2:26) as it helps us know what they are for and that you have accidently said something you didn't mean to. Awesome! Thanks!
Wow, this fixed the issue. You're right, why couldn't Microsoft incorporate a self-resizing partition through the update to ensure this worked appropriately, instead of hitting an error.
haha, I'm strong I resisted. (And I don't think it would have worked because my partitions are not in the right order for these instructions to work apparently. Anyway I think it's only relevant if you use bitlocker.)
The video helps greatly much better then just written instruction. Well made video easy to follow. It fixed the problem for me. Thank you for your time and effort, much appreciated.
I have no dobut that Microsoft did this on puropse, or really for the most part--they have no desire to fix the error. Afterall, Microsoft will stop supproing Windows 10 in another year, they want you to move on.
Cheers for the tutorial, I had this on my windows server, so it was a different update number, but the update serves the same purpose which means this fixed it for me. I can't believe this went through though, imagine how many people are gonna forever have that "Retry" button on their windows update, because they don't understand they could google how to fix it.
Instead of risking getting commands wrong I used AOMEI Partition Assistant and shrank the primary partition and then expanded the RE partition so that the RE partition had 750MB as recommended here. This worked first time and the KB5034441 installed successfully.
I tried this and it let me decrease the Primary partition size but wouldn't let me adjust the size of the recovery partition. There's some glitch with the recovery partition apparently because I can't adjust the size of it.
If you're recovery partition happens to not be the last partition, you cannot use this process. It is likely the last partition by default for most systems. I have systems that are not configured as such unfortunately. Then it becomes necessary to use utilities to shrink and move partitions to allow free space after the current recovery partition. It's possible to relocate the recovery partition as well to the end, but that's a little more involved.
@@fretizpaulrenaison5771They are going to provide a fix, so you may want to wait on that. However, you need a tool like MiniTool Partition Wizard (free version available) installed. Always good to have a backup of the drive if possible. Tools are not perfect. Using this tool, you shrink your main data partition (usually the largest one) by 250+MB. This will likely require a reboot. Depending on where the recovery partition is, use the same tool to move the partitions so that the unallocated free space is just after or just before the recovery partition. Then resize the recovery partition to include unallocated space. Then run Windows Update. This is what worked for me.
So if I have only 2 partitions for my disk and partition 2 is my recovery, I can still do it? I am having another issue with my computer at the moment and I am not sure if this is the issue or not. It would be nice if I could show you my screen and be in a call with you to see what you think for a few minutes.
@@ethansams3430 Sorry, I don't connect for security reasons. Your description likely means that you have an older non-UEFI setup, but I'm not as familiar with that since it's been quite a few years since I had a system without the EFI system partition and dealt with that. However, the concept is the same. If there is a large partition and then the smaller recovery partition (typically 500ish MB), then you need to shrink the first partition down by 500MB (at least 250MB), then move the recovery partition left to start at the beginning of that new free space after the larger partition, and finally resize the recovery partition to include the now trailing 500MB you created at the end. My only concern is if the partition tool (e.g. Minitool Partition Wizard) will or needs to change the MBR (Master Boot Record; pre UEFI boot record) to the new location after the move of the recovery partition; if needed. The tool should should warn about that or handle it. As always, a backup of the drive is a good idea. Partition |Recovery| Partition | |Recovery| Partition |Recovery| | Partition |Recovery | Size not scale, but this is what the tool should show as you perform each step; Start After freeing space (called Resize or Shrink in tools) After move of recovery After resize of recovery
What do you do if you are working with a system that had originally Windows 10 v1904 or prior? In these cases, the Recovery partition is the first partition on the disk, and the OS is the last partition on the disk. So, when you shrink the OS you have two non-contiguous sections of disk space and, without a partition editor, no way to combine them. Then there is the situation where you have an HP or Dell or Lenovo or any other machine that still has all the crapware that these companies load their computers down with, and naturally those partitions are after the OS partition, and the recovery partition is at the end of the drive, so once again, you are left with a need for a partition editor. And then there is the problem where the WINRE.WIM fil is so far out of date that the update can't merge the changes into the file. There are just three of the scenarios I've come across while trying to come up with a plan to fix almost 1000 of the 15K endpoints our company controls.
Thank you for this, the fact that this is still an issue is so annoying. I had been updating my graphics driver, cleaning up space etc thinking thats why it wasn't installing.
Thank you very much. I originally tried to do it by the Microsoft directions but got lost along the way but with those and your very helpful video I successfully managed it and got that stubborn update installed. Well done, I appreciate it.
Oh how I hate windows updates and its notorious errors. This is the las windows pc I will ever have. I'm so done with windows! Thanks for the video mate, very clear to follow.
250mb never worked for me, so changed to 750mb, which worked. Great video, thank you so much. As it is now updated, do we need to change anything back?
I followed the Microsoft article to the letter and was left with 2 primary partitions. While still in DISKPART, use the following commands to flag your new partition as the recovery volume, SWAP "PART 2" FOR THE NUMBER THAT APPLIES TO YOUR SETUP: DISKPART> select part 2 Partition 2 is now the selected partition. DISKPART> set id=27
Watch FIX IT...Part II ua-cam.com/video/ficOxwCf6Vc/v-deo.html then... Try running this powershell script "Run as Administrator". Follow the instructions in this article. learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
@@AnimeinSession i ended up downloading minitool partition wizard and then i merged that unallocated space with the windows recovery partition. Also i found out that updates just fail sometimes and you have to wait for a fix from microsoft as i have more than 2gb on re partitio and still got the error (now its fixed)
Hi, thanks for the video, but I had one small problem. I followed every step and almost everything worked as intented, except by the fact that when I checked reagentc /info, i noticed that the recovery partition had changed. Now, when I checked the partition list, I notice that the changes in space worked, but now they are all named Primary, and non of them says Recovery. Is there something wrong there? If there is, how can I change that?
I followed these instructions to the letter, but when I try to enable reagentc it tells me that "The Windows RE image was not found" and thus I can't re-enable it. Any tips?
Run the command reagentc /setreimage /path to set the location of the Windows RE image file. For example, if the file is in C:\Windows\System32\Recovery, run reagentc /setreimage /path C:\\Windows\\System32\\Recovery. This helped me enable it
@Gragorg Run the command reagentc /setreimage /path to set the location of the Windows RE image file. For example, if the file is in C:\Windows\System32\Recovery, run reagentc /setreimage /path C:\\Windows\\System32\\Recovery. Then do reagentc /enable
PC Health keeps saying I can upgrade to Win11. But I hit a road block with this update. Your instructions were great and the update went through. Windows keeps saying I can't upgrade, but at least I move one step closer. Thanks!
Add another "Thanks!" to the list @MrDabrudda ! You holding our hand with this video, as we proceeded with the steps textually outlined in the Microsoft link you posted....made the world of difference. Cheers and thanks again for having taken the time to do this and helping others. 😀
Hello! My Windows RE Status is already "Disabled", and I can't find the partition disk "Recovery" to delete it, I can't proceed with the steps, kindly advice dear ))
:\windows\system32>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Disabled Windows RE location: Boot Configuration Data (BCD) identifier: 915dabd9-5815-11eb-be69-045e3c2a8b5f Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. Same thing here
I did all you said in the video but didn't work for me! :/ I would love some help, if you can. I tried again to do it, but with copy/pasting from the Microsoft site, thinking i missed some 0 or letter in some command ^^ but when I typed: list disk -> Disk 1 Online size=465 GB free=250 MB and when i typed: list part -> Partition 1 Recovery 529 MB 1024 KB that is the same i had in the 1st place, meaning it didn´t get to be 250mb bigger and went on to become just free space. What can i do to fix this or what did i do wrong? thank you in advance :)
@@nantplays9740I had the same problem and couldn't figure out why the freed 250MB was not combining with the formatted Recovery partition (530MB). I ended up resolving this by freeing up 850MB instead of the 250MB. The new Windows RE partition installed on the 850MB and the update error was finally resolved. Although now under disk management there is 530MB of unallocated space that is unable to be added to the OS partition. If you have not already resolved the issue I hope this helped.
i get this after typing in shrink command, any help? Virtual Disk Service error: The specified shrink size is too big and will cause the volume to be smaller than the minimum volume size.
can't believe i had to manually do this to 3 MS operating systems, thanks for the video, your instructions were clear & I was able to follow with ease.
Another happy subscriber here in central Minnesota. VERY clear instructions, took me all of about 15 minutes and worked perfectly. THANK YOU for making this video!
i'd say ik stuff like optimizing and some troubleshoots but ig this is the part of windows i have bare knowledge of so anyone correct me if im wrong, i was forced to upgrade my laptop to windows 11 cause i thought of id now on get updates for 11 not that KB version for 10 but im also not sure if it fixed the WINDOWS RE @@boytoz
well i was forced to jus upgrade to windows 11 it fixed both since i think that update is for windows 10 so 11 means a whole different version. last year or the past two years or in short when 11 came out or any new that comes out ofc ppl would advise you to not upgrade yet since there's gon be bugs and problems but think abt it it's been out it should be fine now @@boytoz
i hope that helps and plus there's a very little increase of performance by having windows 11 you could only notice it if you know your pc so well and what's the max it can do on some situations
Wow i cant believe it i have been trying to fix this issue for weeks i was trying the usual enabling and disabling windows update services checking the disk health and checking for corrupted system files nothing worked then i heard about resizing the recovery partition i seen a video that was just way too long and had way to many unnecessary steps then i found this video straight to the point and very professional my system is now working and im so happy you really saved alot of stress i just dont understand why Microsoft make a default recovery partition so small and dont even have an option to change it i cant believe this actually fixed it thanks so much you earned a subscriber
Thanks MrDabrudda. Waited weeks for MS to fix this but your solution mostly worked Problems: 1. DiskManagement showed 2 Recovery partitions. So after checking around I removed the one that was not active 2. format quick fs=ntfs label=”Windows RE tools” FAILED. MS update still not working. After some checking I found the partition was not ntfs or labeled. I labelled it correctly but using Paragon Partition Manager but even that would not format it properly. Solution was to follow written instructions above re CHKDSK AND DISM Final reboot and all good :)
I was terrified to do this. WHEW! You are a model for effective "Windows How To..." videos. Thank you so much! This solved my issue. Step for MBR worked fine. MBR due to upgrades rather than clean install.
God bless. There may be people that couldn't get their problem fixed for one reason or another. But after carefully following your instructions the update finally went through. Thank you or your hard work.
Can't express my happiness !!!!! I was struggling so hard to install it even after following many instructions given by other youtubers. But you made it easy 👍 Wishes form INDIA
This was the fix I've been looking for. Tried other "fixes" first (several times even) but this was the actual fix that allowed the update to go through. Big thanks to the author of this video for a great solution with clear instructions. I will make only one note, and that is that there is a missing part in the video as you're entering the commands alongside this video. For some reason these lines disappear from his command window immediately following the shrink command, but they remained on my screen after running the command. DISKPART> shrink desired=250 minimum=250 DiskPart successfully shrunk the volume by: 250 MB Please watch the video carefully all the way through, and listen to his instructions, and be careful to type things exactly. Other than the fact that my hard disk and partition numbers had to be adjusted from the lines that he entered, and the missing lines I mentioned above, everything worked exactly the way it was showed. Again, listen carefully and pay attention to both the commands shown, and the explained instructions he gives verbally during the video. Good luck!
MAN! THANK YOU! Idk if my drivers wouldnt update because this wouldnt. But i did all your steps and messed something up the first time so i low key almost panicked but went back and followed them again and boom it worked. Got the update and the error to go away rebooted my pc and boom my drivers now had an update. Thank you so much haha
Cheers mate.. my drives were getting full and this update was causing too much grief. I tried following a microsoft forum but it was half greek to me. I was doing so much this morning trying to fix the issue based on microsoft advice short of going cmd prompt. When I finished the steps the update was still stagnant/ causing issue but I did a reboot and it took no problem. Really appreciate this video!
i thought it didnt work but i went back and looked at the video and saw that I forgot to do reagentc /enable and after I did that it worked, thank you very much for this tutorial. This has been a major problem for me for awhile.
Thanks for the video. This really helped me. It is unbelievable that these companies dare to say you will not own your tech, treat you like a garbage censor what you say while you as customer have to fix their broken products. Big thumbs up.
followed directions exactly as you did them, and it worked. thank you. now i don't see that stupid error message every time it tries to update windows.
Watch FIX IT...Part II ua-cam.com/video/ficOxwCf6Vc/v-deo.html then... Try running this powershell script "Run as Administrator". Follow the instructions in this article. learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
I switched from 11 to 10 thinking it was stable and this error happened. But you sir, were the ray of hope all 344254 people were seeking. Thank you!!!
Thank you for your step-by-step instructions. I found it easier to do the fix than reading the instructions. It worked and the download of the KB5034441 security update was seamless.
Wow thanks for this - when you first mentioned to shrink the Windows Primary partition by 250GB, I was like WHAT LOL I'm going to keep watching and whew glad you clarified it was actually 250MB shortly after, that sounds more reasonable for the overall relatively small Windows Recovery environment partition. and yes, this is ridiculous Microsoft didn't include an automatic way for the Windows Recovery partition to increase in size - considering it's only 250MB - hardly a concern on most systems even those 10+ years old by now. This worked! Thanks again
Hey man thanks very much, i was having this issue for almost 2 years. i was actually losing hope to update to windows 11, you are doing god's work man keep up with the content bro!
Thank you for the help!! I had to change my recovery partition as I came from a MBR partition and converted to GPT, which wouldn't let me expand my recovery partition any more because it wasnt contiguous (next to each other in the partition mapping) So I used disk manager and shrunk the OS partition 750 MB to then apply the new recovery partition to the new unallocated space. Yes, I lost out on 528 MB of space, which i could just reformat; but I have the update and can now update to Win 11 finally. Thanks again.
Note: S tells you to shrink the OS partition. It's a bad description. The real goal is to shrink ANY partition (out of however many you have) to release space. Many OEM OS partitions can't be shrunk, so their description will have no effect.
Watch FIX IT...Part II ua-cam.com/video/ficOxwCf6Vc/v-deo.html then... Try running this powershell script "Run as Administrator". Follow the instructions in this article. learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
Oh my god, it worked. I haven't commented on a window FIX video in so long. This one WORKED. Its been a while since the last time someone gave a solution that actually worked. Thank you soo much!
I followed almost every single step and it really worked! I've been issues with this update for so long and finally got rid of it! Pay attention to the drive AND VERY IMPORTANT TO THE PARTITION as I had two recovery partitions
Thank you so much! Even though I read this MS article I was too afraid to follow it as I don't really know which one to select. You made it really clear with explanation of what and why. Totally worked, my computer is not a brick 👍
You made it all so easy, I watched your UA-cam video, and then just now I fixed the problem. it's helped me to fix the update problem. Now no error. Windows Update works now. Thank you, Boss.
Thank you, your video helped me a lot. I've made several different attempts and found that there's no need to enlarge the partition. Just delete the WinRE partition and create it again and format it. That will fix the problem.
i did it and it worked. also, i went with 300mb instead of 250mb so my recovery was 508mb and now it was 808mb and the update installed perfectly. thanks a bunch.
Splendid! Apparently I was attempting to resize the wrong OS disk... Lesson learned. Knowledge gained. Appreciate it. Though I'm still pissed that I had to do windows job for them
After watching so many videos, on error xxx=80070643, yours was the only video that resolved the issue that Microsoft created on my laptop. Tnanks for the help !
This man here deserves a gracious thanks from the community as these simple instructions have solved my issue, a recurring problem I have faced for the last 2 months consistently and why windows can't come up with solutions per say for such as an update still remains unclear to this day, however thanks.
i followed the video, i thought it wouldnt work cuz i had the same lag. but after being patient enough, it turned out to be successful. Thank you so much, i appreciate it.
Watch FIX IT...Part II ua-cam.com/video/ficOxwCf6Vc/v-deo.html then... Try running this powershell script "Run as Administrator". Follow the instructions in this article. learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
@MrDabrudda I am speechless 😅 , so from what i understand the update required the recovery partition size to be 250 MB more and somehow a billion dollar company couldn't work around this issue while you provided a solution in few minutes, I've had this issue for months and its finally solved. Thank you brother, I appreciate it. 🙏👍
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac gpt attributes =0x8000000000000001 format quick fs=ntfs label="Windows RE tools" list vol
This is brilliant. Thank you so much. This fixed the issue for me, after I had spent hours this afternoon researching notes from Microsoft and trying to apply scripts that were supposed to fix the issue but didn't work on my ancient PC (or I was applying the intended remedies wrong). Your instructions were perfect, to the point, and I was able to execute all the steps.
Glad I found your vid. Made it so easy - after failing to succeed with MS's own description. Yours is the one and only reasonable description how to fix that s...
Works perfectly. Thanks for the help, mate! :-D Edit: I shrinked my Windows system partition with 500mb instead of 250mb to be on the save side. Resizing my Windows recovery partition from 500mb to 1000mb (1GB).
Many many thanks! I'm newish to PCs having jumped ship from Macs. So very good when doing these things for the first time to have someone talk you through. I'd found the link @ microsoft support which was great to have open to copy and pastes for some more complex commands but having you run through this on video was amazing. Couldn't have done it without you. All updated and super happy. D : )
Thanks it fixed the issue, I really hate how incompetent Microsoft is. Users shouldn't have to fix what mistakes they did, and its not easy steps either. Smallest mistake can delete your whole computer.
I still have it after that
And in a year we are more pestered from the money-mafia Microsoft, that made sure that Windows 11 DID NOT MEET THE MINIMUM OF REQUIREMENT.,.....so our Window 10 computers have to be scrapped, as no support anymore..... Seems like terror!! Why is Window 11 made to use Widows 10 on for instance Lenovo T 60 and 61 UNSUDEABLE - what about compensation. PS. why is this security (0x80070643) not installing, doesnt Microsoft know what they are doing!!! We pay for the program!!
Some media such as Windows Latest or Bleeping Computer are now reporting that Microsoft is aware of the problems and is working on fixing them. Redmond intends to provide further information "shortly". For the majority of those affected, I think it's a case of waiting and seeing what Redmond comes up with.@@nio7620
Win 7 was the best they could come up with. Visualy more better. Bring those developers back!
I was getting this issue on all my new windows 10 installs. This fixed it. For anyone thinking about attempting this fix, I would suggest opening the first link in the description so you can copy and paste commands.
NOTE: if you have MBR format, after you format, the id is lost and it converts back to PRIMARY. So you need to run this afterwards to get back to the same point he had.
sel disk
sel part
set id = 27
at the beginning , when i ran "reagentc / info" , the recovery partition was on part 3 and the primary was on part 2 . I followed everything he did except for the create id because i dont have a gpt format . when i was done i ran "reagentc / info" but it says that the recovery is on part 2 now . I still have 3 partitions and they all show as primary when i run "list part" . Do you have any idea about this ?
i tried setting the id for partition 3 , so now partition 3 looks like its the recovery one , but whenever i run reagentc /info , it still shows that partition 2 is the recovery.
@@ralphtawil8266 I followed eveything he said but I had to add those above steps after I formattedy partition
When in the video do you start the steps you added
@@raidensepulveda9204 I don't recall but it appears previously I stated after a specific step, see my sub comment above
Unbelievable that this made it through testing. I'm guessing it's going to impact smaller drive systems. Just had it on a laptop with ~180GB SSD
shocking ...and remember we have parents and grand parents dealing with these nonsense...
Huge thanks, all of the other tutorials did not work, completely uninstalled all my drivers and nothing but this worked!
This actually worked! Thank you! This error was so annoying. All the generic troubleshooting guides didnt work, like stopping update service, clearing temp files, chkdsk, system repair, ...
You made it all so easy! I was scared to do it just from the instructions without seeing it done. All is working now thanks to you! WONDERFUL!
You're welcome!
I havean issue there is 2 partition recovery
should i use the third party app to increase it or is there a way to find current one?
@@MrDabrudda
@@MrDabrudda still getting an error and i triple checked that everything?
That's weird... I followed the directions to a T and it worked first try.
My advice would be to just wait for the next update.
If it's not fixed by then, there will be enough people annoyed at Windows which will incentivize them to fix the dang thing.
I update my PC once a month and it's ALWAYS something. @@XhitmanXX103
@@MrDabrudda I made a mistake & redid the tutorial. but accidentally made recover partition 1240mb . Is that bad ?? ? & it did work though
Other option is to ignore this repeated error. MS may find a different solution for this update that does not require so much recovery partition. Also, this change only matter if you are using BitLocker to encrypt your drive(s). If not, this update is not required especially for Windows 10 Home users that can't activate BitLocker; Pro and above versions only. Same code base, however, so they are pushing this change to everyone in case you upgrade your license to Pro or other in the future. Dumb, but it's a just in case CYA move by MS.
And updated videos state MS will provide a different fix for this. Unclear what that means.
Do you think it could be caused by malware? I had my PC infected 10 days ago and day after i got infected i reinstalled the windows and then i thought i got rid of it. My PC no longer finds any threats and i think it's already fine, however this update 10 days later somehow makes me worry if some part of the virus has survived or not.. do you think it could be caused by this?
@@waidi3242 unlikely related in any way. This update issue is MS creating a default recovery partition size (512MB) many many years ago and it now not being large enough to accommodate update requirements. This is not related to malware. Yes. there is a BitLocker vulnerability. Are you running encrypted drives and BitLocker? If not, and this would be true for Home versions (no support for BitLocker), then this driver was not active and the vulnerability also not active. Nothing is impossible, just very unlikely.
@@Bare_Essence Alright then thanks :D I already followed this tutorial and got it fixed and nope, i don't use Bitlocker. So it's all fine i just got paranoid :D (i lately am very paranoid about it..)
If the reagentc.exe and the winre.win disappeared it could certain be malware. The reagentc.exe is a protected by the Trusted Installer process to prevent deletion. A process running at or above Trusted Installer access deleted the exe.
HEY THANK YOU SO MUCH! I am a certified PC Technician and have been in the industry for over 25 years. I was loosing my mind over this and your video was only solution i could find. ODD THING WAS MY RECOVERY part was larger than yours was at the end from the start. i still increased 250mb and it worked on the first try. I was a bit nervous, I never disabled recovery parts in CMD until today. YOUR A LIFE SAVER, I WILL LIKE and Subscribe. HAPPY YEAR
***How to fix***
1) Open a CMD window and "Run As Administrator"
2) Type DISM.EXE /Online /Cleanup-image /Restorehealth
3) After the DISM.exe command finishes then type
4) SFC /SCANNOW
5) After the SFC command finishes Reboot your computer
6) Run Windows Updates and ensure you are running the latest version of Windows 10 22H2
7) Install and scan your computer with a reputable anti-virus/security suite
Good Day. I did not Follow it well? if you deleted the part.4 what will happen? and iam Confused?
If you are getting an error of not being able to shrink the partition, you are probably selecting the wrong partition. I wasn't paying close enough attention and I selected the recovery partition (so for him it was partition 4) before trying the shrink command, but it wouldn't let me. But we are trying to make the recovery partition larger not smaller. So we are selecting a different partition to shrink first so that there is enough space to make the recovery partition larger. I had read an article about this error and thought that for some reason Microsoft needed the recovery partition to be smaller, and I was very confused because that makes no sense. And of course it made no sense, because that wasn't what they wanted you to do haha. You need a larger recovery partition for the update to work.
Everything was going smooth up until the very end, I'm stuck, I can't enable my re agent with the /enable command. I'm met with "REAGENTC.EXE: The Windows RE image was not found. " any ideas? :(
Same
same here, please provide a fix if you managed to fix it.
@@Joe-ew4qx same here, please provide a fix if you managed to fix it.
same
same here
Thanks, this helped a lot! For anyone else still having trouble, the exact instructions in this video / link didn't work for me at first, so I made a larger partition by using 750 instead of 250 and following all of the other instructions exactly as-is. That fixed everything and I'm up to date now.
thank that worked
so instead of the shrink desired=250 minimum=250 you do shrink desired=750 minimum=750?
@@rahmsalama yea thats what i did
@@aar5n thank you, i’ll try it again
@@rahmsalama hopefully it works for u
Been wrestling with this bastard update for over a week. I followed your tutorial to the letter and it worked like a charm first time. Everything happened as it did in your example - just perfect. 👍
I now have no pending updates.
Thanks so much for your help.
Kindest regards, Andy, London UK. 😊
I'm not gonna fix microsofts issues, let them do it themselves at the next patch round.
Do you fix the problem
Nah for real😂
I keep getting this message when I go to shrink the partition of the primary:
"Virtual Disk Service error:
The specified shrink size is too big and will cause the volume to be
smaller than the minimum volume size."
I am having the same problem now. Did you find a fix?
@@CaioTheFrog same for me, any advice on this issue @MrDabrudda ?
this was a huge help! followed everystep and had to spell out all the long codes but it was worth it. very easy steps and well spoken directions. thank you for the help man!
Well... That was scary, at some points I thought I did something wrong but I just slowly followed what you did and the problem is solved. Thank you for all your help! :)
Glad it helped!
@@MrDabrudda i am seeing multiple primery which one to choose
Also......if you are going to increase the size of the Recovery Partition (and shrink the OS part), why only do a 250mb increase. It's not like you are going to miss even a 1 GB less disk space on the OS part, and if you increase more than the required 250mb, it may prevent MS screw up and needing more space in the future....Thoughts?
Never underestimate Microsofts ability to screw up. They probably have an error lined up and waiting in case the partition is TOO BIG!!!
@@mainepants haha
Appears to only work if the partitions are in the right order. When Disk Management shows recovery partition at end all is good but when recovery partition is tat the start the recovery partition does not expand in to the newly created space.
I am guessing there is a way to do this by stealing more drive space from the primary and then somehow creating the new recovery in the new empty space but I am not sure of the commands and sequence?
Having the same issue, Recovery is on part 1 with exact 529MB as before and now I only have additional 250MB of unallocated space :D
@@raytorflurch9155 If it’s an issue on a new computer/for new images, I’ve fixed it by creating an entirely new image using a .wim file (using DISM in Windows PE) and modifying the “apply-image” batch file to create a partition with 1000MB instead of 500, so that it automatically is able to install the update after creating the partitions at the very beginning of the process.
Alternatively, if you’re just looking for a quick fix for one computer, Microsoft has released a powershell script that you can use to manually apply what the security update fixes. I’ll find the link and send it here so you can use it if that’s what you need.
@@stefandothill Hey I get that same problem. Even though I have a new big partition now, when I type "reagentc /enable" I get "REAGENTC.EXE: The Windows RE image was not found." What is the fix that you mentioned that you did?
same issue@@AndersSundstedt
@@raytorflurch9155 You need to use the partion that's it right to next to the recovery partion to take 250 mb from it not from the OS partion and then when you delete the recovery partion they gonna merge with thease 250mb and from theare you folow the steps.
I needed to get this update for a validation tool before I start a new job and nothing was working until I did this.. thank you so much!! You saved my life! 😊😊
I'd been struggling with this update for months and worried it would damage my computer since it was running into a blue screen here and there with the effort of trying to install. Thank you for posting this, was finally able to get it to install today, really appreciate your help!
Thanks for the tutorial! Nice and clear and the links were so helpful in the description, all updated now!
You're welcome!
Awesome video and help! I greatly appreciate that you explain certain things as you go along (e.g., 2:26) as it helps us know what they are for and that you have accidently said something you didn't mean to. Awesome! Thanks!
Awesome clear procedural instruction - thank-you for sharing! Should maybe warn this is not for beginners. Worked great!
Wow, this fixed the issue. You're right, why couldn't Microsoft incorporate a self-resizing partition through the update to ensure this worked appropriately, instead of hitting an error.
Thank you, kept retrying and getting a failed to install error, did all the steps you outlined, and it finally successfully installed.
0 fucking chance I'm doing this and risking making a mistake to install a windows update
Edit: I'm weak I did it
haha, I'm strong I resisted. (And I don't think it would have worked because my partitions are not in the right order for these instructions to work apparently. Anyway I think it's only relevant if you use bitlocker.)
The video helps greatly much better then just written instruction. Well made video easy to follow. It fixed the problem for me. Thank you for your time and effort, much appreciated.
You're welcome!
I have no dobut that Microsoft did this on puropse, or really for the most part--they have no desire to fix the error. Afterall, Microsoft will stop supproing Windows 10 in another year, they want you to move on.
Cheers for the tutorial, I had this on my windows server, so it was a different update number, but the update serves the same purpose which means this fixed it for me. I can't believe this went through though, imagine how many people are gonna forever have that "Retry" button on their windows update, because they don't understand they could google how to fix it.
Instead of risking getting commands wrong I used AOMEI Partition Assistant and shrank the primary partition and then expanded the RE partition so that the RE partition had 750MB as recommended here. This worked first time and the KB5034441 installed successfully.
I tried this and it let me decrease the Primary partition size but wouldn't let me adjust the size of the recovery partition. There's some glitch with the recovery partition apparently because I can't adjust the size of it.
If you're recovery partition happens to not be the last partition, you cannot use this process. It is likely the last partition by default for most systems. I have systems that are not configured as such unfortunately. Then it becomes necessary to use utilities to shrink and move partitions to allow free space after the current recovery partition. It's possible to relocate the recovery partition as well to the end, but that's a little more involved.
same issue here, i got 250MB free space, the RE part remain the same
And how can I do that? Thx in adv.
@@fretizpaulrenaison5771They are going to provide a fix, so you may want to wait on that. However, you need a tool like MiniTool Partition Wizard (free version available) installed. Always good to have a backup of the drive if possible. Tools are not perfect. Using this tool, you shrink your main data partition (usually the largest one) by 250+MB. This will likely require a reboot. Depending on where the recovery partition is, use the same tool to move the partitions so that the unallocated free space is just after or just before the recovery partition. Then resize the recovery partition to include unallocated space. Then run Windows Update. This is what worked for me.
So if I have only 2 partitions for my disk and partition 2 is my recovery, I can still do it? I am having another issue with my computer at the moment and I am not sure if this is the issue or not. It would be nice if I could show you my screen and be in a call with you to see what you think for a few minutes.
@@ethansams3430 Sorry, I don't connect for security reasons. Your description likely means that you have an older non-UEFI setup, but I'm not as familiar with that since it's been quite a few years since I had a system without the EFI system partition and dealt with that. However, the concept is the same. If there is a large partition and then the smaller recovery partition (typically 500ish MB), then you need to shrink the first partition down by 500MB (at least 250MB), then move the recovery partition left to start at the beginning of that new free space after the larger partition, and finally resize the recovery partition to include the now trailing 500MB you created at the end. My only concern is if the partition tool (e.g. Minitool Partition Wizard) will or needs to change the MBR (Master Boot Record; pre UEFI boot record) to the new location after the move of the recovery partition; if needed. The tool should should warn about that or handle it. As always, a backup of the drive is a good idea.
Partition |Recovery|
Partition | |Recovery|
Partition |Recovery| |
Partition |Recovery |
Size not scale, but this is what the tool should show as you perform each step; Start
After freeing space (called Resize or Shrink in tools)
After move of recovery
After resize of recovery
Not working to my pc fail install the update KB5034441.
Error 0x80070643 😢
Same here
Same :( not working
same
on another note it took longer to tell me know, getting somewheere
🙃
Same😢
What do you do if you are working with a system that had originally Windows 10 v1904 or prior? In these cases, the Recovery partition is the first partition on the disk, and the OS is the last partition on the disk. So, when you shrink the OS you have two non-contiguous sections of disk space and, without a partition editor, no way to combine them. Then there is the situation where you have an HP or Dell or Lenovo or any other machine that still has all the crapware that these companies load their computers down with, and naturally those partitions are after the OS partition, and the recovery partition is at the end of the drive, so once again, you are left with a need for a partition editor. And then there is the problem where the WINRE.WIM fil is so far out of date that the update can't merge the changes into the file. There are just three of the scenarios I've come across while trying to come up with a plan to fix almost 1000 of the 15K endpoints our company controls.
Thank you for this, the fact that this is still an issue is so annoying. I had been updating my graphics driver, cleaning up space etc thinking thats why it wasn't installing.
Thank you very much. I originally tried to do it by the Microsoft directions but got lost along the way but with those and your very helpful video I successfully managed it and got that stubborn update installed. Well done, I appreciate it.
Oh how I hate windows updates and its notorious errors. This is the las windows pc I will ever have. I'm so done with windows! Thanks for the video mate, very clear to follow.
#LinuxMint
microsoft the worst company in the World !!!
sometimes hahah
and sometimes good
then Go and Buy Apple If you afford 😂
L Microsoft
Microdic
This is the marketing strategy to upgrade windows 11
250mb never worked for me, so changed to 750mb, which worked. Great video, thank you so much. As it is now updated, do we need to change anything back?
did you change directly to 750mb or first to 250 and then 750?
I followed the Microsoft article to the letter and was left with 2 primary partitions. While still in DISKPART, use the following commands to flag your new partition as the recovery volume, SWAP "PART 2" FOR THE NUMBER THAT APPLIES TO YOUR SETUP:
DISKPART> select part 2
Partition 2 is now the selected partition.
DISKPART> set id=27
Watch FIX IT...Part II
ua-cam.com/video/ficOxwCf6Vc/v-deo.html
then...
Try running this powershell script "Run as Administrator". Follow the instructions in this article.
learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
Worked! I followed the steps on 03.05.2024 and Windows updated as it should be. Thanks a lot!
it didnt work for me strangely.
i tried twice and now i got 500 mb unallocated space. why doesnt it transfer to the RE volume?
same boat did you find a solution?
no@@miecraftandmoregames
I have this same problem!!!
@@AnimeinSession i ended up downloading minitool partition wizard and then i merged that unallocated space with the windows recovery partition. Also i found out that updates just fail sometimes and you have to wait for a fix from microsoft as i have more than 2gb on re partitio and still got the error (now its fixed)
Hi, thanks for the video, but I had one small problem. I followed every step and almost everything worked as intented, except by the fact that when I checked reagentc /info, i noticed that the recovery partition had changed. Now, when I checked the partition list, I notice that the changes in space worked, but now they are all named Primary, and non of them says Recovery. Is there something wrong there? If there is, how can I change that?
I followed these instructions to the letter, but when I try to enable reagentc it tells me that "The Windows RE image was not found" and thus I can't re-enable it. Any tips?
I have the same problem
Run the command reagentc /setreimage /path to set the location of the Windows RE image file.
For example, if the file is in C:\Windows\System32\Recovery, run reagentc /setreimage /path C:\\Windows\\System32\\Recovery.
This helped me enable it
Same Issue. I wish I didn't touch it
@Gragorg Run the command reagentc /setreimage /path to set the location of the Windows RE image file.
For example, if the file is in C:\Windows\System32\Recovery, run reagentc /setreimage /path C:\\Windows\\System32\\Recovery.
Then do reagentc /enable
Watch FIX IT...Part II
ua-cam.com/video/ficOxwCf6Vc/v-deo.html
PC Health keeps saying I can upgrade to Win11. But I hit a road block with this update. Your instructions were great and the update went through. Windows keeps saying I can't upgrade, but at least I move one step closer. Thanks!
Add another "Thanks!" to the list @MrDabrudda !
You holding our hand with this video, as we proceeded with the steps textually outlined in the Microsoft link you posted....made the world of difference.
Cheers and thanks again for having taken the time to do this and helping others.
😀
Hello! My Windows RE Status is already "Disabled", and I can't find the partition disk "Recovery" to delete it, I can't proceed with the steps, kindly advice dear ))
:\windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 915dabd9-5815-11eb-be69-045e3c2a8b5f
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
Same thing here
@@kingp43 Try putting in: reagentc /enable
Then start the process from the beginning.
I did all you said in the video but didn't work for me! :/ I would love some help, if you can. I tried again to do it, but with copy/pasting from the Microsoft site, thinking i missed some 0 or letter in some command ^^ but when I typed: list disk -> Disk 1 Online size=465 GB free=250 MB and when i typed: list part -> Partition 1 Recovery 529 MB 1024 KB that is the same i had in the 1st place, meaning it didn´t get to be 250mb bigger and went on to become just free space. What can i do to fix this or what did i do wrong? thank you in advance :)
help!🥲
@@nantplays9740I had the same problem and couldn't figure out why the freed 250MB was not combining with the formatted Recovery partition (530MB).
I ended up resolving this by freeing up 850MB instead of the 250MB. The new Windows RE partition installed on the 850MB and the update error was finally resolved.
Although now under disk management there is 530MB of unallocated space that is unable to be added to the OS partition. If you have not already resolved the issue I hope this helped.
had the same issue I even tried third party parition software still couldn't merge the two together. unallocated space together
@@kickrocks5780 Im sorry for the late reply! So many things irl i forgot. Thank you for the info! I´ll try it.🙂 ---- update: WORKED!!!! THANK YOU!! 💪😁
i get this after typing in shrink command, any help?
Virtual Disk Service error:
The specified shrink size is too big and will cause the volume to be
smaller than the minimum volume size.
I get this same error message :/
Same problem and of course no workaround has been published....
its ur disk partition style, you might be MBR not GPT so do the other one
can't believe i had to manually do this to 3 MS operating systems, thanks for the video, your instructions were clear & I was able to follow with ease.
Another happy subscriber here in central Minnesota. VERY clear instructions, took me all of about 15 minutes and worked perfectly. THANK YOU for making this video!
it says the Windows RE image was not found? help
Same😢
i'd say ik stuff like optimizing and some troubleshoots but ig this is the part of windows i have bare knowledge of so anyone correct me if im wrong, i was forced to upgrade my laptop to windows 11 cause i thought of id now on get updates for 11 not that KB version for 10 but im also not sure if it fixed the WINDOWS RE @@boytoz
well i was forced to jus upgrade to windows 11 it fixed both since i think that update is for windows 10 so 11 means a whole different version. last year or the past two years or in short when 11 came out or any new that comes out ofc ppl would advise you to not upgrade yet since there's gon be bugs and problems but think abt it it's been out it should be fine now @@boytoz
i hope that helps and plus there's a very little increase of performance by having windows 11 you could only notice it if you know your pc so well and what's the max it can do on some situations
Watch FIX IT...Part II
ua-cam.com/video/ficOxwCf6Vc/v-deo.html
Wow i cant believe it i have been trying to fix this issue for weeks i was trying the usual enabling and disabling windows update services checking the disk health and checking for corrupted system files nothing worked then i heard about resizing the recovery partition i seen a video that was just way too long and had way to many unnecessary steps then i found this video straight to the point and very professional my system is now working and im so happy you really saved alot of stress i just dont understand why Microsoft make a default recovery partition so small and dont even have an option to change it i cant believe this actually fixed it thanks so much you earned a subscriber
Thanks MrDabrudda. Waited weeks for MS to fix this but your solution mostly worked
Problems:
1. DiskManagement showed 2 Recovery partitions. So after checking around I removed the one that was not active
2. format quick fs=ntfs label=”Windows RE tools” FAILED. MS update still not working. After some checking I found the partition was not ntfs or labeled. I labelled it correctly but using Paragon Partition Manager but even that would not format it properly. Solution was to follow written instructions above re CHKDSK AND DISM
Final reboot and all good :)
followed exactly and it was fixed after all these months of not installing. Thank you!
I was terrified to do this. WHEW! You are a model for effective "Windows How To..." videos. Thank you so much! This solved my issue. Step for MBR worked fine. MBR due to upgrades rather than clean install.
God bless. There may be people that couldn't get their problem fixed for one reason or another. But after carefully following your instructions the update finally went through.
Thank you or your hard work.
Can't express my happiness !!!!!
I was struggling so hard to install it even after following many instructions given by other youtubers. But you made it easy 👍
Wishes form INDIA
I was just about to reimage, thanks for making this. It amazes me that this kinda stuff can still happen.
This was the fix I've been looking for. Tried other "fixes" first (several times even) but this was the actual fix that allowed the update to go through. Big thanks to the author of this video for a great solution with clear instructions. I will make only one note, and that is that there is a missing part in the video as you're entering the commands alongside this video. For some reason these lines disappear from his command window immediately following the shrink command, but they remained on my screen after running the command.
DISKPART> shrink desired=250 minimum=250
DiskPart successfully shrunk the volume by: 250 MB
Please watch the video carefully all the way through, and listen to his instructions, and be careful to type things exactly.
Other than the fact that my hard disk and partition numbers had to be adjusted from the lines that he entered, and the missing lines I mentioned above, everything worked exactly the way it was showed. Again, listen carefully and pay attention to both the commands shown, and the explained instructions he gives verbally during the video. Good luck!
MAN! THANK YOU! Idk if my drivers wouldnt update because this wouldnt. But i did all your steps and messed something up the first time so i low key almost panicked but went back and followed them again and boom it worked. Got the update and the error to go away rebooted my pc and boom my drivers now had an update. Thank you so much haha
Thanks a ton! 5 months after this update was made i was still fighting it, and only you and your video helped me to fix it, thank you so much!
Cheers mate.. my drives were getting full and this update was causing too much grief. I tried following a microsoft forum but it was half greek to me. I was doing so much this morning trying to fix the issue based on microsoft advice short of going cmd prompt. When I finished the steps the update was still stagnant/ causing issue but I did a reboot and it took no problem. Really appreciate this video!
i thought it didnt work but i went back and looked at the video and saw that I forgot to do reagentc /enable and after I did that it worked, thank you very much for this tutorial. This has been a major problem for me for awhile.
Thanks for the video. This really helped me. It is unbelievable that these companies dare to say you will not own your tech, treat you like a garbage censor what you say while you as customer have to fix their broken products. Big thumbs up.
followed directions exactly as you did them, and it worked. thank you. now i don't see that stupid error message every time it tries to update windows.
Error: The arguments specified for this command are not valid.
For more information on the command type: HELP CREATE PARTITION PRIMARY
Watch FIX IT...Part II
ua-cam.com/video/ficOxwCf6Vc/v-deo.html
then...
Try running this powershell script "Run as Administrator". Follow the instructions in this article.
learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
I switched from 11 to 10 thinking it was stable and this error happened. But you sir, were the ray of hope all 344254 people were seeking. Thank you!!!
I followed your instructions to the letter, and it worked perfectly.
thank you so much for pointing out how to know the disk partition style, other tutorials dont point it out
Thank you for your step-by-step instructions. I found it easier to do the fix than reading the instructions. It worked and the download of the KB5034441 security update was seamless.
Worked perfectly for me. Mine was MBR but had no asterisk. Had to use the id=27 method. Thank you MrDabrudda!
Wow thanks for this - when you first mentioned to shrink the Windows Primary partition by 250GB, I was like WHAT LOL I'm going to keep watching and whew glad you clarified it was actually 250MB shortly after, that sounds more reasonable for the overall relatively small Windows Recovery environment partition.
and yes, this is ridiculous Microsoft didn't include an automatic way for the Windows Recovery partition to increase in size - considering it's only 250MB - hardly a concern on most systems even those 10+ years old by now.
This worked! Thanks again
Hey man thanks very much, i was having this issue for almost 2 years. i was actually losing hope to update to windows 11, you are doing god's work man keep up with the content bro!
Thank you, that worked a treat. It's just so annoying as I now have to do this to around 7 PCs around the house!!
Thank you for the help!! I had to change my recovery partition as I came from a MBR partition and converted to GPT, which wouldn't let me expand my recovery partition any more because it wasnt contiguous (next to each other in the partition mapping) So I used disk manager and shrunk the OS partition 750 MB to then apply the new recovery partition to the new unallocated space. Yes, I lost out on 528 MB of space, which i could just reformat; but I have the update and can now update to Win 11 finally. Thanks again.
Note: S tells you to shrink the OS partition. It's a bad description. The real goal is to shrink ANY partition (out of however many you have) to release space. Many OEM OS partitions can't be shrunk, so their description will have no effect.
Watch FIX IT...Part II
ua-cam.com/video/ficOxwCf6Vc/v-deo.html
then...
Try running this powershell script "Run as Administrator". Follow the instructions in this article.
learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
Oh my god, it worked. I haven't commented on a window FIX video in so long. This one WORKED. Its been a while since the last time someone gave a solution that actually worked. Thank you soo much!
I followed almost every single step and it really worked! I've been issues with this update for so long and finally got rid of it!
Pay attention to the drive AND VERY IMPORTANT TO THE PARTITION as I had two recovery partitions
Thanks for the easy to follow instructions....some software developer(s) at MSFT really screwed up on this patch.
Thank you so much! Even though I read this MS article I was too afraid to follow it as I don't really know which one to select. You made it really clear with explanation of what and why. Totally worked, my computer is not a brick 👍
You made it all so easy, I watched your UA-cam video, and then just now I fixed the problem. it's helped me to fix the update problem. Now no error. Windows Update works now. Thank you, Boss.
Thanks! A huge help! Especially explaining what each step is doing as I have multiple harddrives so I needed to select different disks and partitions!
Thank you, your video helped me a lot. I've made several different attempts and found that there's no need to enlarge the partition. Just delete the WinRE partition and create it again and format it. That will fix the problem.
i did it and it worked. also, i went with 300mb instead of 250mb so my recovery was 508mb and now it was 808mb and the update installed perfectly. thanks a bunch.
I have tried everything so far and watched so many videos , i am so glad i bumped into your video, IT IS FINALLY FIXED OMG THANKS
Splendid! Apparently I was attempting to resize the wrong OS disk... Lesson learned. Knowledge gained. Appreciate it.
Though I'm still pissed that I had to do windows job for them
After watching so many videos, on error xxx=80070643, yours was the only video that resolved the issue that Microsoft created on my laptop. Tnanks for the help !
This man here deserves a gracious thanks from the community as these simple instructions have solved my issue, a recurring problem I have faced for the last 2 months consistently and why windows can't come up with solutions per say for such as an update still remains unclear to this day, however thanks.
i followed the video, i thought it wouldnt work cuz i had the same lag. but after being patient enough, it turned out to be successful. Thank you so much, i appreciate it.
Watch FIX IT...Part II
ua-cam.com/video/ficOxwCf6Vc/v-deo.html
then...
Try running this powershell script "Run as Administrator". Follow the instructions in this article.
learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11#extend-the-windows-re-partition
@MrDabrudda I am speechless 😅 , so from what i understand the update required the recovery partition size to be 250 MB more and somehow a billion dollar company couldn't work around this issue while you provided a solution in few minutes, I've had this issue for months and its finally solved. Thank you brother, I appreciate it. 🙏👍
Thank you. Increasing the Recovery Partition size worked for me too.
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes =0x8000000000000001
format quick fs=ntfs label="Windows RE tools"
list vol
Video very much appreciated! Have had this update error bugging me for months.
didnt work for me. thanks for the video though. the Microsoft instructions confused me and i appreciated a guide to follow along with
This is brilliant. Thank you so much. This fixed the issue for me, after I had spent hours this afternoon researching notes from Microsoft and trying to apply scripts that were supposed to fix the issue but didn't work on my ancient PC (or I was applying the intended remedies wrong). Your instructions were perfect, to the point, and I was able to execute all the steps.
Glad I found your vid. Made it so easy - after failing to succeed with MS's own description. Yours is the one and only reasonable description how to fix that s...
Works perfectly. Thanks for the help, mate! :-D
Edit:
I shrinked my Windows system partition with 500mb instead of 250mb to be on the save side. Resizing my Windows recovery partition from 500mb to 1000mb (1GB).
Many many thanks! I'm newish to PCs having jumped ship from Macs. So very good when doing these things for the first time to have someone talk you through. I'd found the link @ microsoft support which was great to have open to copy and pastes for some more complex commands but having you run through this on video was amazing. Couldn't have done it without you. All updated and super happy. D : )
Thank you so much! I've been struggling with this on a new laptop for 2 days now. Your tutorial was concise and fast to understand.
Worked perfectly, thanks very much. I had 3 recovery partitions for some reason but I just actioned it on the 1st one (Disk0, partition 4)