How to ask questions about IT problems

If you ask for help, there might be lots of pieces of information which can help the people who want to help you. You may want to go through the checklist below and see if you can add anything of relevance to reduce the amount of ping-pong between you and a potentially helpful person.

The more information you include, the more likely it is that someone is actually able to help you. Keep in mind that hitting people with a wall of text might also be counter-productive, so maybe put some of the very verbose supporting information on a separate website, e.g. a pastebin.

• Research done to solve the problem
  • URLs of guides used
  • Settings changed
  • Files edited (full path¹)
• Involved software
  • possibly including versions, both on the client and server side for network connections
• Expected behaviour of the software
  • how do you run the software?
    • in case of CLI: what flags/arguments did you use and why?
  • In which way does it work not as expected?
  • How can you reproduce the problem?
  • Are there any error messages? If so, please provide them.
    • what do you think the error messages mean?
    • is there anything you tried to resolve the error message?
  • How did you install the software? [Your Linux distribution's package manager, Flatpak, Windows Store]
• Hardware
  • CPU
    • CPU architecture [x86_64, ARM]
  • GPU
  • Mainboard
  • in case of laptop or OEM PC:
    • exact model number²
    • possibly link to the specifications page or handbook
• Operating system
  • Name and version
    • Windows: run winver
    • macOS: Apple logo at the top left → "about this Mac"
  • Linux:
    • distribution and release (cat /etc/issue and/or cat /etc/lsb-release)
    • Kernel version (uname -rm)

• How To Ask Questions The Smart Way by Eric Steven Raymond
• The Help Vampire: A Spotter’s Guide by Amy Hoy
• What have you tried? (Matt Gemmell, 2008. original article dead)
  • Matt in Hindsight wishes to have never written that article because "[t]he tone is reasonably helpful, but veers periodically towards didacticism and even arrogance". (2015, archived version, Twitter discussion, Stackexchange reply)