The new partition not work because it is not a recovery partition. The partition is a standard NTFS partition. Recovery files point to drive C and folder Recovery and new partition is completely useless now.
@@sterntechdaddy Command prompt reagentc /info tells you where the recovery partition is. I had a similar problem, but I finally figured it out. Microsoft's own official instructions are incorrect for the MBR disk type. The problem was the ID number and the instruction made a standard NTFS partition. Everything is correct only when the reagentc /info data actually points to the recovery partition. Info data reveals this. Windows simply does not accept a normal NTFS partition because the ID(Type 07) number is wrong. All values up to the ID(Type) number are important or else the recovery partition will not work. Diskpart can change and fix the partition ID number and it is enough for MBR disk type. In GPT disk type, Microsoft's official instructions work. Diskpart command detail partition show selected partition info. Diskpart command setid set partition type. Only one parition allowed to be type 27 and it's Recovery Partiotion. Normal NTFS partition type is 7. Partition type 27 is special partition witch allowed to boot automaticly if main boot partition fail. Standard NTFS partition type 7, it is not allowed to act as a Recovery Partition under any circumstances. The restriction is valid even before Windows starts. The update didn't even touch your new partition. The standard NTFS partition is not in any way or form a Revocery Partition and all the update data was stored in to the C drive. I think Microsoft's way of putting the recovery partition on the same disk is bad and it can also be locked if you use a pin code login and a Microsoft account. The problem can be fixed only by login with the correct Microsoft account password, which is not easy. After that, create a local user account and the old account password suddenly starts working in the revocery partition, if you do the same with pin code to login, the revocery partition stops working. This is a 0-day bug and the recovery partition requires a correct password, which won't work if this bug hits your spot. Because of this, one local backup user is a reasonable solution, but Microsoft is trying its best to prevent Windows users from creating a local account in the future. I am using windows server and logging into it, but it doesn't work or help to Windows Home version users. 99.9% have ended up reinstalling Windows or leaving the problem as it is. I don't, because I started to investigate the reason why the correct password is not valid for the places where it should work. From this we can conclude that the system administrator's passwords are stored in the recovery partition, because internet connection not needed, but a password is required. The recovery partition can be easily tested from Windows. Hold shift key down and select restart with the mouse. Revocery partition boot starts. The location is C drive or real revocery partition. In your case, the recovery partition should work, even if you delete the new created partition, because the recovery drive path leads to the C drive, where all the data is stored, if the C drive partition stops working, then the revocery feature can do the same. If you delete and create a new recovery partition, file copying starts on an empty partition when the partition is activated with the reagentc /enable command. If the recovery partition has been created incorrectly, then C drive starts to handle the recovery partition function (backup option for this fuction). It is safer if you know how to repair the real recovery partition. I suspect that the next target for hackers may be the recovery Ipartition passwords, if they can get their hands on them. About 1982 I got my first computer. So I know a lots of things that others don't. I using USB or bluetooth Yubikey 2FA security keys in all places where they work. I have 3 active USB keys. All accounts that can be locked if 2FA physical key is missing. I don't want to break you, so keep up the good work on the channel. If you play this information security game, there should be 3 keys. i have yubico 5 NFC keys and one 5Ci key for the apple products.
I've gone back to the laptop used and you're right - WinRE is using a folder on the C: drive and not the new partition. The reagentc /info command points to a Recovery folder on partition 3 - which is the main C: drive. So I think WinRE b0rks as it tries to use the new partition, fails and so reverts to the C: drive because it's the only place it can use. This fix does work, but not for the right technical reasons - and it won't work for everyone first time. I'll make a video explaining this in the future. 😁
If the new partition type comes up as "Data" you can use Disk Genius (free) to change the identity to "Recovery" before carrying on. I spotted this and this how I fixed it.
Thank you so much! Tried other fixes which exclusively use cmd and they didn't work. However following your simpler guide actually worked. Appreciate it!
I hope you receive the biggest check possible for this video thank you so much for this keep this up. People love to have videos like this when ever we need them and not enough people with these talents make them sadly.
Thank you so much! This is the most useful and easiest way I found on UA-cam. Worked like a charm, and solved problem very easy in my case! Thumbs up for this tutorial.
I actually can't even comprehend how grateful I actually am! I've not had Windows updated for months due to that I've had problems with monitors flickering or the second monitor won't even turn on, buzzing or humming sounds coming from my microphone when I'm playing on Steam, I'm kind of hoping this fixes that issue but either way I greatly appreciate your genius! Finally part of the windows updated club once again. 🙏💯
Probably won't fix it no. I'll try it tomorrow, literally only happens when I play a game on Steam, so weird! Hey windows being updated is definitely a positive.
Bruv, you really pulled my balls out of the fire here. As of march 13th 2:44 am central time I can say that this error is still an issue. Thanks for helping me get this sorted out. I subbed too. Cheers mate!
BRO!!!! I watched multiple videos on UA-cam. THIS IS THE ONE! AGAIN! IF YOURE HAVING THIS ERROR THIS IS THE VIDEO TO FIX!!! I watched multiple other videos regarding the CMD and followed the prompts on Microsoft page. NOTHING WORKED! THIS worked for me! THANK YOU THANK YOU THANK YOU THANK YOU! I wouldnt recommend any other video except this one, ive had this issue for months and its finally fixed! THANK YOU AGAIN!!!!
Thanks for this Nick. Been having this problem too with this KB5034441 but also KB5001716. I tried to include a screen shot of update history showing KB5001716 from October 2023 still refusing to install but exactly same KB5001716 with today's date installed successfully. Can't paste screen shot so you'll have to take my word for it. Anyway KB5034441 now installed. Thanks again. Tony
Glad it helped. The error is a general error that pops up when the WinRE partition isn’t large enough to fit the update into. So you can get the error for several updates - as you know! I’ll add this info to the description in case it helps someone else.
Glad it helped. There's no BSOD if you don't do this update - you just keep getting the Windows Update error. It's ironic that KB5001716 is an update for Windows Update components - it's just larger than some WinRE partitions can handle. The KB5034441 is a WinRE update that can also cause this error according to some of the comments on this video. Personally, I've only encountered the KB5001716 error. Microsoft might decide to fix it at some point. :)
There was another Windows update error in the couple of days, not related to the recovery partition size (assuming the size was previously increased for the problem a few weeks ago). However, it appears that MSFT has fixed the latest problem with a new update.
I hope so! It's the 9th March 2024 as I type, and I made this video a few days ago using a laptop I was refurbishing. It encountered the error during my usual Windows Update session - so if they have fixed it then they've fixed it very recently! About time too... the common update that produces this error was released in January! The error code actually refers to a 'not enough disk space' error so it might happen again. It seems the size of the WinRE partition varies! As this fix is free and pretty easy to follow it’s worth trying before getting anyone else involved. It might work and thus save some money. 🙂
3:40 if you have a lot of drives, you can look at the name of your boot drive on diskmanagement (the first step where you shrunk the volume) or another way is is when you type diskpart it will show free amount in mb. usually the other drives have 0 free.
DISKPART can be pretty scary, so a less technicdl way for people who don’t have your skills is to use Disk Management to view this information. It will show the partitions on a drive and label them as boot and system. It will also show the drive letter assignments. The WinRE partition will be small and not have a drive letter which identifies it nicely. Note that you can assign a drive letter and it’ll appear and be browsable in File Manager. Handy if you want the check what’s there. 🙂
holy fucking shit it really worked. Been unable to update this specific security update and this guide actually helped (ngl I was a bit skeptic at 1st) thanks a lot m8
mine didn't work. it kept it in two separate unallocated partitions, one at each end of that disk management line. I turned the largest one back into WinRE.. how do I merge the two unallocated partitions,,, doesn't seem to be any way to do it in Windows
You can do it with DISKPART or a third party program like EaseUS Partition Manager. But if you're not sure what you're doing then I would pay a tech expert to sort it for you.
The new partition not work because it is not a recovery partition. The partition is a standard NTFS partition. Recovery files point to drive C and folder Recovery and new partition is completely useless now.
@@sterntechdaddy Command prompt reagentc /info tells you where the recovery partition is. I had a similar problem, but I finally figured it out. Microsoft's own official instructions are incorrect for the MBR disk type. The problem was the ID number and the instruction made a standard NTFS partition. Everything is correct only when the reagentc /info data actually points to the recovery partition. Info data reveals this. Windows simply does not accept a normal NTFS partition because the ID(Type 07) number is wrong. All values up to the ID(Type) number are important or else the recovery partition will not work. Diskpart can change and fix the partition ID number and it is enough for MBR disk type. In GPT disk type, Microsoft's official instructions work. Diskpart command detail partition show selected partition info. Diskpart command setid set partition type. Only one parition allowed to be type 27 and it's Recovery Partiotion. Normal NTFS partition type is 7. Partition type 27 is special partition witch allowed to boot automaticly if main boot partition fail. Standard NTFS partition type 7, it is not allowed to act as a Recovery Partition under any circumstances. The restriction is valid even before Windows starts. The update didn't even touch your new partition. The standard NTFS partition is not in any way or form a Revocery Partition and all the update data was stored in to the C drive. I think Microsoft's way of putting the recovery partition on the same disk is bad and it can also be locked if you use a pin code login and a Microsoft account. The problem can be fixed only by login with the correct Microsoft account password, which is not easy. After that, create a local user account and the old account password suddenly starts working in the revocery partition, if you do the same with pin code to login, the revocery partition stops working. This is a 0-day bug and the recovery partition requires a correct password, which won't work if this bug hits your spot. Because of this, one local backup user is a reasonable solution, but Microsoft is trying its best to prevent Windows users from creating a local account in the future. I am using windows server and logging into it, but it doesn't work or help to Windows Home version users. 99.9% have ended up reinstalling Windows or leaving the problem as it is. I don't, because I started to investigate the reason why the correct password is not valid for the places where it should work. From this we can conclude that the system administrator's passwords are stored in the recovery partition, because internet connection not needed, but a password is required. The recovery partition can be easily tested from Windows. Hold shift key down and select restart with the mouse. Revocery partition boot starts. The location is C drive or real revocery partition. In your case, the recovery partition should work, even if you delete the new created partition, because the recovery drive path leads to the C drive, where all the data is stored, if the C drive partition stops working, then the revocery feature can do the same. If you delete and create a new recovery partition, file copying starts on an empty partition when the partition is activated with the reagentc /enable command. If the recovery partition has been created incorrectly, then C drive starts to handle the recovery partition function (backup option for this fuction). It is safer if you know how to repair the real recovery partition. I suspect that the next target for hackers may be the recovery Ipartition passwords, if they can get their hands on them. About 1982 I got my first computer. So I know a lots of things that others don't. I using USB or bluetooth Yubikey 2FA security keys in all places where they work. I have 3 active USB keys. All accounts that can be locked if 2FA physical key is missing. I don't want to break you, so keep up the good work on the channel. If you play this information security game, there should be 3 keys. i have yubico 5 NFC keys and one 5Ci key for the apple products.
I've gone back to the laptop used and you're right - WinRE is using a folder on the C: drive and not the new partition. The reagentc /info command points to a Recovery folder on partition 3 - which is the main C: drive.
So I think WinRE b0rks as it tries to use the new partition, fails and so reverts to the C: drive because it's the only place it can use.
This fix does work, but not for the right technical reasons - and it won't work for everyone first time.
I'll make a video explaining this in the future.
😁
If the new partition type comes up as "Data" you can use Disk Genius (free) to change the identity to "Recovery" before carrying on. I spotted this and this how I fixed it.
Excellent tip!
I'll use this for the follow up video.
:)
Here's the follow up video...
ua-cam.com/video/3YSUF4pCr0o/v-deo.html
Been ignoring this error for months lol, this video fixed it! Thank you.
Glad I could help!
Thank you so much! Tried other fixes which exclusively use cmd and they didn't work. However following your simpler guide actually worked. Appreciate it!
Glad it helped. 🙂
This was my problem for months! Thank you so much, now it's gone! What a clever solution!
Glad it helped! 🙂
THANK YOU SO MUCH, IVE BEEN STRESSING FOR A FEW DAYS, you really helped me, it was messing with my vr a lot when I tried to play.
Glad I could help! :)
Dirty Fix really worked i can't believe it, thank you so much for your effort! I wish you all the best!
Glad it helped.
Watch the follow on if you’re interested. Link in the description.
It make the fix less messy.
🙂
I hope you receive the biggest check possible for this video thank you so much for this keep this up. People love to have videos like this when ever we need them and not enough people with these talents make them sadly.
Thanks!
Glad the video helped. 🙂
This was the fix for my Windows 10 Pro. It worked like a charm. Thank you so much, keep up the wonderful work.
Glad it helped. If you want make the fix a bit less messy then see the follow on video. Link in the description.
Thank you so much, finally a video that worked on the topic. You are the best!
Thanks!
Glad it helped.
Thank you so much!
This is the most useful and easiest way I found on UA-cam. Worked like a charm, and solved problem very easy in my case! Thumbs up for this tutorial.
Glad it helped! And glad it’s easier to follow than the other videos about this. 🙂
@@sterntechdaddy I saw few of your other videos, and I decided to subscribe. Keep up a good work! Greetings from Serbia! 😉
Thanks for the fix! Only video I found that worked 👍
Glad I could help.
Lets GOOO! The only video that was straight forward and the result was a success... Thanks!~
Glad it helped. :)
I actually can't even comprehend how grateful I actually am! I've not had Windows updated for months due to that I've had problems with monitors flickering or the second monitor won't even turn on, buzzing or humming sounds coming from my microphone when I'm playing on Steam, I'm kind of hoping this fixes that issue but either way I greatly appreciate your genius! Finally part of the windows updated club once again. 🙏💯
It probably won’t fix the sound issues… but Windows Update will be a lot happier.
🙂
Probably won't fix it no. I'll try it tomorrow, literally only happens when I play a game on Steam, so weird! Hey windows being updated is definitely a positive.
I followed the steps in this video and now the problem is fixed, thank you so much
Glad it helped. 🙂
I've had this problem for months now not knowing how to fix it and nothing worked. I came across this video and it solved everything. Thank you 🙏🙏
Glad it helped.
Yep, definitely the quickest and easiest way to fix it! Thanks alot finally get rid that annoying warning in my malwarebytes
Glad it helped. 🙂
Bruv, you really pulled my balls out of the fire here. As of march 13th 2:44 am central time I can say that this error is still an issue. Thanks for helping me get this sorted out. I subbed too. Cheers mate!
Glad it helped. 🙂
Omg after a long struggle and many videos this finally worked. Thanks you
Glad it helped. 😊
Wow! I would have saved a bunch of time if I had found you earlier. Awesome. Thank you and subscribed!
Glad I could help!
Thank you. This method fixed the error on my computer. I have a few others which I'm going to try it on.
Glad it helped. 😂
Wow I had a hard time figuring how this thing works now after watching this video it completely worked. Thank u so much you’re the best
Glad it helped!
Thank you!!! Windows support couldn't help me at all. This video helped me fix it.
Glad it helped!
The only method that really worked! Thanks a lot!
Glad it helped!
BRO!!!! I watched multiple videos on UA-cam. THIS IS THE ONE! AGAIN! IF YOURE HAVING THIS ERROR THIS IS THE VIDEO TO FIX!!! I watched multiple other videos regarding the CMD and followed the prompts on Microsoft page. NOTHING WORKED! THIS worked for me! THANK YOU THANK YOU THANK YOU THANK YOU! I wouldnt recommend any other video except this one, ive had this issue for months and its finally fixed! THANK YOU AGAIN!!!!
Glad it helped. :)
This comment was thee one that made me try this video!...I have been pulling my hair out trying to fix....will post update after troubleshooting
Hope it works for you too. 🙂
worked perfectly brother. thanks for this. subbing right now
Glad it helped and thanks for the sub.
🙂
Update 4441 successfully installed! Finally, a fix that worked! I'm moving on to your follow-on video. Thanks for the constructive video!😊
Glad it helped!
Thanks for this clear procedure
Thank you so much Nic! You helped me a lot!
Glad it worked.
Thank you so much for this solution🙏
Happy to help. 🙂
thanksyou man u r a lifesaver. i hope u made this video alot cause i had a lot of strange problem from my computer
Glad it helped. 🙂
Can u make a video about when i turn on the pc but it said no signal in the screen
Absolutely brilliant. Many thanks.
Thanks!
Thanks mate you have made a grown man happy 👏👍🏿
Glad it worked!
Love you bro, this solved my problem. Thank you. 😁
Happy to help!
The only video who really help me! Thank so munch!
Glad it helped. 🙂
thank you Nic, here it worked for me... I increased the partition to 500 MB and now everything is fine 🤗🤗🤗🤗🤗
Glad it worked.
Interesting how 500MB worked, but the laptop in the video initially had a larger one and it didn’t like it until 250MB was added.
Great info, fixed the issue!
Glad it helped!
You are a life saver. 100 percent use this tutorial it works.
Glad it helped. If you want make the fix a bit less messy then see the follow on video. Link in the description.
This worked 100% first time! Thank you! :D
Glad it helped!
thank you worked perfect, had this for ages and now i can rest
Glad it helped.
Awesome!!! Thanks, fixed my issue. Liked and subscribed.
Glad it helped!
google can't even solve their own problems but you are built different 🔥
Thanks!
The problem was solved with this method. thank you man❤
Glad it helped. 🙂
Wow! This actually worked. Thanks alot!
😁
Glad it helped!
This worked mate, cheers!
Glad it helped. Check the follow on video if you want to tidy up a bit.
it was really helpful , thank you so much
Glad it helped!
Thanks for the fix!
Happy to help!
Shout out to you man awesome video fix my problem and you're the best thank you
No problem 👍
amazing......Finally in this video I found the answer. and the update was successful. Thank you, I hope more people see the video.
Glad it helped!
Thank you so much Sir 😊
Glad it helped.
Thank you so much it fixed it for me!
Glad I could help!
Big help sir! Thank You!!!
No problem!
Glad it worked. 🙂
Tysm dude u possibly saved my windows
Glad it helped. Take a look at the follow on video though. It helps finish things of properly.
Thanks....its working rn good job 👏🏽
Glad it helped. 🙂
Excellent ! Fixed now thanks
Glad it helped!
Thanks a lot , it worked 😃, Great Job👍
Glad it worked!
Done, Its work ! thank you !!
Glad it helped. Read the description for the follow on video if you want to make this fix less messy. 😊
Thanks for this Nick. Been having this problem too with this KB5034441 but also KB5001716. I tried to include a screen shot of update history showing KB5001716 from October 2023 still refusing to install but exactly same KB5001716 with today's date installed successfully. Can't paste screen shot so you'll have to take my word for it. Anyway KB5034441 now installed.
Thanks again. Tony
Glad it helped. The error is a general error that pops up when the WinRE partition isn’t large enough to fit the update into. So you can get the error for several updates - as you know!
I’ll add this info to the description in case it helps someone else.
Man AINT NO WAY BRAHHH , U HELPING ME MANNNN , thx u so much , u my new tech hero bru
Glad it helped.
Perfect, thank you.
Glad it helped!
You're amazing thank you so much for this❤
Glad it helped. 🙂
Thanks so much it worked 👍
Glad it helped. 🙂
I can only say that you were great! ❤
Thank you! 😊
worked perfectly Thanks
Great to hear!
This fixed my issue. 👍💯
it worked, Thanks a Lot!
Glad it helped. 🙂
OH SHIT BRO THIS IS AMAZING!! THANK YOU THIS FIX MY PROBLEM!
💥💥💥
Glad it helped!
This guy is the GOAT🔥💯 thanks bro🙏
Glad it helped.
Wis suwun lik...mantep tenan sampean...
Bungah bisa mbantu.
:)
@@sterntechdaddy wkwkwkwk....
Thank you so much sir, it worked :)
Glad it helped. 🙂
IT WORKED THANKS ,Subbing rn
Glad it helped and thanks for the sub. 🙂
Thanks man. my laptop is now fixed😃
Glad I could help.
Great tutorial Nic Thx 4 that
Have a look at the follow on video… it’s a more technically correct tweak to this fix.
@@sterntechdaddy I will thank you 😊
Wow! This step by step guide provided was very helpful to. Thanks Nic... appreciate
Glad it helped.
God bless you
Everything worked perfectly after update successfully. Few minutes ago it came up again with this blue error Dog watch...
What is the error code?
You can perform repairs by using a Windows setup USB stick made with the Media Creation Tool if you can't boot to the desktop.
Memory management
Thank you very much.
Glad it helped. 🙂
Wow! Thank you, thank you, thank you!
Glad it helped. 🙂
Thank you…. I have this problem too… finally…
Glad it helped.
Bro thanks this method works for me ❤
Glad to hear it worked. 🙂
Thanks it worked 😌🙏
Glad it helped. 🙂
thank you!
Glad it helped.
Bravo best metode
I LOVE YOU THANK YOU!!!
Glad it helped. Take a look at the follow on video if you want to tidy up this messy fix a bit.
Cheers buddy! This one gave the Mac users their 5 mins of fame!!!
Macs are pretty famous already so I doubt this video contributed to that in any meaningful way.
😂
Thanks alot this fixed that update issue. If you don't do this update does it cause BSOD errors ?
Glad it helped.
There's no BSOD if you don't do this update - you just keep getting the Windows Update error. It's ironic that KB5001716 is an update for Windows Update components - it's just larger than some WinRE partitions can handle. The KB5034441 is a WinRE update that can also cause this error according to some of the comments on this video.
Personally, I've only encountered the KB5001716 error.
Microsoft might decide to fix it at some point.
:)
There was another Windows update error in the couple of days, not related to the recovery partition size (assuming the size was previously increased for the problem a few weeks ago). However, it appears that MSFT has fixed the latest problem with a new update.
I hope so!
It's the 9th March 2024 as I type, and I made this video a few days ago using a laptop I was refurbishing. It encountered the error during my usual Windows Update session - so if they have fixed it then they've fixed it very recently!
About time too... the common update that produces this error was released in January!
The error code actually refers to a 'not enough disk space' error so it might happen again. It seems the size of the WinRE partition varies!
As this fix is free and pretty easy to follow it’s worth trying before getting anyone else involved. It might work and thus save some money.
🙂
Thankyou bro 😊
Glad it helped.
Well Done! Great fix! Worked for one of my systems.
Thanks!
Glad it helped.
Thanks!
Glad it helped. 🙂
Thank you so much indeed sir, problem has been solved
Glad it worked. 🙂
3:40 if you have a lot of drives, you can look at the name of your boot drive on diskmanagement (the first step where you shrunk the volume) or another way is is when you type diskpart it will show free amount in mb. usually the other drives have 0 free.
DISKPART can be pretty scary, so a less technicdl way for people who don’t have your skills is to use Disk Management to view this information. It will show the partitions on a drive and label them as boot and system. It will also show the drive letter assignments.
The WinRE partition will be small and not have a drive letter which identifies it nicely.
Note that you can assign a drive letter and it’ll appear and be browsable in File Manager. Handy if you want the check what’s there.
🙂
Thank you so much
Glad it helped.
thank you !!👌😄
Glad it helped. 🙂
you're the man!
Thanks!
it worked thank you
Glad it helped. :)
holy fucking shit it really worked. Been unable to update this specific security update and this guide actually helped (ngl I was a bit skeptic at 1st) thanks a lot m8
Glad it helped!
i am struggling in 5:32 please help me
i entered reagentc /enable and it says The Windows RE image was not found. how to fix it?
Have a look in the description…
You can try opening an admin level CMD or Powershell and type sfc /scannow first to see if that helps.
OHH GOD THANKYOU SO MUCH IT WORK REAL BRO
Glad it helped. 🙂
OMG thank you sir it worked
Glad it helped. 😂
Hey, when I tried reagentc /enable it says "The Windows are image was not found ", what do I do?
Read the video description… 🙂
mine didn't work. it kept it in two separate unallocated partitions, one at each end of that disk management line. I turned the largest one back into WinRE.. how do I merge the two unallocated partitions,,, doesn't seem to be any way to do it in Windows
You can do it with DISKPART or a third party program like EaseUS Partition Manager.
But if you're not sure what you're doing then I would pay a tech expert to sort it for you.
Merciii🎉🎉🎉 ça a marché pour moii
Je suis content que ça ait aidé. 😊