Asklemmy

43965 readers

1885 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]

287

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]

120 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] 4 points 1 year ago* (last edited 1 year ago) (1 children)

That's because most people use them incorrectly. You need to run DISM first to repair the component store, but for that to work properly, you'll need source files/wim that matches the same OS patch level as that of the machine you're trying to fix. Once the component source is repaired properly, then run SFC, which would replace the corrupted system files from the now repaired component store.

If you ran SFC on its own, it may not do anything if the component store is corrupted, and if you ran DISM on its own, it won't fix the actual issue. You need to run both, in the proper order, against matching source files.

[–] silentdon 1 points 1 year ago

Thanks! I just learned something new!