Asklemmy

43989 readers

1429 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] 1 points 1 year ago (1 children)

Unless you do the online command so it pulls the most recent wim and does it on its own. I've got a batch file I use to fix computers at work that does the online dism followed by sfc and have had a few successes with it.

[–] [email protected] 1 points 1 year ago (1 children)

Nah, I’m currently trying to fix a PC that is so borked, that not even a clean install.wim can fix. According to some sources, there are some packages missing in current installation medias, that are not needed for the installation, but you cannot repair a borked install, if those are affected. This seems to be the case since at least somewhen in 2021, from which I found the earliest reports. Oh… and they aren’t in the online image as well. So if those break, you can only do a clean install.

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

The trick to a successful DISM though is matching the broken system's patch level with that of the source files. DISM basically repairs your component store using the source, so for it to work properly, you'd want to use the same OS patch level store as the source. I used to keep a few good Windows VMs at different patch levels for this purpose. I'd then patch the VM up to the same level as that of the broken machine (if needed), and then use the good VM as the DISM source.

In any case, if DISM keeps failing, then a repair install (aka in-place upgrade) usually does the trick.