Asklemmy

44196 readers

1159 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!

Open-ended question
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.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

305

Has Windows startup repair or a troubleshooter ever fixed your issue even once? (midwest.social)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

127 comments fedilink hide all child comments

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

[–] [email protected] 3 points 1 year ago

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.