"Linux is only free if your time is worthless"
There are more of these stupid slogans. My experience is that you will run into problems that cannot be easily solved – or not without looking it up online – on all operating systems.
Sooner or later it will happen. Windows in particular is complete garbage when it comes to meaningful error messages.
How the f… is anybody supposed to interpret "0x80070643" as "Not enough free space in the recovery partition"? Are you insane at Microsoft HQ? What is wrong with you?
Windows Update just throws this nonsense number. "Something went wrong. We will try again later." → "Something went wrong. We will try again later." → "Something went wrong. We will try again later." →…
I've looked it up online. Of course. The number is useless as such. Old results. New results. Results for .NET Framework. Seems to be a generic error. Great!
For f…s sake, tell me *WHAT* went wrong! A refined search with KB5034441 showed new results and a link to this old help article on MS Homepage.
This article is for an extremely old version of Windows 10. My installation is latest version, just a few weeks old installed with default settings on an old 128GB SSD. And the Windows installation program automatically set the recovery partition size to 50MB (!) only. Didn't they take the previous problems in account? Having 250MB more or less for drive C:\ isn't a crucial problem. My data is stored on HDDs.
On the very first occasion after initial installation Windows Update fails.
Why? Why? WHY? To hell with this! Windows rubbish!
I've experienced a very similar problem on Android a few weeks ago (no error message, manual partition resize required).
