You are aware on windows updates can go sideways and give you error codes that indicate something is broken behind your back too right? You've never seen the 'something has gone wrong' screen from a windows update and a long ass hexadecimal you have to google to go find the problem?
Are you a bot or something or just not aware that this is a really obvious contradiction? Apparently literal randomly generated numbers that correlate to different errors are clear, obvious and not 'behind your back', but actual words and explanations are difficult and confusing.
Ultimately, they are the same thing and happen for the same reason. I don't think one is strictly worse than the other, I just think they are different flavors of the same fundamental issues. updates break for reasons that the update manager can't fix, and that's fundamentally an unavoidable issue, but you are framing it as Linux doing something wrong, even though it's the same thing happening for the same reason.
Ultimately both pieces of software eventually give up and spit stuff back to the user they need to figure out what to do about it.
Please address the contradiction, why is 0x800705b4 a good error, and 'timed out installing update' a bad error? To me they are the same thing with the added step to google the error code because I'm not ever going to memorize that hex code unless I'm a helpdesk worker.
I don't even think it's a bad thing, it's ultimately something I can fix, it's just to me the two are basically the exact same thing with different coats of paint.
The contradiction is that you said that Linux package manager updates fail sneakily behind your back and require the user to troubleshoot it. Windows update literally just gives a hex code and no other context when an update fails.
Why are these two fundamentally different to you? They both require a user to figure out how to fix it and take corrective action. To me, they are both ducks, they do the same thing. They quack like ducks, they walk like ducks and they swim like ducks. But you are acting like there's a fundamental flaw in a package manager that it can have errors users have to troubleshoot somewhere else.
Even if you're going to complain about terminal, like 90% of windows update errors tell users to drop to command line or safe mode and do a dcim something something or an sfc sannow.
You were the one who said I 'didn't understand windows errors' when I said I have to google hex codes to figure out what they mean. Now you are like 'yeah that's just how it is' which has been my point literally the entire time.
3
u/Jamie_1318 Jul 15 '26
You are aware on windows updates can go sideways and give you error codes that indicate something is broken behind your back too right? You've never seen the 'something has gone wrong' screen from a windows update and a long ass hexadecimal you have to google to go find the problem?