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.

40 points

Yes it has.

I used to have a sound issue and the repair wizard would always fix it. It would happen again, I think after the next reboot.

permalink
report
reply
5 points

I feel like I’ve seen a unicorn!

permalink
report
parent
reply
7 points

I’ve only ever had it fix a sound issue, as well. Bad driver?

permalink
report
parent
reply
0 points

This was nearly 20 years ago, i really do not recall what the issue was, order of if I ever fixed it. I may have replaced the card or something.

permalink
report
parent
reply
1 point
*

Sounds a bit like the repair tool broke the sound everytime itself you shut down to polish its image

permalink
report
parent
reply
1 point

Possible! I have also used it when I disabled my network and it was quicker to run the repair tool than it was too try and remember what exactly i had done to disable it.

permalink
report
parent
reply
2 points
*

No. Tried it like 3-4 times in my life for really f-ed up not booting machines and it never worked for me. Haven’t tried it since the ealy Win10 times, though.

permalink
report
reply
12 points
*

Once. It was a long time ago, and I don’t remember exactly what was wrong, but it did fix it. Since then I’ve run it probably 10 more times and it’s never worked again. Even when the thing that’s wrong is something that it should be able to fix, like I formatted the EFI partition, and it just needs to add its own boot loader again.

permalink
report
reply
4 points

Ha! That’s one of the problems that it has failed to fix for me. I converted several machines from netboot to local boot; the EFI partition was there, but the startup repair couldn’t even handle copying the bootloader files onto it. (Or even diagnose that they were missing.)

permalink
report
parent
reply
5 points

Not for me. I dual booted Fedora and W10 and W10 decided it could no longer boot.

Tried all those powershell commands to fix boot but no bueno. Gave up Windows after.

permalink
report
reply
18 points

the troubleshooter is great! – “problem not found” – it’s exactly the same problem you couldn’t find yesterday, or the day before, or the day before …

(I think I just keep clicking it out of a sense of ritual – it fixed itself once, so I keep doing the same unrelated set of steps in the same order in some forlorn hope of appeasing the Windows daemons)

permalink
report
reply

Asklemmy

!asklemmy@lemmy.ml

Create post

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

Community stats

  • 11K

    Monthly active users

  • 5.7K

    Posts

  • 310K

    Comments