41–50 of 223 posts
i remember reading years ago about the reason windows updates since 8 or 10 were so bad was because MS fired all testers and scrapped their testing hardware and now they are testing virtually in cloud. I guess nothing has changed, still. cost cutting at its best.
Had the journalist tryied Linux, would have known that it gives much better error messages than some random looking number.
Glad to see that Microsoft is making Windows more and more similar to Linux by every passing day :)
Yeah, this isn't Linux. Linux is better than this these days.
Every time I've tried Linux, I've had to dive into the terminal and paste commands from the internet to get normal things to work.
My win10 kept giving me “bug check” reboot treatment and I had to go win11 reluctantly. Oh well, there goes my vertical taskbar.
What did the author want, a button to push for each solution to every possible exotic error, even critical ones that would require to resize a system partition from a running OS? Seriously!? Of course one solve this through the command line.
Or, if that wasn't what the author meant, then he may have to upgrade his Slackware 4.0 install, because a thing or two have changed in the Linux world.
Earlier quoted context omitted.
Yeah, this isn't Linux. Linux is better than this these days.
Except for if you want to use dual monitors, etc. etc. Every time I've tried Linux, I've had to dive into the terminal and paste commands from the internet to get normal things to work.
My win10 kept giving me “bug check” reboot treatment and I had to go win11 reluctantly. Oh well, there goes my vertical taskbar.
Had the journalist tryied Linux, would have known that it gives much better error messages than some random looking number.
Exit code 139. Hm.
As daunting as the fix seems, I appreciate them offering any at all; couple years ago when an update broke ReFS arrays for more than a handful of people, we were never given a solution beyond rolling back, until the update eventually became required and uninstallable, necessitating rebuilding the array from scratch
We should hold Microsoft accountable for borking installs and coming up with a half-assed fix even if it is a complex problem. They're in the lead on the desktop OS market and make billions upon billions of dollars that way. They should do better.