Forum Discussion
KB5034441 fails to install with error code 0x80070643.
Microsoft's obvious objective is to destroy old computers. I understand the problem as MS sees it. My computer isn't broken, but you insist on fixing it anyway. Until you break it or set it up for some cyber-criminal to break it for you. And no matter how EVIL you get, there is nothing I can do about it. I hope to gawd I have purchased my last MS machine last year--but you have also destroyed my freedom to pick other options. Just too fricking bad I like freedom, eh? Just when I think I don't have to hate you so much...
shanen0 I'm sure the "you" you're referring to is Microsoft and not Susan Bradley. Susan is a long-time member of the IT community whose invaluable contributions have benefitted IT professionals everywhere. Susan isn't a Microsoft employee, yet she donates countless hours helping others to navigate the complexities of managing Microsoft products and services in an enterprise and small business environment. A true MVP.
We all understand your frustration, Susan included.
PRSGroupITNo, she seemed to make it fairly clear that she was speaking on behalf of someone else who apparently didn't want to be clearly identified.
SusanBradleyGeek It's a great article. Very in-depth and detailed ,and I think you're spot-on in your criticism of Microsoft for the way they handled this update.
I've found in most cases, the problem isn't that the partition is too small for the updated WindowsRE, but that it's too small to apply the update in-place. If WindowsRE is updated outside of the recovery partition, it can be returned with space to spare. The method I described above, which may not work in every case, temporarily moves the WindowsRE files to the system (C:) drive where the update can succeed--providing C: has adequate space--then returns the files back to the hidden recovery partition.
I'm not sure if space would be a problem if we mount the recovery partition and perform an in-place, offline update to Winre.wim, but if so, the file could always be manually copied out, updated offline, and copied and back in. Microsoft supports offline updates using dism (https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11).
I can't imagine why Microsoft released the update that created this problem in the first place, but it's even more puzzling why they recommended a solution that involved a risky process of resizing a system partition and deleting the recovery partition.
- I'm speaking on behalf of everyone dealing with this update and the frustration we all have. We're on month two with no good resolution other than potentially destroy your computer. I was trying to be diplomatic about my feedback. What I said here: "What you are asking your Microsoft patchers to do with this update is not acceptable and not attainable by your Windows 10 patching audience." still stands. This is feedback TO Microsoft.
