xDiVolatilX
2[H]4U
- Joined
- Jul 24, 2021
- Messages
- 2,550
Yea tried to update my daughter's Win 10 PC and the update is still errored and won't install.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
thats not the topic update nor the replacement, and it looks like its installing...
same what?Same here on two installations of Windows 10 21H2 LTSC (one physical and one virtual)
I fix this by running the windows update troubleshooter. Many work computers.View attachment 635957
During the January update round MS issued a security update for Windows 10 that should fix a security issue which could allow an attacker to bypass Bitlocker encryption using the Windows Recovery Environment. Except the update throws an unexplained error code for many users: 0x80070643. As it turns out the error is caused by MS changing how WinRE is updated from now on: cumulative updates instead of small patches. Except for many users when they originally installed Windows 10, the installer was not prepared for this so the automatically created Recovery partition is not large enough to apply this update out of no fault of their own.
Since then MS has issued a manual workaround for installing the update. But the workaround involves resizing your system and recovery partitions, so it is only recommended if you are desperate to have this update installed and know what you are doing.
Most people were hoping that in the February patch Tuesday MS would sort out the issue properly, but unfortunately that's doesn't seem to be the case. The erroneous patch hasn't been pulled and no updated version was issued. It is unclear when can we expect MS to properly fix the issue instead of a workaround that is risky even for enthusiasts.
Until now the issue was a mere inconvenience, but since you can't opt out of the broken update even if you don't use Bitlocker, it can interfere with the installation of any further updates as well, as it tries to install it first, but fails blocking the entire update process.
Windows 10 KB5034441 is still broken with 0x80070643 error
There is no replacement. KB5034843 is an entirely unrelated "quality" update.thats not the topic update nor the replacement,
sureThere is no replacement. KB5034843 is an entirely unrelated "quality" update.
I used to have this problem with an x99 motherboard but it went away with am4.Just because you don't encounter something doesn't mean the problem is not widespread. You can't do an in-place upgrade if you are already on the latest version of windows. Also not sure if that would be a guaranteed fix.
I have had the same issue with multiple mice, and it's not that the mouse is moving on its own or drifting (I'd cut my wrists if the $200 mouse was drifting). The mouse itself goes to sleep mode, so it is out of the question that's the problem. The only way I can get the monitor to properly time out is if I disable the ability in device manager for the mouse to wake up the computer. I couldn't even manually put the computer to sleep before I did this, as it would just immediately wake up again.
Don't remind me how finicky the X79 and X99 boards were especially the BIOS and USB settings were rough lolI used to have this problem with an x99 motherboard but it went away with am4.
Not sure, fact. Even after installing KB5034843, KB5034441 still shows up and gives an error. So it neither supersedes the update, neither does it fix the issue preventing KB5034441 from installing.sure
it (KB5034441) fails to install, sorry for the missing contextsame what?
sureNot sure, fact. Even after installing KB5034843, KB5034441 still shows up and gives an error. So it neither supersedes the update, neither does it fix the issue preventing KB5034441 from installing.
I had this update fail on a fresh install i did for windows 10 pro this week. Mind you the install media usb image im using is prob a 6+ year old version of windows if that matters. I did the recovery partition resize and that didnt fix it so i just installed w11 instead lolsure
what ive found on the units ive done, this update works fine if its a fresh new install of windows. if you have an oem system with their install, it tends to fail. ive also have seen it completely skipped.... either way, if its failing on you, just ignore it, not the big of a deal in the first place.
yeah 6+ is a little old...I had this update fail on a fresh install i did for windows 10 pro this week. Mind you the install media usb image im using is prob a 6+ year old version of windows if that matters. I did the recovery partition resize and that didnt fix it so i just installed w11 instead lol
I hidden the update.
Seems to be their way of thinking since they pushed 10 out the door. Maybe 8 but I'm not familiar with their update strategy there.It seems Microsoft's solution to the problem is to just ignore it exists.
And I ran out of patience so I hidden the update.
Microsoft has confirmed that it won't provide an automated fix for a known issue causing 0x80070643 errors when installing recent Windows Recovery Environment (WinRE) updates.
The problematic updates were issued during the January 2024 Patch Tuesday to fix CVE-2024-20666, a BitLocker encryption bypass vulnerability that allows attackers to access encrypted data.
The issue impacts Windows 10 21H2/22H2 (KB5034441), Windows 11 21H2 (KB5034440), and Windows Server 2022 (KB5034439).
On affected systems, it mistakenly shows generic '0x80070643 - ERROR_INSTALL_FAILURE' error messages instead of the correct CBS_E_INSUFFICIENT_DISK_SPACE error on systems with a Windows Recovery Environment (WinRE) partition that's too small for the update to install.
Microsoft first acknowledged this known issue in January, days after widespread reports from Windows users of 0x80070643 errors and the installation failing.
In all fairness would you trust Microsoft to automatically repartition your drives to expand out the one volume and not fuck over the rest?
In all fairness would you trust Microsoft to automatically repartition your drives to expand out the one volume and not fuck over the rest?
I would fear an automated fix.
It’s not super challenging, but depending on the machine the storage type, the amount of free space, what they may or may not have running when those updates are running, it could get messy. For you or me or anybody else who manages to find this post, it’s a relatively trivial task.Apparently Microsoft doesn't think they can fix it, which is odd, because resizing a partition really isn't that challenging:
https://www.neowin.net/news/microso...0-kb5034441-0x80070643---errorinstallfailure/
Sounds more like they just want people to switch to Windows 11, and want to make living with Windows 10 as difficult as possible.
It’s not super challenging, but depending on the machine the storage type, the amount of free space, what they may or may not have running when those updates are running, it could get messy. For you or me or anybody else who manages to find this post, it’s a relatively trivial task.
For the average Windows user and god help them the below average Windows user, that could go very sideways very fast.
I can see it now, thousands of users who had an expired Norton install paired with a free AVG install on some cheap SSD and too little ram with god only knows what 3’rd party apps running in the background letting Microsoft automatically repartition the drive to do an update.
If that’s not a recipe for an unbootable system then I don’t know what is.
The nature of this one is working specifically with encrypted drives. I’m not sure I would risk that real time, I’d probably remove the bitlocker encryption change the partition then re-enable the bitlocker.While that is true, I guess my take is, I have noticed Microsoft rooting around on my drive, resizing the main partition, creating recovery and other reserved partitions that didn't used to be there and generally messing with things.
So, I feel like they are already doing this. How much riskier would it be to do it for this one patch?
It affects W11 too. They just don't want to take responsibiilty for their F up. It's far easier to tell users you are on your own, risk is yours, than releasing a fix that might cause data loss. I bet you 50 cents they made the tool to fix it long ago, just decided not to publish it.Apparently Microsoft doesn't think they can fix it, which is odd, because resizing a partition really isn't that challenging:
https://www.neowin.net/news/microso...0-kb5034441-0x80070643---errorinstallfailure/
Sounds more like they just want people to switch to Windows 11, and want to make living with Windows 10 as difficult as possible.