Microsoft won't fix Windows 0x80070643 errors, manual fix required : technology

[-] thurstylark@lemm.ee 74 points 7 months ago

Waow. MS can't decide if their users should have control of their hardware or not.

Your linux bootloader and efi config? That belongs to Windows, and it will make changes as much as it wants. A recovery partition that has no usefulness outside their own ecosystem? Yeah, they know it's fucked, and they fucked it, but it's your computer, you fix it!

[-] LordPassionFruit@lemm.ee 39 points 7 months ago

Simple. It's theirs when it works and yours when it doesn't.

[-] deweydecibel@lemmy.world 8 points 7 months ago

Their when it works and it's profitable.

[+] wizardbeard@lemmy.dbzer0.com -12 points 7 months ago

Not dickriding microsoft here, but they have provided all the tools to fix this. They just can't make them happen automatically on effected machines because they broke something particularly complicated.

You need to have enough space to resolve the issue (which was caused by not having enough space in the recovery partition in the first place). You need to adjust the size of the parition (traditionally a risky operation, especially through Windows). You then need to download a specific update while skipping another, install, and reboot.

They have provided scripts for backing up the recovery partition, expanding it, and restoring the contents from backup if expanding fucks the contents. They have provided a script to download and install the specific update to fix the problem once you have enough space in that paritition. They did not automate restarting the computer (piss easy to automate), or to hide the problematic update (easy through UI, probably a pain to script).

[-] thurstylark@lemm.ee 21 points 7 months ago

I agree that if there was enough space in the recovery partition to begin with, this wouldn't be a problem, but the user isn't the party that specified that size or the party that decided to add enough stuff to the recovery partition to exceed that spec.

MS knows that this is a widely-deployed configuration (they deployed it), but they're going ahead with an automatic update that is incompatible with that configuration anyway, failing to communicate to the user why the failure occurred, and refusing to automate a fix to the thing their automation broke in the first place.

[-] kungen@feddit.nu 13 points 7 months ago

But the partition is Microsoft's own, basically no one has ever touched it themselves. So why can't they do some housecleaning to make enough space? At the very least, they could fix the error messages to be more descriptive on how to fix it.

The tin-foil in me says it's just a tactic to get people to switch to Windows 11. "Oh, I have errors with my updates? I should really try upgrading and see if that fixes it, I don't want any hackers to steal my megabytes..."

[-] n3cr0@lemmy.world 29 points 7 months ago

A recovery environment is overrated under Windows. Just backup your files and reinstall from scratch.

[-] Crackhappy@lemmy.world 18 points 7 months ago* (last edited 7 months ago)

I've been using windows since windows 3. The number of times I've used the "recovery" feature is exactly zero.

Edit: Corrected by another user below. I have used it a couple times for update rollbacks, I just haven't used it for a full recovery. When I've run into serious issues I just reload it from scratch, as I keep data and OS on completely separate drives.

[-] Buelldozer@lemmy.today 15 points 7 months ago

The number of times I’ve used the “recovery” feature is exactly zero.

The RE Partition is for more than Recovery. If you've ever uninstalled an update then you've used the RE Partition.

[-] Crackhappy@lemmy.world 4 points 7 months ago

Very good point! Then I have used it.

[-] n3cr0@lemmy.world 2 points 7 months ago* (last edited 7 months ago)

In this case I'm happy I always installed Windows without RE partition. It works fine and you can still uninstall updates. Broken system files can also be replaced by a fresh pull from Windows Update.

[-] subignition@fedia.io 6 points 7 months ago

Lucky for you! Twice over the years I have had Windows 10, the system failed to come back up after a windows update and the ability to uninstall the most recent update through the recovery partition saved me.

[-] possiblylinux127@lemmy.zip 3 points 7 months ago

It recovers in the background with no user intervention when things go wrong.

[-] wizardbeard@lemmy.dbzer0.com 11 points 7 months ago

It's more than strictly a recovery partition. It is also used for updates and the files needed to roll individual ones back. The entire issue was that they had an update that didn't properly handle when there wasn't enough space for it in the recovery partition.

[-] catloaf@lemm.ee 5 points 7 months ago

Yeah, I have it turned off on all my machines (mostly because of that vulnerability a few months ago).

I have never been in a situation where it was useful, nor have I ever had it work when I tried it.

[-] claytonburns@lemmy.world 13 points 7 months ago

I have run the script with mostly success. A few computers had the script fail because WinRE was corrupt, or missing, or whatever. You would think that if WinRE wasn't present, the update would be skipped and not repeatedly notify you that it failed, but that's Microsoft for you.

[-] Buelldozer@lemmy.today 11 points 7 months ago

Anyone tried and succeeded?

Shiiit, I have a powershell script for this. Takes 90 seconds or less to fix it on systems with an SSD. Takes 2-3 minutes on HDD systems. I've done hundreds of times since the January 2024 update.

[-] frantic6423@lemmy.world 5 points 7 months ago

Care to share?

[-] Buelldozer@lemmy.today 8 points 7 months ago* (last edited 7 months ago)

