New
#100
Hello and greetings from Poland.
On my PC with Windows 10 the KB5034441 update also failed to install and reported this error.
I tried to clean the SoftwareDistribution folder and disable the antivirus/firewall - nothing of these actions worked.
It pissed me off to the maximum, I went to bed with hope that M$ would release a repair patch as soon as possible.
But today error still appeared and I decided to try solution with resizing Recovery partition.
I used Minitool Partition Wizard for this, I didn't want to bother with CMD:
1) I reduced the System partition (C) to 99 GB, my System partition was 99,5 GB before, Recovery approx 540MB
2) I choosed Recovery partition end extended it with unallocated space to 1GB.
3) Program restarted the computer several times.
4) After PC turned on - I turned off the Windows Update service, cleaned the SoftwareDistribution folder, turned on the service and searched for the update, it was downloaded and successfully installed.
After doing all of these steps list of all partitions on my drive looks like that:
If you don't know how to do it or be scared that you will do it incorrect and destroy your system:
1) Install program and run it as Administrator
2) Choose partition that you will resize by click LMB on it
3) Click resize on left and choose new size of partition, accept it
4) Click on recovery partition now
5) On the left side click extend
6) Choose unallocated space to extend Recovery, accept it.
!!!MAKE SURE YOU CHOOSE UNALLOCATED SPACE IN POINT 6th!!!
7) In left-bottom corner apply changes
8) Program should display message that it needed to restart the computer, so just allow it to do that
7) Don't panic if it take some time and DON'T TURN OFF/RESTART YOUR COMPUTER WHEN PROGRAM IS WORKING. You will have black screen some time, then program will show you progress of the work on the bottom of screen.
You can wait for a solution from M$ too, but I am worried how many time they will wait to repair it - they shared instruction how to enlarge Recovery step by step, so waiting for their action will take more time than doing it by yourself. I did it by myself, my PC is OK, not death working like before. It's not first problem with update, so I am not shocked that M$ did it again.
Sorry that screens from my system are in Polish language, I forgot to change it to English. "Pomyślnie zainstalowano" means successfully installed.
Last edited by Sebastian94; 10 Jan 2024 at 21:58.
I have read all the posts in this thread, but there is one thing I would like to know. Why did my install succeed without resizing the recovery partition?
This update is not really needed unless you
#1 actively use bitlocker (it's enabled)
#2 your PC is vulnerable to local physical attacks
You'll eventually have to install it because, well, Microsoft sucks now as far as updates go.
BUT I wouldn't rush to install it unless I met the 2 requirements I have posted.
I'd give it a few months or more to see if they release something more appropriate for those users that do not have enough space to install it.
The "fix" requires moving the recovery partition to the end of the drive (if it is not already there) and increasing the size of the recovery partition.
I would trust a known good automated process more than most users (no insult intended to anyone-really) to do this properly and without error. Microsoft may just release an automated process with a bit of time. Or they'll tell everyone to reinstall windows and manually increase the size of the recovery partition during installation.
Otherwise OS is pooched and re-install. Ensure your backups are up to date if you do attempt it.
My
* Windows 10 machines have a Recover Partition of 530 MB
* Windows 11 machine has 757 MB
so that might explain why Microsoft is suggesting an extra 250 MB
@LTSnow
"I have read all the posts in this thread, but there is one thing I would like to know. Why did my install succeed without resizing the recovery partition? "
Your recovery partition had sufficient space so install was no issue.
Mine is 2x the size set during install (900mb) - I always give more than the OS says you need.
More space, more CPU, more ram, more power supply - words I learned over 32 years of Desktop support!
We don't know that, maybe your Recovery partition is bigger than our were, so you don't have any problems with update and we have them. Nobody knows it without info about your system. If you are using Windows 10, maybe gave more space to it when you installed OS. My partition was approx 540 MB, so update result was error, nevermind what I did to install it. After resizing Recovery partition, update has been successfully installed.
I think that problem is with unpacking files of the package, after installing update my disk info shows that all of space added by me to this partition is free, not used, used is approx 460-470 MB of 1GB available from now, after i resized it.
Maybe default Recovery partition size when user install Windows 11 is bigger than in Windows 10, maybe M$ did one update for both systems, that ends like that - Windows 11 users have enough space on the partition to unpack and install it, but Windows 10 users partitions are too small to do it, but these are just my guesses, I'm not a programmer.
Really don't know what to write, I am only user like you, but i know that it works. I don't care that my Recovery partition size is now 1000MB and not ~550. For me important is that I don't have to reinstall my OS because programmers from worldwide company did their job the worst they can do it. Maybe you used newer ISO file from M$ site in which they changed something that allows your OS install this package, really nobody of us knows that, we only did what was in solution from them to not see anymore a frustrating update that won't install, every time when we launch Windows Update.
It seems like lottery - one user don't have problems with update and other have. But I am sure that M$ did it again - by uploading package that is problematic for users. And I am sure too this is not last time, it is what it is, so we can accept that or install Linux on our PC's.
Fortunately, it's not Vista, which had a tendency to crash at the slightest opportunity, and a partition program is enough to fix M$'s sloppiness.
Last edited by Sebastian94; 11 Jan 2024 at 00:22.