The other day: I’m trying to export my emails in outlook to a pst file. While it’s running, everything is ok, if the computer locks itself then something shuts off outlook, but the export process prevents it, but the export process also somehow stops working. How the fuck do you troubleshoot that?
Bonus: it keeps saying “3 minutes remaining”, sometimes 8, sometimes 2, sometimes 6. Process has been running for an hour and a half at that point.
Another one: absolutely no way to access my file share with windows 11. And I’ve tried everything under the sun. Registry hacks, new shares, smb versions, firewall settings, … Whatever.
As if Windows coughed up error messages. More like “How to fix spinner never stop spinning?”
Back in the day, the blue screen hex codes were actually insanely useful for debugging. Honestly? I think most (all?) linux distros could learn a lot from ACTUALLY showing the error when the machine dies a horrible death rather than assuming people will dig through the right log files before they rotate.
But I know a few years back (… so probably over a decade) they started having QR codes instead. Which sounded awesome until you try to use one and realize they all go to the same generic help page. Not sure if the hex codes were still there.
I think most (all?) linux distros could learn a lot from ACTUALLY showing the error when the machine dies a horrible death
Linux recently DRM (Direct Rendering Manager, not copyright protection garbage) subsystem recently gained the ability to do something even better.
It can render a QR code containing debug information and kernel logs.
https://github.com/markusfisch/BinaryEye
Default apps tend to suck at recognizing big codes.
Yeah. Heard about that, never seen it in action.
I think part of the other problem is that Linux, in general, is meant for servers. So if anything functions, keep on chugging and rely on external monitoring to alert the user. Only acknowledge failure when all hope is lost.
Which is great for a server, not so much for a desktop where you might realize kde plasma fell over at 15:22 because you can’t click to a new window and the clock hasn’t updated since then (in fairness, I expected that when I finally installed openrazer). Nothing a reboot can’t fix but it still makes debugging a lot more tedious.
Not sure of a good way to handle it, but it would be wonderful to get stuff like that sooner rather than needing to wait for a full on kernel panic catastrophe.
And, in fairness, when I have to deal with a windows PC I have definitely noticed that MS changes the frequency of blue screens a lot from year to year. Back in the day, even a slightly wonky mouse driver would instantly trigger one. Then sometimes it feels like every single service could fail and it still wouldn’t pop one.
I think they stopped showing hex codes by default and just had error messages instead (I think hex codes can be turned on with the registry), it was still quite helpful, I’ve never been given a useless error but I think they were recently trialing removing error codes as well. I don’t know if they actually did that, I stopped using windows a few months ago.
*scans QR code*
welcome to the Microsoft troubleshooting website! What is your issue?
I DON’T FUCKING KNOW, YOU’RE THE ONE WHO BROUGHT ME HERE!
Has all the hallmarks of a good idea that never got properly implemented.
Google-fication comes for us all.
