Asklemmy

43974 readers

685 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
!lemmy411@lemmy.ca: a community for finding communities

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

founded 5 years ago

MODERATORS

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 SwingingTheLamp@midwest.social to c/asklemmy@lemmy.ml

126 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

[–] kuneho@lemmy.world 54 points 1 year ago* (last edited 1 year ago) (4 children)

strangely Network Troubleshooter always helped me when I was out of ideas why the network just... stopped working

tho never said the problem, things just got fixed in the meantime while it analyzed n shit and then it reported no issues :P

[–] dmention7@lemm.ee 35 points 1 year ago (3 children)

That one usually is successful by disabling your network adapter, then re-enabling it. Basically....

Have you tried turning it off then back again?

[–] USSEthernet@startrek.website 4 points 1 year ago

I believe the troubleshooter also does a WINSock reset as well. I'm not sure, though. I know it definitely disables/enables the adapter.

https://www.howtogeek.com/785351/how-and-why-to-perform-a-netsh-winsock-reset-on-windows/

load more comments (2 replies)