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

Posted by RiceeeChrispies@reddit | sysadmin | View on Reddit | 27 comments

[Article from Bleeping Computer](https://www.bleepingcomputer.com/news/microsoft/microsoft-wont-fix-windows-0x80070643-errors-manual-fix-required/).

Reply to Post

27 Comments

[-]

rms141@reddit

>"The WinRE partition requires 250 megabytes of free space. Devices which do not have sufficient free space will need to increase the size of the partition via manual action." Well... yeah. Microsoft can't patch more storage space on your disk.

[-]

fadingcross@reddit

Well... Yeah. But a regular out of box Windows Server install comes with a too small partition if not changed by the user installing the system. So they made it themselves.

[-]

TrantaLocked@reddit

I mean apparently any install does. My clean Windows 10 Pro installation made last year made a 530MB partition that's allegedly too small too? So no stock Windows 10 computer works with an update made for Windows 10?

[-]

Ferretau@reddit

> Well... yeah. Microsoft can't patch more storage space on your disk. True - but they created the update and should account for customers machines that do not have the space and be able to accommodate it instead of just failing and going ahh well its broken. Especially when they push update out and it won't opt out.

[-]

Thotaz@reddit

No, but they could update the update to take the low disk space into account. Assuming a default partition layout from the installer like: EFI, MSR, Windows, Recovery they could move the recovery image to C:\, delete the partition, shrink C:\, Recreate the partition, move the recovery image over. Alternatively, if it just needs 250MB more during the installation as the files are being updated they could make it use C:\ as a scratch drive instead of the recovery drive. I could understand them not being willing to fix this if it was a non-standard config but them not bothering to find a solution that their default configuration has caused is ridiculous.

[-]

andrew_joy@reddit

You want a windows update to mess around with partitions ? You are a braver man than me .

[-]

LibtardsAreFunny@reddit

probably why MS said fuck no.

[-]

TaiGlobal@reddit

While technically this sounds great im not sure I want Microsoft resizing partitions for windows updates. Sounds like it will only make the problem worse. Now I understand why my previous environment removed recovery partitions from the image entirely.

[-]

Distinct_Spite8089@reddit

I’d bet most everyone has plenty of space, Microsoft made their dumb partition too small and didn’t account for any future patching needs. What a ridiculous oversight and lazy “solution” to make your customers go resize it.

[-]

lxnch50@reddit

Yeah, just start resizing partitions for the users. What could go wrong?

[-]

Distinct_Spite8089@reddit

No one is saying resize a partition for the user, make the update smaller ?

[-]

disclosure5@reddit

Their own disk images in Azure, as of last week, ship out of the box with "all updates applied". They have the April CU and .Net updates applied, but this one is not applied and the image they build does not have the resources for this three month old update to install. I would totally understand if these small disks were an end user's fault, but even "doing everything right" leads you to a box that can't install this update.

[-]

jamesaepp@reddit

I agree..... ....BUT Microsoft has published system requirements for a reason. If the system doesn't operate as expected and cannot be updated when we meet the system requirements....what the heck are they for?

[-]

osxdude@reddit

Fixed it in a server image. It’s pretty straight forward. Changing partitions attributes isn’t something one would want to be liable for if something goes wrong. And, in a corp, easy to automate anyway.

[-]

TrantaLocked@reddit

then make an update that works without changing the existing partition that Windows 10 chose to make?

[-]

DonCBurr@reddit

old old news

[-]

bfodder@reddit

There was an assumption that eventually Microsoft would fix it. It wasn't until now that they confirmed they won't.

[-]

DonCBurr@reddit

guess my point is that I don't know anyone who made that assumption and have moved on and put this is the rear view mirror

[-]

RiceeeChrispies@reddit (OP)

Not really, the update was only posted by MS on 30-04.

[-]

DonCBurr@reddit

KB5034441 was released months ago ...

[-]

RiceeeChrispies@reddit (OP)

Correct, but this statement from Microsoft was released three days ago.

[-]

Distinct_Spite8089@reddit

Wow Microsoft great look for your LTSC/IOT customers….wtf maybe for Windows 11 LTSC make the stupid recovery partition big enough for any future needed patches. Acting like users made a mistake and can just manually fix your screw up is beyond ridiculous.

[-]

RiceeeChrispies@reddit (OP)

Removing the WinRE partition still causes the error, even though it’s not vulnerable.

[-]

redstarduggan@reddit

Haven't seen any tbh