Write a support report someone can reproduce

A support report is most useful when another person can repeat the problem. A screenshot supports the report, but it does not replace the steps that lead to the issue.

Describe one observable problem

State the task, the expected result and what happened instead. Include the application version and operating system when they are relevant. Avoid combining several unrelated issues into one report; each may have a different cause and resolution.

Collect useful evidence

1. Write the shortest sequence of steps that still reproduces the problem.
2. Capture the relevant window and enough context to identify it.
3. Annotate the exact control or error message.
4. Remove private information and check the saved attachment.

If the problem involves timing or motion, a short screen recording may explain it better than a static image. Keep the recording focused on the reproducing steps.

Verify the report before sending

Read the steps as if you had never seen the application. Check that filenames, settings and necessary inputs are described. Attach the actual error text when possible so it can be searched. A concise report with a clear reproduction is easier to act on than a large collection of screenshots with no explanation.

Official reference

Read the official documentation for current controls, system requirements and release-specific details. Find the publisher’s download link in our Sharex listing.