this post was submitted on 13 Nov 2023
295 points (95.7% liked)

Asklemmy

43851 readers
896 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

Yeah, basically that. I'm back at work in Windows land on a Monday morning, and pondering what sadist at Microsoft included these features. It's not hyperbole to say that the startup repair, and the troubleshooters in settings, have never fixed an issue I've encountered with Windows. Not even once. Is this typical?

ETA: I've learned from reading the responses that the Windows troubleshooters primarily look for missing or broken drivers, and sometimes fix things just by restarting a service, so they're useful if you have troublesome hardware.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] AlijahTheMediocre@lemmy.world 9 points 1 year ago (2 children)

Windows's ability to troubleshoot itself or at least point you in the direction of a solution is non-existent. One reason I switch to Linux fully.

[โ€“] lightnsfw@reddthat.com 4 points 1 year ago (3 children)

You mean "something went wrong :(" is insufficient?

I know, right? It's 2023. They should really provide a QR code or something.

No, just spent the better part of half a day helping a friend troubleshoot his PC because it kept crashing when trying to game.

BSOD was useless, dug in logs to find the errorcode. Error code was some generic Nvidia driver had an oopsie daisy, all it confirmed was that it was a software issue. Spent next 3 hours finding and reinstalling drivers until finally reinstalling the chipset drivers seems to have resolved it.

[โ€“] Honytawk@lemmy.zip 1 points 1 year ago (2 children)

If you want more info, you just open up the Event Viewer.

It really isn't that difficult.

As mentioned in another comment, event viewer didn't get me much more than "Nvidia Driver crapped out", searching the bugcheck code lead to "heres several things that might fix it". In no way did it suggest that reinstalling the chipset drivers would resolve the issue.

[โ€“] lightnsfw@reddthat.com 1 points 1 year ago

But they could just put the actual event on the huge fucking screen instead of a worthless message with a frowny face. Or if not a page with instructions to access the event viewer so that inexperienced users know where to begin. Literally anything would be better than the current screen.

[โ€“] Honytawk@lemmy.zip 1 points 1 year ago

Say you have no knowledge about Windows without saying you have no knowledge about Windows...

Do you see all the comments on this post telling you it fixed their issues? Because I do.