I've gotten that error, too. I'm not gonna bother trying to increase the recovery partition, because I don't want to risk breaking my computer. Microsoft should've known better than to release an update that can't be installed for a lot of users. Hopefully, they'll pull this update ASAP and replace it with a new version that fixes the error. Edit: Well, I found out earlier that Microsoft will not fix this issue after all, so I ended up doing what I didn't want to do in the first place with help from a video from another RUclipsr (Julia's Tech Spot) to ensure I do it correctly. Thanks to that video, I was able to properly adjust the C drive size and increase the size of my recovery partition to get the update to finally install. I hate that it has led to this outcome. They should've pulled the update instead.
@@lukasbruderlin2723 Its even worse and super gross they gave out this info!! People on REDDIT had to spread the info that this will break pcs and laptops that arent good enough to enlargen the recovery partition! If someone older googled it and gets that article first and follows the instructions, they'd have their computer destroyed. This feels like a disgusting way to handle this because in the end they win! They get you to buy a new computer and most likely windows 11 to get past it...
I did that it worked, but now I am having the error again not to mention I had issues is there a way to undo the increase on recovery partition I did and is there a fix for this error?
Actually, this update is not that important. It is important if you use bitlocker, which would impact business users most likely running Pro. Also, most users do not dork with the recovery partition, it is set by Microsoft, or possibly an OEM/Sysadmin depending. So, Microsoft should know how big that partition is and they should have known it was going to cause widespread failure. Additionally, this is a security patch for a business that should be pushed out by their sysadmins and not included via the internet, especially knowing the failures it will cause. Finally, resizing a partition is not a simple thing. I am shocked Microsoft would think that it is given there are restrictions based on data storage in the other partitions. Why on earth they didn't create a temporary folder in the system partition and swap between the two is beyond me since I'm assuming the partition size issue likely revolves around the recovery files being moved and replaced. For heaven's sake, every Windows computer has a C drive/Primary partition. There is nothing stopping the developers from using a temp space on that drive, and oh, I don't know, even to a disk space check before running and if there isn't space failing the update with the message to free up space. Speaking as a retired software developer. The lack of error handling by the current generation would have resulted in a LOT of firings back in the 90s and 2000s. Oh, and I'm a Microsoft alumni from the 90s. I can't understand how the company has fallen so far in its quality. They should be embarassed.
Good to know about that thank you. Interestingly I have Win 10 Home, so it does not have bitlocker so the part that this update is supposed to fix is pointless.
Since 1982 I have an incurable fast growing Allergy against anything Micro Soft I still use Win XP and Win 7 without any problems ever and am immune to the para noikkers
whats sad is microsoft doesn't realise they are asking millions of novice users to try an tinker with critical parts of th OS. That doesn't sound like a good idea to me. They probably said to themselves oh well screw them they are the ones that refused to upgrade to windows 11.
Sorry but I am down voting every video that shows how to fix because this is 2024 and Microsoft knew they shouldn't have rushed the update, and to expect a very large amount of people who don't know much about computers, and software to mess with anything for windows recovery, let alone the Command prompt is the stupidest thing any company can do. You think the Nurses, Doctors, Elderly, and others are not going to damage there computer or worse screw someone else files? This is Microsoft's screw up, and they should be the ones to fix this.
I totally agree. This update has been failing on my rig ever since they put it out. Every once in a while, I will retry it, and it still fails. I know how to resize a partition, but I refuse to do it because this is Microsoft's debacle - they are allegedly the experts so they should be the ones to fix it. There are a lot of folks out there who are not tech savvy enough to be messing with that type of stuff, and Microsoft should know this. If they are not going to fix it right away, they need to take it out of the Update Queue until it is fixed.
thank you so much for this! I thought I was going crazy trying all these other "hacks" I found online forcing me to download and install different software to try and fix the problem. Unfortunately I don't feel like manually changing the disk partition so I'll just wait and hopefully a new update will be released. This was immensely useful though and really eased my irrational thoughts.
Ignore ignore ignore. This update is going to be abolished for an upgraded update. Like all updates in the past that had issues. Either Microsoft sent a removal tool for the update if it installed successfully in some devices and then the install for the upgraded or different update became available. Do not mess with your partitions or you will do more harm or crash your computer. Don't force install or your drivers may act up and fail if they're not up to snuff.
Thanks for this. I encountered this error myself a few hours ago. I found that disabling and then reenabling the recovery environment fixed it. Though, to be clear, I had to do this a few times, with reboots in between for it to stick. The part about there not being enough space in the recovery partition I found was a red herring, as there was plenty of space on that partition in my case. It may well be the same for others.
@@stekl9wka Start an elevated command prompt and type in "reagentc.exe /disable." Without the quotation marks and then press enter. To reenable Windows RE, type "reagentc.exe /enable," and then press enter. It may or may not work for you to do this as I did a few times (rebooting in between), but worth a shot. You can check if it's properly enabled again by typing, "reagentc /info."
Don't bother even continuously trying to download KB5034441. It's been overridden by the update 22H2 KB5034736. This download installed fine and restarted my computer. I still get the promt to download the former and one still gets the error. A new removal tool also was installed. You may still get the prompt to download the former. Don't do it and don't mess with the partitions. Nothing wrong with the computer. Eventually windows 10 will be no more anyways
Great info on recovery size being to small. Went into Mini Tool partition Wizzard. Expanded recovery partition.Took about 2 minutes for process.Did a restart and went to Windows Update clicked on update. Process to a few minutes but worked just fine. Thanks for your great info.
Love your background!! That's the Albuquerque international balloon fiesta! Behind the balloons is the Sandia Mountains and below the balloons is the Rio Grande.
yeah, windows default recovery partition is 500mb... which is where it fails. IMHO most people who would run with defaults aren't going to be "comfortable" trying to fix it.
I resized that partition from 500 to 750 MB and its okej now, but its crazy how Microsoft propose that every PC user know how to make it even with that instructions, no everyone its PC IT. What they think????
A frequent cause of failure is that not all hard disks have a recovery partition. In that situation a failure to install is actually normal. You cannot update what does not exist. So it fails.
Typical Microsoft update, no real testing and just throw it out there to the masses. I'm tired of being an unpaid beta tester (actually alpha tester, since they don't test anything). Everyone needs to take control of Microsoft updates on their machines, and I highly recommend delaying all updates for at least a week to allow the mistakes to show up and be fixed before allowing them onto your machine. There are several videos and articles available that will tell you how to set this up. Personally I've turned off all so-called feature updates, and delayed all other updates for a week. I sure hope someone creates a top notch operating system for the masses soon; I can't see Microsoft getting any better.
When that update failed on my laptop, my desktop and my church's computer, I set all of them to delay updates for two weeks to give programmers time to get it right.
They did a terrible, terrible job this time. On one machine it even tried to install Windows 11 disregarding group policies. Something very chaotic is going on at Microsoft.
I resized my partition... But I didn't "mess with it." I followed the instructions and the update installed great. It was really easy and took about 15 mins.
thank you for sharing this. I have this issue on my new system when I tried to update yesterday. I had never experienced an issue with Win Update before so this was something that puzzled me and I randomly came across your video today so I am glad I found an explanation for the problem.
If a hacker has broken into my house and is sitting in the office messing with my computer I probably have more serious security problems than a Windows update can fix. Locked my front door turned on porch light. There fixed. Hella easier than resizing partitions.
Thanks for info, it worked.. mine was 509mb and it didnt install.. followed steps from the link posted in the description and increased the partition by exactly 250mb via command line prompts.. checked windows update again and everything installed flawless!
Thanks for the information. I am having the same issue with trying to install this update. I hope you are right and Microsoft will get enough complaints about it to fix the issue. Thanks again for getting the word out.
Funny how I found out about this update today and your video was three weeks ago. Ive been trying a bunch of different methods to try and get it to update but none of them worked. Now I know why thanks to you. I think Im going to ignore this update.
Thanks for the info, I’ve been searching for a fix since yesterday. I’m way over my head here though haha I’m just gonna wait and hope for a new update soon 👍🏻
I fixed mine without having to delete the recovery partition. Here is what I did... Used the Microsoft Disk Management and shrank the OS partition by 1GB, just to be safe. Downloaded and installed AOmei partition manager standard, the free version. You don't need the pro version for this. Launch the command/DOS prompt as an admin. You can create a shortcut on your desktop, right click and use CMD for the target, name it whatever you want. Right click the shortcut you just created and select Run As Administrator. Now you need to stop the recovery service, type reagent /disable. Now install and run the AOmei partition assistant. Select the recovery partition and resize it to use the extra space you have from shrinking the OS partition, should be 1GB if you shank it by this much. Now in AOmei, click apply. It should now show a larger recovery partition. Now either reboot or go back to your admin command prompt, and start the recovery service by typing reagent /enable . Now run the update, it should work now.
4:57 Microsoft own manual partition resizing instruction fail with MBR disk. Microsoft try to set partition ID to 27, but the format command sets partition ID again to 7 and Microsoft's instruction does not work. Recovery partition also doesn't work for the same reason. You have to enter the command set id=27 when the MBR partition format command is done, or else the instructions won't work. There may be a similar error in the GPT disk instructions. 🧐🤔Normal MBR disk NTFS partition ID number is 7 and MBR disk rocovery partition ID number is 27. Microsoft's own instructions destroy the entire recovery partition and its data. The Format command creates a standard NTFS partition. The following commands don't even find the revocery partition anymore and windows creates a Recovery folder on the C drive, where the tool programs are copied. The instructions end at the point where the recovery partition no longer exists and the tool programs have been copied to the wrong place. The instructions have created a standard NTFS partition, which does not work as a revocery partition at all.
Well, the "Windows, computers and technology" channel actually advised users to download & use the Windows Update Show/Hide tool to hide KB5034441, so that users who the update is failing to process for can ignore it.
Microschrott should just simply retract that update... and anyhow they should implement simple mechanisms like in Win7 Pro to never show that update again... especially on the PRO version! It is dead simple to implement, like (preferably separately) download and install every single update and even with the first use of Windows Update they could ask "do you want to always select updates separately?" Anyhow... these days Big Tech more and more feels like they must decide for the user, because they can not think for themselves. Yes, on one hand MS wants to make live as simple as possible, but on the other hand they really should understand, that - especially if you are using developer mode - uses might be very tech-savvy.
Hi I found a fix that worked for me, I haven't heard anyone else talk about this? if anyone has expanded their recovery drive and the update still doesn't work, watch this video on youtube, to make sure that your recovery environment is actually enabled, this fixed the KB5034441 problem for me, here is the video title: How to Enable Windows Recovery Environment on Windows 10 [Tutorial]
I have expanded the recovery partition on my computer, and after that, it installs successfully. However, the online Microsoft step-by-step guide is a little bit flawed. In the guide, you read "OS partition index". That what you are looking for, is not actually the partition on which Windows is installed. You are looking for the partition from which you can free up space, which in Command Prompt, has the type "Primary". You need to select that, and unallocate 250 MBs of space with the given gommand. Just be aware of that. It made me confused for a bit, but then I checked in Disk Manager, and the only partition I was able to shrink, was that on my C drive.
I have a 574 mb partition and have the error issue also. I was debating whether to clear previous updates but felt better to be safe than sorry and gonna wait to see if Microsoft releases a fix.
@@resonmon or you can just hide the update, go to google in your PC/laptop, search WUSHOWHIDE click the windows One, or the second one, then scroll until you find WUSHOWHIDE tool link, then run the WUSHOWHIDE tool after that click hide update Choose the KB5034441, after hiding the update, go to check update see if you still have the error "WUSHOWHIDE UPDATE IS AN OFFICIAL WINDOWS TROUBLE SHOOTER TOOL" so ITS safe. To download
Mine recovery partition is only 512MB and I'm getting a "Download error - 0x80070643" for KB5034441 in Windows Update when trying to download it (the others downloaded ok) so maybe MS has withdrawn it? Either way I think I'll leave it alone and wait for MS to roll something out rather than mess about increasing the partition size 🤔
One would expect that Microsoft would make the update check for size or very existence of the partition and then decide to install it or to make a placeholder with the note in System menu that it is unavailable due to size of partition or the type of the system. I guess that is not in the minds of the company that currently (sort of) prevents you to install their latest OS due it is out of their fashion style, although it is more then enough performance capable to run it.
Right! I didn't have the partition. I set everything up, installed the update, then wiped the partition. Ran SFC /scannow. Everything came back good. And that was it. Typical Microsoft..
After the update it uses almost 550Mb of space there, so it doesn't fit in the default 500Mb partition created during the initial Windows installation...
@@Sacto1654 Depending on the layout (and there may be so many layouts, including weird dual-boots with Linux) it will require very specific actions... Can't be scripted reliably... If they try, we'll see a lot of corrupted setups because the script did something dumb...
Update on my situation... Not gonna lie, it was a bit stressful... So, I had 500MB recovery partition, followed by EFI, followed by 16Mb MSR, and then the C partition... In other words, the Recovery partition wasn't at the end... Even worse is the tiny useless MSR partition in-between EFI and C... It cannot be moved or resized, even by Minitool PW... So, after making a backup image of the entire drive I did the following in MiniTool PW: 1. Resize C to add 1GB of space in front of it; 2. COPY the 16Mb MSR partition to the end of the new unallocated space; 3. Delete the original MSR; 4. (IMPORTANT) Set the partition flag of the MSR copy to Microsoft Reserved, because it isn't carried over during copy; 5. Move EFI partition to the right; 6. Resize the Recovery partition to fill all the space. Importantly, the order of partitions didn't change, so after all the operations were done, the computer booted fine... The 4441 update installed successfully... Before the update the Recovery partition used 445Mb/500Mb, now it uses 543Mb/1.25Gb... Obviously, 500Mb wasn't enough... For some reason, a lot of people on the Internet say DO NOT EVEN TOUCH the MSR partition, it is extremely crucial, and the computer won't boot... Maybe they confuse MSR and EFI??? Always make backups!!!
The problem with this failure with tens of thousands of Win 10 users. 99% are not going to go through a long procedure to fix this issue since Microsoft was in error and should send a work along to fix it in the near future. I know I am not going to put line after line in attempt to fix it since doing the obvious fixes: Trouble shooter that fixes update problems and others that do NOT work. I tried the sfc and Dim one which just takes an hour to run both. Also does not work. Those were touted by others as being possible fixes. I am still able to receive daily defender updates when they come in. I am just going to wait it out and see if Microsoft is going to fix this stuff they put out incorrectly.
The problem with Microsoft's fix, is that's it's wrong. When you go back to verify the location of WinRe after doing their fix, it actually has moved to the OS partition. It's not even in the correct partition anymore, and the recovery partition that Microsoft tells you to create, gets mounted as a primary drive with label, therefore it shows up in the file explorer as a storage device. The level of incompetence shown by Microsoft here is just astounding. The actual way to fix this problem, is with DISM. You have to issue a DISM command to copy the existing recovery image out of that partition, then resize it as an unallocated space, and then use DISM to copy the image back in. Then mount/enable it in the system with the WinRe enable commands. That's how you actually fix it. I really don't understand why a multi-billion dollar company like Microsoft, is so grossly incompetent. All i can say is, I'm so glad i made the switch to Linux all those years ago. I still have to support Windows, that's how i know how to fix this. But every day I work on Windows, i'm reminded why i hate it so much LOL!! Our little online community of Developers has a nickname for Windows 10. We call it "Malware 10". 🤣🤣🤣 Funny thing is, the more time goes on, the more it seems to live up to that name. ¯\_(ツ)_/¯
I also tried the Microsoft instructions yesterday in a virtual Windows 10 Pro installation in VirtualBox. Much to my irritation, I got the same results you described. After following the Microsoft instructions, the Windows recovery environment, previously contained in a separate recovery partition, was now included in the operating system drive in the "C:\Recovery" directory. And the newly created recovery partition was then present as an empty new drive in Windows. And the security update KB5034441 still could not be installed with the same error message. I found this development quite irritating. How could Microsoft make such mistakes in this proposed solution? And why haven't these instructions been changed yet? And why could the security update still not be installed even though there was enough free space in the operating system drive? I was very happy that I only tried the Microsoft instructions in a virtual Windows 10 Pro installation.
Every other update that was pushed out for me download and installed without issues. But, that f'n KB5034441 didn't, It gave me that 0x80070643 error code. I tried and tried and still nothing. That's been since the 9th for me. First time this has ever occurred for me.
I have no intention of trying to fix this problem. The last time I tried that, due to a previous Windows update stuff-up, I ended up having to re-install Windows. Never again.
Thank you so much for this video explaining what the problem is. I used AOMEI Partition Assistant to resize my recovery partition, and it allowed the update to install.
For me it was the last partition on the disk that was about 400 MB in size. I resized it to 2 GB, which did the trick. I'm pretty sure the partition was labeled as a recovery type in the program.@@alphaomega1969
Thanks for the video. What the hell is Microsoft thinking? My father is 76 years old and my mother is 75 years old, should I send them instructions from 1993? I have to teach them CMD line and diskpart, and where is which disk and partition! After all, they don't even know what's in that box, let alone know that it has a disk.
thank you for what you said brother!... I'm still worried because I saw that the kb5034441 update failed, I wonder why everything I have to do to put it on my pc but it still fails. By the way, you can just ignore the kb5034441 update because it's not necessary.
Thank you for the great content! I just got prompted that I need to restart to install the updates and this is one of the updates...Now I don't want to restart it because I only have 650MB for that partition... Hoping you would do a step-by-step tutorial on how to do the increment of space to the partition (to reduce the risk of us f***ng up something)...that would be truly appreciated and awesome!
Is it because of that update that the blue screen keeps appearing these days? It was fine until a few days ago, but lately the blue screen keeps popping up while playing games
Thank you very much for your advice in reports of Windows 10 KB5034441 failing to install. With my ASUS X415 Laptop I've been having an issue trying to install the latest update of windows 10. I even tried troubleshooting, rebooting and the issue still exists.
Solution: if there is a problem with the security update, the only way to figure this out is to increase the recovery partition via a third tool program.. I gave my laptop to a service store in order to install this stupid update, because I couldn't myself solve it... increase up to 700MB your recovery partition and problem is solved!
Macrorit Disk Partition Expert will enable the automation of the process using a GUI and a batch file will then automate the process for you. It is a free utility.
@@brentech Hey thanks. Turns out it wasn't Microsoft at fault. It was my Kaspersky Total Security that just deciced to block ALL my updates! Shits and giggles at the Kaspersky Lab I guess?
Through the AOMEI Partition Assistant 10.2.2 program, I was able to delete the Health folder, which was 255 MB in size, and created a 1 GB replacement for it. Then I reinstalled update number KB5034441, and the installation was successful.
the pushed up the update without fixing the issue first for a simple reason : TOTAL INCOMPETENCE as it as always been lately in updates. I'm not modifying my partitions in any way , i'm not gonna risk to break my system for their incompetence , i dont need a recovery partition at all nor i need the crappy updates
This Update is less than 24 Hours Old. I'm sure there will be a patch. Hopefully. I don't have the tech knowledge to even attempt that fix so U better give a Step-by-Step Visual Guide on how to do that fix When U say Ignore for now, I will. For Those that will say or comment well U should know how to Understand how to fix your Computer- There are Computer Repair Shops and People that get paid a lot more than me to Understand this stuff. People that went to School to learn this Stuff. I didn't. If U contact Microsoft Support, they are just going to follow their steps on their Support Page because they don't have any other knowledge of fixes to go by at the moment so that will be a waste of your time to even try. I compare this to when Your Car Breaks Down. Some People know how to fix Cars, Others bring it to the Auto Mechanic to get it fix so they don't have to deal with the Stress. If U have the Update Congrats. If U don't have the Update and honestly don't know what the heck u are doing, wait for a follow up video before U break your computer on accident.
Yeah, I opened the CMD, command prompt and copy / pasted the command for disabling the recovery environment, then I enabled it again, and, finally just in case logged in under my administrator account and went to the windows update...... BAM, update was completed after over a week and 18 other unsuccessful tries, it installed without any change to the buffer, yay!
That published fix doesn't work on all machines and on some it causes the WinRE not to run. This is from personal experience applying it to many different machines. My advice is download the Microsoft Fixit tool that hides the update so you don't keep on seeing 'Update failed - Retry'
Microsoft ... forces updates on to Windows users. Forced update breaks computer. How can they legally get away with this? Forced updates must be illegal.
At first I was confused, in the end I increased the volume of the system reserved partition to 1.03 Gb because I was so annoyed that I increased it all and managed to install the update.
A good footnote on this "FIX". If you don't have your system backed up prior to doing it, please ensure you do have a backup. With that said: The MBR fix does NOT work. The problem is not assigning the new partition as type 27. (Recovery partition) because once you FORMAT NTFS, it reverts to a regular partition and you cannot use it for recovery at all. Edit: The reagentc will move the recovery to your SYSTEM drive! WHAT A MESS.
when this update came out with other updates that actually worked, my audio drivers are broken. even if my headset is connected it says theres no headphones connected. i think this is the reason why it broke.
I skipped it. It's not really needed and there's only a year and a half until it reaches end of life. By then I'll have removed it and done a full install of Linux instead of my current dual boot. That's the only time I'm going to mess with the partitions again.
I followed the instructions but chickened out when it came to deleting the old existing recovery partition (260MB). It did create a new recovery partition which is 980MB, which is also recognised correctly by the reagentc /info command, but the update still fails to install...
Funny thing, my recovery partition size is 530mb & still failed to install the update. So the 250mb recommended partition size by microsoft is not apply to my PC
KB5034441 fails if you have no recovery partition. On MacBook bootcamp, WinRE has no drivers for disk, keyboard and trackpad. This makes it useless, so I deleted the partition.
Windows home does not support bitlocker so if you have home ignore the update ,if you have pro and not have activated bitlocker ignore the update most computers do not ship with bitlocker activated. A hacker would need physical access to your computer for the exploit to work so really this update is not needed there are a number of really bad security holes in windows which been around since windows 3.1 that have not been patched that is so much more worse than this that can be run remote that still to this day that has not been patched and that is why i don't use windows anymore and have moved to Linux.
I did the update, just followed instructions on using diskpart. took about 15 mins.. no big deal. I'm not a programmer or computer genius, but I can follow instructions. How did I know it would work? I read the comments first and everybody was saying it was a great video.
On my PC, there was no error message in regard to insuffiecent disk space, it just failed and said try again later, however I used Disc Genius (free) to change the size of the recovery partition and it worked.
I couldn't even do those instructions in that page their link directs me to. I get to the section where I select my Drive, but when I run "list part" instruction Command Prompt tells me no Drive was selected. Damn stupid instructions 😡
I installed AtlasOS over Windows 11, which disables all the spyware and disables Windows update. I'm the only one who uses my PC, so any WinRE issue is irrelevant to me.
From what I saw, the patch wants about 750 MB or more in the Recovery Partition. Mine was 500 MB and it failed to install. I increased to 750 MB and it installed.
@@cheokfungchiew9741 If you have 3rd party partitioning software, that's the easiest. If not, then you'll need to follow the instructions in the KB article from Microsoft. I've seen 2 possible scenarios: 1) the Restore Partition is at the end (right side in Disk Manager). If so, shrink the C partition and recreate the Restore Partition. 2) The Restore Partition is to the left side. In this case, my suggestion would be to use 3rd party partitioning software or ignore the error and, hopefully, MS will come out with a newer patch that doesn't have the issue. Scenario 2 can get dangerous quickly. If you use 3rd party software, you'll need to reboot when done then try the install again. Whatever you try, make sure you have a backup first. Also, you can only shrink the C partition if it has the room to be shrunk. If it's almost full, then there's nothing you can do except get a larger hard drive or delete some data off the C partition. If you choose to ignore the error, MS does have software that will allow you to tell Windows to ignore that patch and not bug you about it again. It's called "wushowhide.diagcab". download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab
im glad i found this i will ignore the update but my beef is partitions were set when i installed i used recommended settings at the time if it doesn't work on what was previous recommended this should only be in optional extras with a may not work warning bad form as normal
oops mistake! 03:38 900MB 2nd partition is in wrong place and should be 100MB EFI then OS then 900MB Recovery or the 22H2 upgrade fails due to wrong order partitions. i fixed many broken win updates w reagentc to enable
Windows 10 pro. This particular update fails. Checked my recovery patition which is 522 mb by normal windows installation. That was yesterday. I ran the update today. But again failed. Check recovery partion - surprised it automatically added one more recovery parition 546 mb. Now I hv two recovery partitions - one original and 2nd one added automatically by this update. Ran onece more. But still it failed.😢
It installed fine on all my computers with recovery partitions of various sizes decided by the Windows installer or computer manufacturers starting at 500 MB, but on one where I created the partitions by hand it failed with a 537 MB recovery partition, perhaps it expects sizes divisible by the programmer's favorite number 🤔
@@user-pf2jl3es1q I resized it with Paragon Hard Disk Manager 15 because I already had it, it's almost 10 years old and does not recognize newer partition types but knowing the limitations it can be still used to resize NTFS partitions.
I did the fix and it was easy if you follow step by step instructions. Its a good learning experience for those curious. Worst that happens is hard drive gets messed up and you have to reinstall windows and lose data. There are some people who should not attempt this. But there are others like me who can follow simple instructions, and maybe learn something in the process. I learned how to fix cars and computer by just going for it!!! Did I ever may a mistake fixing cars and computers, yes, but it was a learning experience.
I've gotten that error, too. I'm not gonna bother trying to increase the recovery partition, because I don't want to risk breaking my computer. Microsoft should've known better than to release an update that can't be installed for a lot of users. Hopefully, they'll pull this update ASAP and replace it with a new version that fixes the error.
Edit: Well, I found out earlier that Microsoft will not fix this issue after all, so I ended up doing what I didn't want to do in the first place with help from a video from another RUclipsr (Julia's Tech Spot) to ensure I do it correctly. Thanks to that video, I was able to properly adjust the C drive size and increase the size of my recovery partition to get the update to finally install. I hate that it has led to this outcome. They should've pulled the update instead.
So won't I ... expecially as I don't use Bitlocker.
Still it's stupid from MS pushing a failing 'Security Update'
@@lukasbruderlin2723 ...again...
@@lukasbruderlin2723 Its even worse and super gross they gave out this info!! People on REDDIT had to spread the info that this will break pcs and laptops that arent good enough to enlargen the recovery partition! If someone older googled it and gets that article first and follows the instructions, they'd have their computer destroyed. This feels like a disgusting way to handle this because in the end they win! They get you to buy a new computer and most likely windows 11 to get past it...
I did that it worked, but now I am having the error again not to mention I had issues is there a way to undo the increase on recovery partition I did and is there a fix for this error?
They still haven’t done anything
Actually, this update is not that important. It is important if you use bitlocker, which would impact business users most likely running Pro. Also, most users do not dork with the recovery partition, it is set by Microsoft, or possibly an OEM/Sysadmin depending. So, Microsoft should know how big that partition is and they should have known it was going to cause widespread failure. Additionally, this is a security patch for a business that should be pushed out by their sysadmins and not included via the internet, especially knowing the failures it will cause.
Finally, resizing a partition is not a simple thing. I am shocked Microsoft would think that it is given there are restrictions based on data storage in the other partitions. Why on earth they didn't create a temporary folder in the system partition and swap between the two is beyond me since I'm assuming the partition size issue likely revolves around the recovery files being moved and replaced. For heaven's sake, every Windows computer has a C drive/Primary partition. There is nothing stopping the developers from using a temp space on that drive, and oh, I don't know, even to a disk space check before running and if there isn't space failing the update with the message to free up space.
Speaking as a retired software developer. The lack of error handling by the current generation would have resulted in a LOT of firings back in the 90s and 2000s. Oh, and I'm a Microsoft alumni from the 90s. I can't understand how the company has fallen so far in its quality. They should be embarassed.
Good to know it's only important if you use bitlocker. Thanks!
I think you can even have the recovery environment on the C drive, at least on earlier Windows 10 builds that was possible.
Good to know about that thank you. Interestingly I have Win 10 Home, so it does not have bitlocker so the part that this update is supposed to fix is pointless.
It is not important but it is blocking another update in the queue 😡
Since 1982
I have an incurable fast growing Allergy
against anything
Micro Soft
I still use Win XP and Win 7
without any problems ever
and am immune to the para noikkers
whats sad is microsoft doesn't realise they are asking millions of novice users to try an tinker with critical parts of th OS. That doesn't sound like a good idea to me. They probably said to themselves oh well screw them they are the ones that refused to upgrade to windows 11.
Sorry but I am down voting every video that shows how to fix because this is 2024 and Microsoft knew they shouldn't have rushed the update, and to expect a very large amount of people who don't know much about computers, and software to mess with anything for windows recovery, let alone the Command prompt is the stupidest thing any company can do. You think the Nurses, Doctors, Elderly, and others are not going to damage there computer or worse screw someone else files? This is Microsoft's screw up, and they should be the ones to fix this.
I totally agree.
This update has been failing on my rig ever since they put it out.
Every once in a while, I will retry it, and it still fails.
I know how to resize a partition, but I refuse to do it because this is Microsoft's debacle - they are allegedly the experts so they should be the ones to fix it.
There are a lot of folks out there who are not tech savvy enough to be messing with that type of stuff, and Microsoft should know this.
If they are not going to fix it right away, they need to take it out of the Update Queue until it is fixed.
thank you so much for this! I thought I was going crazy trying all these other "hacks" I found online forcing me to download and install different software to try and fix the problem. Unfortunately I don't feel like manually changing the disk partition so I'll just wait and hopefully a new update will be released. This was immensely useful though and really eased my irrational thoughts.
Ignore ignore ignore. This update is going to be abolished for an upgraded update. Like all updates in the past that had issues. Either Microsoft sent a removal tool for the update if it installed successfully in some devices and then the install for the upgraded or different update became available. Do not mess with your partitions or you will do more harm or crash your computer. Don't force install or your drivers may act up and fail if they're not up to snuff.
Thanks for this. I encountered this error myself a few hours ago. I found that disabling and then reenabling the recovery environment fixed it. Though, to be clear, I had to do this a few times, with reboots in between for it to stick. The part about there not being enough space in the recovery partition I found was a red herring, as there was plenty of space on that partition in my case. It may well be the same for others.
how did you disable the recovery environment
@@stekl9wka Start an elevated command prompt and type in "reagentc.exe /disable." Without the quotation marks and then press enter. To reenable Windows RE, type "reagentc.exe /enable," and then press enter. It may or may not work for you to do this as I did a few times (rebooting in between), but worth a shot. You can check if it's properly enabled again by typing, "reagentc /info."
How did you disable recovery?
@@stekl9wka run command prompt as admin and type reagentc /disable and then type reagentc /enable
@@madmax2069 run command prompt as admin and type reagentc /disable and then type reagentc /enable
I do have a error but I don't like to mess with partition recovery I just ignore it.
Precisely. A no brainer.
Don't bother even continuously trying to download KB5034441. It's been overridden by the update 22H2 KB5034736. This download installed fine and restarted my computer. I still get the promt to download the former and one still gets the error. A new removal tool also was installed. You may still get the prompt to download the former. Don't do it and don't mess with the partitions. Nothing wrong with the computer. Eventually windows 10 will be no more anyways
Great info on recovery size being to small. Went into Mini Tool partition Wizzard. Expanded recovery partition.Took about 2 minutes for process.Did a restart and went to Windows Update clicked on update. Process to a few minutes but worked just fine. Thanks for your great info.
Love your background!! That's the Albuquerque international balloon fiesta! Behind the balloons is the Sandia Mountains and below the balloons is the Rio Grande.
yeah, windows default recovery partition is 500mb... which is where it fails. IMHO most people who would run with defaults aren't going to be "comfortable" trying to fix it.
I resized that partition from 500 to 750 MB and its okej now, but its crazy how Microsoft propose that every PC user know how to make it even with that instructions, no everyone its PC IT. What they think????
i had 565MB recovery partition with MiniTool partition wizard i added 1GB then installed update
A frequent cause of failure is that not all hard disks have a recovery partition. In that situation a failure to install is actually normal. You cannot update what does not exist. So it fails.
Typical Microsoft update, no real testing and just throw it out there to the masses. I'm tired of being an unpaid beta tester (actually alpha tester, since they don't test anything). Everyone needs to take control of Microsoft updates on their machines, and I highly recommend delaying all updates for at least a week to allow the mistakes to show up and be fixed before allowing them onto your machine. There are several videos and articles available that will tell you how to set this up. Personally I've turned off all so-called feature updates, and delayed all other updates for a week. I sure hope someone creates a top notch operating system for the masses soon; I can't see Microsoft getting any better.
Disable updates, you and none of us need updates....
When that update failed on my laptop, my desktop and my church's computer, I set all of them to delay updates for two weeks to give programmers time to get it right.
They did a terrible, terrible job this time. On one machine it even tried to install Windows 11 disregarding group policies. Something very chaotic is going on at Microsoft.
Do NOT mess with disc partitions, just pause updates and wait for microsoft.
@repIika i had 565MB recovery partition with MiniTool partition wizard i added 1GB then installed update
I resized my partition... But I didn't "mess with it." I followed the instructions and the update installed great. It was really easy and took about 15 mins.
thank you for sharing this. I have this issue on my new system when I tried to update yesterday. I had never experienced an issue with Win Update before so this was something that puzzled me and I randomly came across your video today so I am glad I found an explanation for the problem.
*MicroSUX should address this problem, and not make the users deal an issue that they created*
If a hacker has broken into my house and is sitting in the office messing with my computer I probably have more serious security problems than a Windows update can fix. Locked my front door turned on porch light. There fixed. Hella easier than resizing partitions.
Thanks for info, it worked.. mine was 509mb and it didnt install.. followed steps from the link posted in the description and increased the partition by exactly 250mb via command line prompts.. checked windows update again and everything installed flawless!
Thanks for the information. I am having the same issue with trying to install this update. I hope you are right and Microsoft will get enough complaints about it to fix the issue. Thanks again for getting the word out.
Funny how I found out about this update today and your video was three weeks ago. Ive been trying a bunch of different methods to try and get it to update but none of them worked. Now I know why thanks to you. I think Im going to ignore this update.
Thanks for the info, I’ve been searching for a fix since yesterday. I’m way over my head here though haha I’m just gonna wait and hope for a new update soon 👍🏻
i had 565MB recovery partition with MiniTool partition wizard i added 1GB then installed update
I deleted the recovery drive and expanded by 250mb as instructed, restarted system and then update windows successfully. thanks heaps!
I fixed mine without having to delete the recovery partition. Here is what I did...
Used the Microsoft Disk Management and shrank the OS partition by 1GB, just to be safe.
Downloaded and installed AOmei partition manager standard, the free version. You don't need the pro version for this.
Launch the command/DOS prompt as an admin. You can create a shortcut on your desktop, right click and use CMD for the target, name it whatever you want. Right click the shortcut you just created and select Run As Administrator.
Now you need to stop the recovery service, type reagent /disable.
Now install and run the AOmei partition assistant. Select the recovery partition and resize it to use the extra space you have from shrinking the OS partition, should be 1GB if you shank it by this much.
Now in AOmei, click apply. It should now show a larger recovery partition.
Now either reboot or go back to your admin command prompt, and start the recovery service by typing reagent /enable .
Now run the update, it should work now.
Very useful. Thanks very much! I'll leave it and wait for Microsoft to sort it out.
You know that this updates is useless.. except if you use bitlocker because this is a bitlocker security update so pretty much its useless
@@bs_rockyroki2098 Thankyou
4:57 Microsoft own manual partition resizing instruction fail with MBR disk. Microsoft try to set partition ID to 27, but the format command sets partition ID again to 7 and Microsoft's instruction does not work. Recovery partition also doesn't work for the same reason. You have to enter the command set id=27 when the MBR partition format command is done, or else the instructions won't work. There may be a similar error in the GPT disk instructions. 🧐🤔Normal MBR disk NTFS partition ID number is 7 and MBR disk rocovery partition ID number is 27. Microsoft's own instructions destroy the entire recovery partition and its data. The Format command creates a standard NTFS partition. The following commands don't even find the revocery partition anymore and windows creates a Recovery folder on the C drive, where the tool programs are copied. The instructions end at the point where the recovery partition no longer exists and the tool programs have been copied to the wrong place. The instructions have created a standard NTFS partition, which does not work as a revocery partition at all.
Well, the "Windows, computers and technology" channel actually advised users to download & use the Windows Update Show/Hide tool to hide KB5034441, so that users who the update is failing to process for can ignore it.
Microschrott should just simply retract that update... and anyhow they should implement simple mechanisms like in Win7 Pro to never show that update again... especially on the PRO version!
It is dead simple to implement, like (preferably separately) download and install every single update and even with the first use of Windows Update they could ask "do you want to always select updates separately?"
Anyhow... these days Big Tech more and more feels like they must decide for the user, because they can not think for themselves.
Yes, on one hand MS wants to make live as simple as possible, but on the other hand they really should understand, that - especially if you are using developer mode - uses might be very tech-savvy.
Hi I found a fix that worked for me, I haven't heard anyone else talk about this?
if anyone has expanded their recovery drive and the update still doesn't work,
watch this video on youtube, to make sure that your recovery environment is actually enabled,
this fixed the KB5034441 problem for me, here is the video title:
How to Enable Windows Recovery Environment on Windows 10 [Tutorial]
I have expanded the recovery partition on my computer, and after that, it installs successfully. However, the online Microsoft step-by-step guide is a little bit flawed.
In the guide, you read "OS partition index". That what you are looking for, is not actually the partition on which Windows is installed. You are looking for the partition from which you can free up space, which in Command Prompt, has the type "Primary".
You need to select that, and unallocate 250 MBs of space with the given gommand.
Just be aware of that. It made me confused for a bit, but then I checked in Disk Manager, and the only partition I was able to shrink, was that on my C drive.
i had 565MB recovery partition with MiniTool partition wizard i added 1GB then installed update
No problems here - oh wait I'm on Arch
I have a 574 mb partition and have the error issue also. I was debating whether to clear previous updates but felt better to be safe than sorry and gonna wait to see if Microsoft releases a fix.
You know that this updates is useless.. except if you use bitlocker because this is a bitlocker security update so pretty much its useless🗿
@@bs_rockyroki2098 Should i completely ignore ? Will microsoft fix it in long run ?
Just ignore it if you dont use bitlocker. @@resonmon
@@resonmon just ignore it if you use window home, except if you use Windows pro ,
@@resonmon or you can just hide the update, go to google in your PC/laptop, search WUSHOWHIDE click the windows One, or the second one, then scroll until you find WUSHOWHIDE tool link, then run the WUSHOWHIDE tool after that click hide update Choose the KB5034441, after hiding the update, go to check update see if you still have the error
"WUSHOWHIDE UPDATE IS AN OFFICIAL WINDOWS TROUBLE SHOOTER TOOL" so ITS safe. To download
Mine recovery partition is only 512MB and I'm getting a "Download error - 0x80070643" for KB5034441 in Windows Update when trying to download it (the others downloaded ok) so maybe MS has withdrawn it? Either way I think I'll leave it alone and wait for MS to roll something out rather than mess about increasing the partition size 🤔
Ditto on the download error.
@@chrismoule7242 Same here.
I'm still getting installation error but I assume that's because I have it downloaded already
I faced same issue Did Microsoft developed this update during Christmas leave.
Microsoft please replace it with new update.
One would expect that Microsoft would make the update check for size or very existence of the partition and then decide to install it or to make a placeholder with the note in System menu that it is unavailable due to size of partition or the type of the system. I guess that is not in the minds of the company that currently (sort of) prevents you to install their latest OS due it is out of their fashion style, although it is more then enough performance capable to run it.
Right! I didn't have the partition. I set everything up, installed the update, then wiped the partition. Ran SFC /scannow. Everything came back good. And that was it.
Typical Microsoft..
I believe that Microsoft may pull this update and produce a new version that will work correctly.
After the update it uses almost 550Mb of space there, so it doesn't fit in the default 500Mb partition created during the initial Windows installation...
@@eliotcougar Hence the reason why Microsoft will need to produce an updated version of this patch.
@@Sacto1654 Depending on the layout (and there may be so many layouts, including weird dual-boots with Linux) it will require very specific actions... Can't be scripted reliably... If they try, we'll see a lot of corrupted setups because the script did something dumb...
Update on my situation... Not gonna lie, it was a bit stressful...
So, I had 500MB recovery partition, followed by EFI, followed by 16Mb MSR, and then the C partition... In other words, the Recovery partition wasn't at the end... Even worse is the tiny useless MSR partition in-between EFI and C... It cannot be moved or resized, even by Minitool PW...
So, after making a backup image of the entire drive I did the following in MiniTool PW: 1. Resize C to add 1GB of space in front of it; 2. COPY the 16Mb MSR partition to the end of the new unallocated space; 3. Delete the original MSR; 4. (IMPORTANT) Set the partition flag of the MSR copy to Microsoft Reserved, because it isn't carried over during copy; 5. Move EFI partition to the right; 6. Resize the Recovery partition to fill all the space.
Importantly, the order of partitions didn't change, so after all the operations were done, the computer booted fine...
The 4441 update installed successfully... Before the update the Recovery partition used 445Mb/500Mb, now it uses 543Mb/1.25Gb... Obviously, 500Mb wasn't enough...
For some reason, a lot of people on the Internet say DO NOT EVEN TOUCH the MSR partition, it is extremely crucial, and the computer won't boot... Maybe they confuse MSR and EFI???
Always make backups!!!
AOMEI Partition Assistant😎😎😎😎
i had 565MB recovery partition with MiniTool partition wizard i added 1GB then installed update
The problem with this failure with tens of thousands of Win 10 users. 99% are not going to go through a long procedure to fix this issue since Microsoft was in error and should send a work along to fix it in the near future. I know I am not going to put line after line in attempt to fix it since doing the obvious fixes: Trouble shooter that fixes update problems and others that do NOT work. I tried the sfc and Dim one which just takes an hour to run both. Also does not work. Those were touted by others as being possible fixes. I am still able to receive daily defender updates when they come in. I am just going to wait it out and see if Microsoft is going to fix this stuff they put out incorrectly.
The problem with Microsoft's fix, is that's it's wrong. When you go back to verify the location of WinRe after doing their fix, it actually has moved to the OS partition. It's not even in the correct partition anymore, and the recovery partition that Microsoft tells you to create, gets mounted as a primary drive with label, therefore it shows up in the file explorer as a storage device. The level of incompetence shown by Microsoft here is just astounding. The actual way to fix this problem, is with DISM. You have to issue a DISM command to copy the existing recovery image out of that partition, then resize it as an unallocated space, and then use DISM to copy the image back in. Then mount/enable it in the system with the WinRe enable commands. That's how you actually fix it. I really don't understand why a multi-billion dollar company like Microsoft, is so grossly incompetent. All i can say is, I'm so glad i made the switch to Linux all those years ago. I still have to support Windows, that's how i know how to fix this. But every day I work on Windows, i'm reminded why i hate it so much LOL!! Our little online community of Developers has a nickname for Windows 10. We call it "Malware 10". 🤣🤣🤣 Funny thing is, the more time goes on, the more it seems to live up to that name. ¯\_(ツ)_/¯
I also tried the Microsoft instructions yesterday in a virtual Windows 10 Pro installation in VirtualBox. Much to my irritation, I got the same results you described. After following the Microsoft instructions, the Windows recovery environment, previously contained in a separate recovery partition, was now included in the operating system drive in the "C:\Recovery" directory. And the newly created recovery partition was then present as an empty new drive in Windows. And the security update KB5034441 still could not be installed with the same error message. I found this development quite irritating. How could Microsoft make such mistakes in this proposed solution? And why haven't these instructions been changed yet? And why could the security update still not be installed even though there was enough free space in the operating system drive? I was very happy that I only tried the Microsoft instructions in a virtual Windows 10 Pro installation.
Every other update that was pushed out for me download and installed without issues. But, that f'n KB5034441 didn't, It gave me that 0x80070643 error code. I tried and tried and still nothing. That's been since the 9th for me. First time this has ever occurred for me.
I have no intention of trying to fix this problem. The last time I tried that, due to a previous Windows update stuff-up, I ended up having to re-install Windows. Never again.
Thank you so much for this video explaining what the problem is. I used AOMEI Partition Assistant to resize my recovery partition, and it allowed the update to install.
Which partition did you resize? 😅
For me it was the last partition on the disk that was about 400 MB in size. I resized it to 2 GB, which did the trick. I'm pretty sure the partition was labeled as a recovery type in the program.@@alphaomega1969
Thanks for the video. What the hell is Microsoft thinking? My father is 76 years old and my mother is 75 years old, should I send them instructions from 1993? I have to teach them CMD line and diskpart, and where is which disk and partition! After all, they don't even know what's in that box, let alone know that it has a disk.
thank you for what you said brother!... I'm still worried because I saw that the kb5034441 update failed, I wonder why everything I have to do to put it on my pc but it still fails. By the way, you can just ignore the kb5034441 update because it's not necessary.
I am having this issue. Thanks for letting us know.❤❤❤
Thank you for the great content! I just got prompted that I need to restart to install the updates and this is one of the updates...Now I don't want to restart it because I only have 650MB for that partition... Hoping you would do a step-by-step tutorial on how to do the increment of space to the partition (to reduce the risk of us f***ng up something)...that would be truly appreciated and awesome!
There already are Videos on how to do it... anyhow I'm not going to risk braking my machine and rather wait for MS to fix this!
I'd just ignore the update but will it not stop future updates coming in ??
ruclips.net/video/71CMOqvW1Go/видео.html
They're still pushing this update. It has "download failed" on my machines for two days in a row.
Is it because of that update that the blue screen keeps appearing these days? It was fine until a few days ago, but lately the blue screen keeps popping up while playing games
No. Sounds like a hardware error. Lemme guess: you have a AMD gpu?
Thank you very much for your advice in reports of Windows 10 KB5034441 failing to install. With my ASUS X415 Laptop I've been having an issue trying to install the latest update of windows 10. I even tried troubleshooting, rebooting and the issue still exists.
Solution: if there is a problem with the security update, the only way to figure this out is to increase the recovery partition via a third tool program.. I gave my laptop to a service store in order to install this stupid update, because I couldn't myself solve it... increase up to 700MB your recovery partition and problem is solved!
Macrorit Disk Partition Expert will enable the automation of the process using a GUI and a batch file will then automate the process for you. It is a free utility.
You know that this updates is useless.. except if you use bitlocker because this is a bitlocker security update so pretty much its useless🗿
Over a week and still NOTHING from Microsoft.
ruclips.net/video/hzc0qeDRfdk/видео.html
@@brentech Hey thanks. Turns out it wasn't Microsoft at fault. It was my Kaspersky Total Security that just deciced to block ALL my updates! Shits and giggles at the Kaspersky Lab I guess?
my dad has windows 10 and he dosent have bitlocker enabled, so like why would people that not use bitlocker need this update?
Through the AOMEI Partition Assistant 10.2.2 program, I was able to delete the Health folder, which was 255 MB in size, and created a 1 GB replacement for it. Then I reinstalled update number KB5034441, and the installation was successful.
the pushed up the update without fixing the issue first for a simple reason : TOTAL INCOMPETENCE as it as always been lately in updates. I'm not modifying my partitions in any way , i'm not gonna risk to break my system for their incompetence , i dont need a recovery partition at all nor i need the crappy updates
This Update is less than 24 Hours Old. I'm sure there will be a patch. Hopefully. I don't have the tech knowledge to even attempt that fix so U better give a Step-by-Step Visual Guide on how to do that fix When U say Ignore for now, I will. For Those that will say or comment well U should know how to Understand how to fix your Computer- There are Computer Repair Shops and People that get paid a lot more than me to Understand this stuff. People that went to School to learn this Stuff. I didn't. If U contact Microsoft Support, they are just going to follow their steps on their Support Page because they don't have any other knowledge of fixes to go by at the moment so that will be a waste of your time to even try. I compare this to when Your Car Breaks Down. Some People know how to fix Cars, Others bring it to the Auto Mechanic to get it fix so they don't have to deal with the Stress. If U have the Update Congrats. If U don't have the Update and honestly don't know what the heck u are doing, wait for a follow up video before U break your computer on accident.
Yeah, I opened the CMD, command prompt and copy / pasted the command for disabling the recovery environment, then I enabled it again, and, finally just in case logged in under my administrator account and went to the windows update...... BAM, update was completed after over a week and 18 other unsuccessful tries, it installed without any change to the buffer, yay!
That published fix doesn't work on all machines and on some it causes the WinRE not to run. This is from personal experience applying it to many different machines. My advice is download the Microsoft Fixit tool that hides the update so you don't keep on seeing 'Update failed - Retry'
Microsoft ... forces updates on to Windows users.
Forced update breaks computer.
How can they legally get away with this?
Forced updates must be illegal.
At first I was confused, in the end I increased the volume of the system reserved partition to 1.03 Gb because I was so annoyed that I increased it all and managed to install the update.
Wondering why MS has such general "Security Updates" categorized as "Quality Updates"
A good footnote on this "FIX". If you don't have your system backed up prior to doing it, please ensure you do have a backup. With that said:
The MBR fix does NOT work. The problem is not assigning the new partition as type 27. (Recovery partition) because once you FORMAT NTFS, it reverts to a regular partition and you cannot use it for recovery at all.
Edit: The reagentc will move the recovery to your SYSTEM drive!
WHAT A MESS.
How do I revert it?
@@gibson7654 The first part of my response. Back up your system BEFORE you do anything.
when this update came out with other updates that actually worked, my audio drivers are broken. even if my headset is connected it says theres no headphones connected. i think this is the reason why it broke.
I skipped it. It's not really needed and there's only a year and a half until it reaches end of life. By then I'll have removed it and done a full install of Linux instead of my current dual boot. That's the only time I'm going to mess with the partitions again.
I exteened the re partition and i still have the update failing. Literally no use
I followed the instructions but chickened out when it came to deleting the old existing recovery partition (260MB). It did create a new recovery partition which is 980MB, which is also recognised correctly by the reagentc /info command, but the update still fails to install...
I was wondering why my mum's computer was refusing to update, and I was forced to remove a couple of previous updates for it to work
Funny thing, my recovery partition size is 530mb & still failed to install the update. So the 250mb recommended partition size by microsoft is not apply to my PC
Increase it to 1GB.
KB5034441 fails if you have no recovery partition. On MacBook bootcamp, WinRE has no drivers for disk, keyboard and trackpad. This makes it useless, so I deleted the partition.
Windows home does not support bitlocker so if you have home ignore the update ,if you have pro and not have activated bitlocker ignore the update most computers do not ship with bitlocker activated.
A hacker would need physical access to your computer for the exploit to work so really this update is not needed there are a number of really bad security holes in windows which been around since windows 3.1 that have not been patched that is so much more worse than this that can be run remote that still to this day that has not been patched and that is why i don't use windows anymore and have moved to Linux.
No fix from Microsoft yet, it's halfway through March?
Correct
Listen, I'm tech savvy and even I don't mess with diskpart
I did the update, just followed instructions on using diskpart. took about 15 mins.. no big deal. I'm not a programmer or computer genius, but I can follow instructions. How did I know it would work? I read the comments first and everybody was saying it was a great video.
I have four computers. Installed fine on three, but one gives an install error.
On my PC, there was no error message in regard to insuffiecent disk space, it just failed and said try again later, however I used Disc Genius (free) to change the size of the recovery partition and it worked.
I couldn't even do those instructions in that page their link directs me to. I get to the section where I select my Drive, but when I run "list part" instruction Command Prompt tells me no Drive was selected. Damn stupid instructions 😡
My partition is 547 mb and still failing to install, resizing Microsoft ”fix” it's so full of crap, not worth bother!
I think its a broken update but unfortunately microsoft hasn't fixed it yet!
Microsoft is creating a lot of new Apple customers!
Should I install this 10 KB5034441 when there is no bitlocker on my computer?
No
You're the only one that helped
Use the Minitool Partition program to Move/Resize Partition on C drive and then add space to the Recovery Partition.
My recovery partition is 549 MB and I still can't install it!
I installed AtlasOS over Windows 11, which disables all the spyware and disables Windows update. I'm the only one who uses my PC, so any WinRE issue is irrelevant to me.
Interesting. However my recovery partition is 1GB with 900MB free and mine also failed 😞. So I'll just have to wait on MS
Go to advanced system options, system recovery, disable it, reboot, re enable it and the update will go thru 👍
From what I saw, the patch wants about 750 MB or more in the Recovery Partition. Mine was 500 MB and it failed to install. I increased to 750 MB and it installed.
same, i only got 500mb but how do i increase it
@@cheokfungchiew9741 If you have 3rd party partitioning software, that's the easiest. If not, then you'll need to follow the instructions in the KB article from Microsoft. I've seen 2 possible scenarios: 1) the Restore Partition is at the end (right side in Disk Manager). If so, shrink the C partition and recreate the Restore Partition. 2) The Restore Partition is to the left side. In this case, my suggestion would be to use 3rd party partitioning software or ignore the error and, hopefully, MS will come out with a newer patch that doesn't have the issue. Scenario 2 can get dangerous quickly. If you use 3rd party software, you'll need to reboot when done then try the install again. Whatever you try, make sure you have a backup first. Also, you can only shrink the C partition if it has the room to be shrunk. If it's almost full, then there's nothing you can do except get a larger hard drive or delete some data off the C partition.
If you choose to ignore the error, MS does have software that will allow you to tell Windows to ignore that patch and not bug you about it again. It's called "wushowhide.diagcab". download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab
i had 565MB recovery partition with MiniTool partition wizard i added 1GB then installed update
great video. have you ever seen this message? application has been blocked from accessing graphics hardware
Nope
My recovery partition is more than 500 megabytes but still I'm having the error!
im glad i found this i will ignore the update but my beef is partitions were set when i installed i used recommended settings at the time if it doesn't work on what was previous recommended this should only be in optional extras with a may not work warning bad form as normal
oops mistake!
03:38 900MB 2nd partition is in wrong place and should be 100MB EFI then OS then 900MB Recovery or the 22H2 upgrade fails due to wrong order partitions.
i fixed many broken win updates w reagentc to enable
It went away today.....all by itself. 👍👍 Oops, false alarm, has come back.
It’s 2 1/2 months later and they still haven’t fixed it and they’re not going to fix it so you’re going to have to do it manually
Windows 10 pro. This particular update fails. Checked my recovery patition which is 522 mb by normal windows installation. That was yesterday.
I ran the update today. But again failed.
Check recovery partion - surprised it automatically added one more recovery parition 546 mb. Now I hv two recovery partitions - one original and 2nd one added automatically by this update. Ran onece more. But still it failed.😢
For me is bigger problem that my laptop is now so much slower when i cant finish that update so any help for that?
Keep calm and carry on.
It installed successfully on one of my machines... It's the one that for some reason doesn't have a WinRE partition at all...
It installed fine on all my computers with recovery partitions of various sizes decided by the Windows installer or computer manufacturers starting at 500 MB, but on one where I created the partitions by hand it failed with a 537 MB recovery partition, perhaps it expects sizes divisible by the programmer's favorite number 🤔
good point mine failed at 509 mb
AOMEI Partition Assistant😎😎😎😎
@@user-pf2jl3es1q I resized it with Paragon Hard Disk Manager 15 because I already had it, it's almost 10 years old and does not recognize newer partition types but knowing the limitations it can be still used to resize NTFS partitions.
I did the fix and it was easy if you follow step by step instructions. Its a good learning experience for those curious. Worst that happens is hard drive gets messed up and you have to reinstall windows and lose data. There are some people who should not attempt this. But there are others like me who can follow simple instructions, and maybe learn something in the process. I learned how to fix cars and computer by just going for it!!! Did I ever may a mistake fixing cars and computers, yes, but it was a learning experience.
Why was even sent to Win 10 home?