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.

  • gregorum@lemm.ee
    link
    fedilink
    English
    arrow-up
    40
    ·
    edit-2
    8 months ago

    Yeah, on Win98 (or maybe Win2k), it would always find this obscure sound card driver for this crappy sound card in this Packard Bell I had. Amazing.

    But not once ever for any other issue before or since.

  • kuneho@lemmy.world
    link
    fedilink
    arrow-up
    30
    ·
    8 months ago

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

  • nocturne213@lemm.ee
    link
    fedilink
    arrow-up
    24
    ·
    8 months ago

    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.

  • andrewta@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    edit-2
    8 months ago

    Never. I’ve been using since Windows 3.11

    Windows 95

    Windows 98

    Windows xp

    Vista

    Windows 8

    Windows 10

    Not once has it solved a problem

      • andrewta@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        8 months ago

        No. That was meant as a statement of I’ve been using windows for that long and since the beginning of Windows (and when ever they introduced the trouble shooter) it’s never worked

    • Honytawk@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      8 months ago

      Then use it more, because it does work.

      ~Sinisterly, someone who has been using Windows as long as you but also has used Windows ME, Windows 2000, Windows 7 and Windows 11.

      • andrewta@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        ? Use it more because it “works” even though it’s never worked for me.

        That’s your logic?

        So you are saying the system uses a powerful AI that learns and adapts? That way over time it will start fixing the issues?

        Look at the other comments to see how many people have had no luck with the system. Maybe it works for you but in general it fails.

  • Paranomaly@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    11
    ·
    8 months ago

    No, however I think there might be a bit of a trap here that skews perception for some. Namely, that the automatic tools are intended to fix problems simple enough that more technical minded people would attempt the solutions it uses themselves before resorting to a troubleshooter.

  • hperrin@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    8 months ago

    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.

    • SwingingTheLamp@midwest.socialOP
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      8 months ago

      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.)

  • averyminya@beehaw.org
    link
    fedilink
    arrow-up
    9
    ·
    8 months ago

    Troubleshooter maybe once, but otherwise no.

    Startup repair yes though, after doing the right set of SFC scan and updating Windows cache whatever thing

  • cerement@slrpnk.net
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    8 months ago

    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)

  • lud@lemm.ee
    link
    fedilink
    arrow-up
    9
    ·
    8 months ago

    The network troubleshooter often works alright. Just never run it if you have setup a bunch of virtual switches in hyper V or something, because it will delete them or otherwise fuck them up and it’s pretty annoying to restore (you have to remove them via device Manager and stuff)

  • Saigonauticon@voltage.vn
    link
    fedilink
    English
    arrow-up
    9
    ·
    8 months ago

    Yes – frequently, but this is a bad thing.

    The issue was that their automatic updater makes my computer unable to boot, due to some compatibility problem with an update. Which it keeps trying to apply. Then every time it fails, startup repair or some troubleshooter rolls back the update and it works again for a while.

    Since I cannot turn off updates, it’s stuck in this loop forever. However, I can turn off my computer via the power button (sending shutdown signal, not hard power off), and this avoids applying the update most of the time.

    This is an older computer that is only used for games, and a slicer for my 3D printer. I’ve decided to leave it in this state – at this point it’s more a piece of performance art than a reliable computer. I moved my business and my clients away from MS a few years back.

    This cost me a lot of easy money though – there’s no maintenance work for me to do and I’ve had to move on to more productive things.

      • Saigonauticon@voltage.vn
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 months ago

        Haven’t found an option that does this with any degree of permanence. Always re-enables updates after a short time without prompting. Then reminds me every 3 days to set up a MS account.

        Not very concerned – it’s not worth my time to fix. I don’t have free time.

      • Omega_Jimes@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        This guy thinks you can do what you want with Windows.

        Disabling updates is such a ridiculous thing because sometimes it works, and sometimes Windows just ignores you.

        I’ve literally had two exact model laptops running as local render servers, fully updated, then disabled updates/reboots on both, around a month later one updated and rebooted dumping my workload and corrupting my database. Disabling anything on Windows doesn’t always work, it does what it wants.

  • EuroNutellaMan@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    8 months ago

    Well, it helped me boot into USB drives so I can remove windows and swap it with Linux on some annoying computers that would boot windows very fast…

  • Jtee@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 months ago

    Yes, and I’ve also had success using tools like SFC and DISM to repair Windows.

        • WhatTrees@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          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.

          • elvith@feddit.de
            link
            fedilink
            arrow-up
            1
            ·
            8 months ago

            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.

            • d3Xt3r@lemmy.nz
              link
              fedilink
              arrow-up
              2
              ·
              8 months 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.

  • JoshCodes@programming.dev
    link
    fedilink
    arrow-up
    7
    ·
    8 months ago

    The Windows network troubleshooter is black magic from the depths of hell itself and is very opinionated and selective in choosing which issues to fix and whether you’ll need to bargain your soul to recieve said fix. I have red hair and find it doesn’t bother bartering with me, but your mileage may vary.