You can literally copy / paste either of these commands into an elevated Powershell session. They create the directories needed, go fetch the script from Github, then execute it with the necessary arguments. I've run this on Windows 10, Windows 11, and all Windows Server versions from 2016 through 2022.

This is a “Confirmation” version. It will stop and prompt you before actually changing anything.

[System.IO.Directory]::CreateDirectory("C:\winrebackup"); [System.IO.Directory]::CreateDirectory("C:\tcmds"); cd c:\tcmds; Invoke-WebRequest -Uri https://raw.githubusercontent.com/Bash-OverRide/UseFulScripts/master/winre.ps1 -OutFile ./winre.ps1; dir; ./winre.ps1 -BackupFolder c:\winrebackup

This is a “No Confirmation” version. If the WinRE partition needs expanded it will just do it.

[System.IO.Directory]::CreateDirectory("C:\winrebackup"); [System.IO.Directory]::CreateDirectory("C:\tcmds"); cd c:\tcmds; Invoke-WebRequest -Uri https://raw.githubusercontent.com/Bash-OverRide/UseFulScripts/master/winre.ps1 -OutFile ./winre.ps1; dir; ./winre.ps1 -SkipConfirmation $true -BackupFolder c:\winrebackup

You may see a reboot warning if you have un-applied Windows Updates. In nearly all cases you can safely ignore the warning but the decision is up to the user.

If it fails with an error about insufficient space to resize the partition and your storage isn't full then it's likely that you have immovable files at the end of the primary partition. Turn off Hibernation and System Restore, which will remove those files, then reboot and try again. Remember to turn Hiberation and / or System Restore back on when done. I've only seen that happen a couple of times which is why it's not scripted in, just wasn't worth the effort.

[-] Nougat@fedia.io 6 points 7 months ago* (last edited 7 months ago)

I have done this multiple times on servers. It's beyond simple and doesn't take but a few minutes. Follow the instuctions and you're gold.

Edit: In short, you use diskpart to resize the boot partition down, then use diskpart again to resize the recovery partition up with the space you created in step one.

[-] Creat@discuss.tchncs.de 11 points 7 months ago

Or you just runs the ps script provided by Microsoft. 1 line. No clue why they can't do that themselves for affected systems...

[-] catloaf@lemm.ee 3 points 7 months ago

Change board says no

[-] possiblylinux127@lemmy.zip 1 points 7 months ago

You could just free up space in the recovery partition

[-] shundi82@sh.itjust.works 6 points 7 months ago* (last edited 7 months ago)

I'd done this some time ago via console.

My RE partition had sat before my main partition - and since you can't shrink partitions at their start (left) with fdisk and I didn't want to boot up a Linux pen drive, I just shrank the main partition at its end (right) and moved my RE partition to the now freed space at the end.

I've made the old RE partition available, but since it's just a few hundred MB, I doubt I'll ever actually use it. :-P

PS: If you do it via fdisk, just make sure you first enable the new RE before disabling the old RE. Otherwise there's nothing that can be copied to the new RE - I've made that mistake and had to get the missing files from a Windows ISO.

[-] ColeSloth@discuss.tchncs.de 5 points 7 months ago

I did all this lovely manual bs to get rid of an update error about a year ago. This one I just said "fuck it" and have left it ignored. I don't get on windows often enough anymore to waste my time on it. About all it gets fired up for is when my kid wants to play fortnite with me.

[-] Burn_The_Right@lemmy.world 4 points 7 months ago* (last edited 7 months ago)

I was able to fix it using a free open source download called "Mint". In fact, Mint permanently solved all of my Windows problems!

[-] OfficerBribe@lemm.ee 2 points 7 months ago

Have run their provided script on one device and it worked like a charm. Think it was this one.

[+] MonkderDritte@feddit.de 1 points 7 months ago* (last edited 7 months ago)

[deleted]

[-] SharkAttak@kbin.social 1 points 7 months ago

My recovery doesn't work and I don't know why and since when, so it's a sorta of non issue for me.

[-] Heavybell@lemmy.world 1 points 7 months ago* (last edited 7 months ago)

I did this ages ago now. Was a non-issue.

Edit: To clarify, I'm not endorsing MS on not fixing this. Just saying I did it and had no issues.

[-] possiblylinux127@lemmy.zip 1 points 7 months ago* (last edited 7 months ago)

I just cleaned the entire partition with disk cleaner and manual deletion of the files.

[+] aniki@lemm.ee -15 points 7 months ago

Tips to avoid destroying a partition and having to reinstall the os?

Start with a file system that doesn't suck, like ext4, bless the drive with a boot loader that doesn't suck, like Grub, and then get yourself a kernel that doesn't suck, like GNU/Linux, then get yourself a software stack that doesn't suck, like Arch.

I use Arch, BTW.

[-] FaceDeer@fedia.io 37 points 7 months ago

OP asked "how can I accomplish goal X?"

You responded "Goal X sucks, you should accomplish goal Y instead!"

That's not exactly useful.

[-] NekkoDroid@programming.dev 2 points 7 months ago

bless the drive with a boot loader that doesn’t suck, like Grub

Ah yes, I need a whole separate OS just to boot my actual OS...

I would in no world call GRUB a bootloader that doesn't suck.

Technology

Our Rules

Approved Bots