• FauxLiving@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    14 hours ago

    Steps to troubleshoot Windows:

    • Reboot, pray
    • Google the error, if any
    • Randomly change registry settings, delete files, install software on the advice of random Internet people/LLMs until the software works or the randomware kicks in.
    • Thank god you’ve never had to touch a Linux terminal, clearly a fate worse than death.
    • Reboot again, just in case
    • ILikeBoobies@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      4 hours ago

      Sfc /scannow

      Dism something

      Are the most common troubleshooting steps and that’s in command prompt

      If that doesn’t work then registry

      If that doesn’t work reinstall the whole OS

      If that doesn’t work just accept that x not working is part of the experience

    • Ferus42@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      13 hours ago

      Looks fairly similar to what you would do on Linux. Change registry to config file (unless you’re using Gnome, then it’s both). You’re right though, on Windows, people don’t usually have paragraph long commands to paste into the terminal to fix some issue. Instead, on Windows you have Microsoft support posts where a “Microsoft Community Support” non-employee pastes non-helpful boilerplate tech support copypasta which are somewhat adjacent to the user’s issue.

      • FauxLiving@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        12 hours ago

        Linux at least gives us useful logging and the software packages have documentation that is accessible without paying for a Microsoft Support contract.

        The Linux community support can actually fix your problems without boilerplate copypasta and doesn’t cost anything but you’ll get the customer service that you pay for.