Windows Apps & tools

Record steps with Problem Steps Recorder

Document a bug reproducibly for IT or forums without third-party tools.

8 min read Beginner Updated 9 Jun 2026

Step-by-step guide

Work through each section in order. Stop when your issue is resolved — you do not need every step for every situation.

What you will achieve

Capture a step-by-step record of a bug or UI problem using Problem Steps Recorder (PSR) — screenshots, clicks, and optional comments saved as an MHTML report you can attach to support tickets or forum posts.

1) Launch Problem Steps Recorder

  1. Press Win + R, type psr.exe, press Enter.
  2. Or search Start for Steps Recorder (Windows 11 name) or Problem Steps Recorder (Windows 10).
  3. The small PSR toolbar appears — drag it so it does not cover the area you will record.

2) Configure before recording

  1. Click the arrow beside HelpSettings.
  2. Set Number of recent screen captures to store — default 25 is usually enough.
  3. Enable Enable screen capture unless privacy policy forbids screenshots.
  4. Optionally set an output location; otherwise PSR prompts on save.

3) Record the problem

  1. Click Start Record.
  2. Reproduce the issue exactly — each click and keystroke is logged with a screenshot.
  3. Click Add Comment at critical steps to annotate what you expected versus what happened.
  4. Click Stop Record when finished.

4) Save and share the report

  1. Choose a save location and filename — PSR creates a ZIP containing an .mht MHTML file.
  2. Extract the ZIP and open the MHTML file in Edge or Internet Explorer — it shows numbered steps with thumbnails.
  3. Attach the ZIP to your ticket; redact sensitive data before sending — PSR captures everything visible on screen including emails and account names.

5) Limitations and alternatives

PSR does not record video, full-screen DirectX games, or elevated (Admin) windows from non-elevated sessions reliably. For video capture use Xbox Game Bar (Win + G). Pair PSR with Event Viewer logs for crashes — our Event Viewer guide covers exporting error details PSR cannot see.

6) Strip sensitive data before sharing

Open the MHTML report and verify no passwords, account numbers, or personal email content appear in screenshots. Crop or redo the recording if needed. Rename the ZIP with the ticket number and date — support teams reject unnamed Problem_Steps archives daily.

Related guides

psr screenshots troubleshooting