Record and Share PC Problems with Windows 10 Pro Steps Recorder
Steps Recorder, sometimes called Problems Steps Recorder, is a small utility tucked inside Windows 10 Pro that captures exactly what happens on your screen while you click through a problem. Every mouse click, keystroke, and dialogue box is saved as a screenshot, wrapped together with the text you typed at each moment. The result is a single file you can hand to a tech-savvy friend or attach to a support ticket so they can replay your session without sitting next to you.
This tool is genuinely handy for everyday Windows users dealing with stubborn issues, particularly when words alone struggle to describe what's going wrong. If your printer driver keeps vanishing in Brisbane, your start menu freezes after a Perth heatwave, or your display scaling breaks every time you dock a laptop in Melbourne, the recorder gives you proof that even the most chaotic bug leaves a paper trail.
Starting Steps Recorder from the Start Menu or Run Box
The easiest way to launch the tool is through the search bar on the taskbar. Type Steps Recorder or the older name psr.exe, and Windows will surface the matching desktop app. A small floating panel appears with a single blue Start Record button. Clicking it begins a silent capture of everything visible on your screen, which is reassuring for users who find screen recorders overwhelming.
You can also open it the old-fashioned way through the Win + R Run dialog. Type psr.exe and press Enter, then position the panel wherever it is least likely to cover the area you're testing, such as the bottom corner of a secondary monitor. The command line is helpful because it can be pinned to a script or a shortcut on your desktop, which is useful when you know you'll be triggering the same bug repeatedly during a long debug session.
If neither approach works, the executable lives at C:\Windows\System32\psr.exe. You can browse to it from File Explorer and double-click to run, although the search method is faster and survives feature updates that occasionally shuffle hidden applets out of view. Right-clicking the executable and choosing Run as administrator also helps when group policies are blocking the app from saving output to the Documents folder.
Recording a Session and Adding Live Commentary
Once you press Start Record, Steps Recorder immediately begins taking screenshots after every click. The default capture rate is generous enough to catch menus, dialog boxes, and pop-up errors, but it does not record video. If a problem happens between clicks, such as a window that disappears on its own, you'll need to reproduce the missing step or capture the screen with another tool entirely.
Beneath the main panel sits an Add Comment button. Clicking this pauses the automatic capture and lets you type a short note describing what just happened. From a support perspective in Australia, this is where most of the diagnostic value comes in, because off-screen context such as "the Wi-Fi indicator was off when this happened" or "I had just restarted after the Optus outage" rarely appears in a screenshot. Aim for one or two sentences per comment so the resulting file stays readable.
During recording, you can also highlight a region using the small selection box that appears around your cursor. Anything inside the box gets emphasised in the saved screenshots, drawing the eye of whoever reviews the file later, whether that's a local IT support person in Adelaide or a remote technician from the vendor. A simple arrow drawn around the misbehaving button is often more useful than a paragraph of plain text.
Annotations, Highlights, and Screen Captures That Travel Well
After you press Stop Record, Steps Recorder reviews the captured sequence and prompts you to save it. Before saving, you can drop additional comments onto specific steps, which helps separate cause from coincidence. If a notification slid in from Teams at the exact moment a setting changed, mention it in a comment so the reviewer doesn't chase a red herring.
The output file is an MHTML document, meaning it bundles the screenshots and the comments into a single self-contained file that opens in Edge, Chrome, or any modern browser. This format is convenient because you can email it as an attachment, upload it to a help-desk portal, or paste it into a OneDrive folder you share with a family member in Ballarat who has volunteered to be your unofficial IT person.
You also get a choice of saving as a ZIP archive, which holds the raw screenshots and an XML index separately. The ZIP option matters when you need to edit screenshots or attach them to a forum post on Whirlpool, the long-running Australian tech community where many users trade troubleshooting tips. Be aware that ZIP files can be quite large when captures run long, so a quick email to a friend in Perth may take longer over a regional NBN connection than you expect during peak hours.
What to focus on before each screenshot
A well-prepared capture saves time on both ends. Keep these habits in mind while the recorder is running:
- Close tabs and chat windows that don't relate to the issue, so reviewers aren't distracted by unrelated content.
- Resize windows so the area you care about sits clearly in view, especially when working on a high-DPI laptop screen.
- Reproduce the problem at a steady pace, pausing briefly if the recorder seems to skip frames.
- Crop or annotate around hidden cursors using the built-in highlight tool so mouse positions stay visible in the saved file.
These small adjustments often turn a baffling file into an obvious diagnosis within minutes, especially on the first try.
Sharing Recordings Safely Under Australian Privacy Conditions
Anything visible on your screen during a capture ends up in the recording, including account names, email subject lines, and browser tabs you forgot were open. Before sharing a Steps Recorder file, scrub it for personal details. The Edit Comment feature in the Review screen lets you delete individual steps entirely, which is faster than re-recording the whole issue from scratch.
For Australian users dealing with service providers, the Privacy Act 1988 applies whenever a recording contains identifiable information about another person. If your issue involves a workplace account, a customer portal, or a screenshot that shows a colleague's name, you may need to mask those elements before sending the file to anyone outside your organisation. Even family-friendly recordings can reveal a bit more than you'd like, such as the name of your Wi-Fi network or the model of your router, which is information some people prefer to keep private.
If you're sending the file to an official Microsoft support channel, review the company's current data handling policy first. Recent guidance has pointed users to a media creation tool page that walks through reinstalling Windows cleanly when recordings alone can't pinpoint the cause, which pairs well with the snapshot you already have.
Common Steps Recorder Errors and How to Fix Them
Some users find that pressing Start Record produces no file at all, while others see the panel close the moment they switch applications. These quirks usually trace back to a small number of causes, and most have a workaround that takes less time than retyping the original problem description. Run a quick check on the installed Windows version too, because Steps Recorder on older 1909 builds behaves differently than the same tool on a fully patched 22H2 installation that has been kept up to date through Windows Update.
Quick fixes for a stubborn Steps Recorder session
- Capture stops the moment you lock the workstation: enable background services through the Services panel, or sign in with a different account that has fewer group policy restrictions.
- Saved file will not open in your default browser: rename the .mht extension to .html, then reload, or drag the file into an incognito window to bypass cached settings.
- Steps Recorder is not listed in search: open Turn Windows features on or off from the Control Panel and ensure the Problem Recording and remote scripting entries remain enabled, then reboot.
- Output is enormous even for a short session: shorten the recording window, switch off full-screen apps that redraw constantly, and prefer ZIP output when archiving captures.
A related annoyance is when the panel itself refuses to respond because another app is stealing focus. Closing Slack, Teams, or Outlook before recording tends to help, because each of these tools aggressively redraws the screen and can slow the recorder to a crawl on older hardware. If the panel is still misbehaving, try right-clicking the Steps Recorder entry in Task Manager and choosing End task, then relaunch it from the Run dialog with administrative privileges to refresh its permissions.
When Steps Recorder Isn't Enough and What to Try Next
Steps Recorder captures clicks and keystrokes, but it cannot reproduce video, sound, or gestures on a touchscreen. If your issue involves a frozen animation, an audio dropout during a Teams call, or a stylus scribble that won't save in OneNote, you'll need a fuller recording tool. The Xbox Game Bar built into Windows 10 Pro handles short video captures, while OBS Studio remains the free option most Australian creators and forum helpers trust for longer clips that need cleaner framing.
For performance issues that Steps Recorder can't capture, such as CPU spikes or memory leaks, the Reliability Monitor in the same Control Panel neighbourhood is a worthwhile companion. It tracks crashes and warnings over time, giving you a longer view of a flaky problem than any single recording can. Pairing the recorder with Reliability Monitor creates a more complete picture, particularly when the bug only appears once a week, which is common with thermal throttling during long Australian summer afternoons when a notebook sits on a warm desk.
If a deep reinstall ends up being the recommended fix, whether from a vendor or a forum helper, having a clean ISO on hand avoids a long wait on a slow connection in regional towns. The same media creation walkthrough that supports Step Recorder troubleshooting also covers burning the ISO to a USB drive, and it pairs well with the recordings you've already gathered so you know exactly what changed between the broken and the working install.
Open Steps Recorder on your own PC, reproduce the next annoying bug you spot, and attach the saved file to whichever support channel you're using along with a short sentence or two of context. Describe what you expected to happen, what actually happened, and any timing clues such as "this only fails after the laptop wakes from sleep", then send the bundle to your helper and let the screenshots do the talking.