Bork Tuesday, Any Problems Yet?

Thankfully aok here W11P. Cause I goofed. I know better than to install updates in the first week of release.

 

I updated 4 Windows 11 PCs today and a Server 2019 Domain Controller. No issues so far. Will roll out the rest tomorrow but no Windows 10 PCs left so I am not expecting any issues.

 

Just updated 11 here with no problems... will update my other dual boot 10/11 machine tomorrow... so far so good.

 

I guess I am one of the lucky ones. I had no problem with KB5034441. FWIW, I am on W10 Home, and my system has the Recovery partition.

Good luck to you guys having this annoying issue.

Bo

 

No problems here either.

 

Further to my earlier posts, KB5034441 installed quietly on it's own on one of the four win 10 machines it failed on earlier - this was without any re-attempt to install it manually (I saw no point as this approach had failed on 2 other machines) or doing anything to bitlocker or recovery partitions.

Hopeful that it had been fixed back end, I just tried on the other 3 it failed on. No go.... same error code on those (which all HP 10th gen machines, though I doubt that has anything to do with it, as the XPS is also a 10th gen & also has bitlocker enabled).

 

What's the size of your recovery partition?

 

It is 874MB.

Bo

 

https://www.tenforums.com/windows-1...ndows-10-21h2-22h2-jan-9-a-3.html#post2598604
https://www.tenforums.com/windows-1...ndows-10-21h2-22h2-jan-9-a-3.html#post2598623

 

Same issue with KB5034441 on Windows 10. Will wait and see if it installs silently.

 

Yip, I'm just gonna leave it. KB5034441 install failure, 0x80070643. Win 10 Pro and Home.
SFC clean, before and after. Tried NVT Win Update Fixer 1.5.

 

Same here, KB5034441 failed to install, install failure 0x80070643. Windows 10 Pro. Microsoft really screwed up with this update!

 

I succeeded in installing KB5034441 following CAREFULLY the instructions on https://support.microsoft.com/en-us...e-update-400faa27-9343-461c-ada9-24c8229763bf , (that I see now applies to Windows 10) shrinking by 250 MB the OS partition and creating a new "recovery" one
Now the "recovery" partition is 813 MB (marked as Primary and no more as "Recovery", I don't know if it makes difference)

I may suspect that the minimum required size is 800 MB

PS
Note that the partition has 98% available space....

 

They sure have. Same problem here on my Win 10 Pro.

 

Macirum, saves the day.

 

Not going through that BS, will wait till they fix, not that important.

 

+1

 

I'm sure glad my main computer isn't M$ Windows.
I'll wait until M$ fixes the problem on my Win 10.

 

I didn't have problems with the updates, but probably because I already increased the size of the RE partition in the past (because another update for Secure Boot required it).
So this update installed successfully. To be honest, my RE partition is merged with my system drive (and it's not a separate partition) but all went ok.
Creating a new RE could be tricky and requires a lot of commands and understanding of bcdedit, reagentc, diskpart. Etc. Good luck everyone.

 

Yeah, I had the same file. Probably because my RE partition is merged with my system drive.

https://superuser.com/questions/1302986/what-is-this-file-winre-backup-partition-marker

Just checked the Disk Management - it seems that I split the RE partition, and now it's a separate partition (1 GB in size). Oh well, anyway. Didn't remember doing it, but probably I rebuilt it in the past.

 

No issues with Windows 11 updates.

 

I'm starting to think Microsoft is run by a bunch of AI bots, seriously.

 

That's a terrible thing to say about AI bots...

 

Yeah, AI bots might be able to run it better. lol