> For the complete documentation index, see [llms.txt](https://docs.themspkb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themspkb.com/resources/technical-resources/msp-toolkit/screen-capture/problem-screen-recorder.md).

# PSR

Problem Screen Recorder. Is a handy screen grabber and set by step documentation tool. It is built directly into Windows 7+

## To record and save steps on your computer

* To open Steps Recorder, select the **Start** button, and then select **Windows Accessories** > **Steps Recorder** (in Windows 10), or **Accessories** > **Problem Steps Recorder** (in Windows 7 or Windows 8.1)
* Select **Start Record**
* Go through the steps to reproduce or solve the problem. You can pause and resume the recording at any time.
* As you record, select **Add Comment**, use your mouse to select the part of the screen that you want to comment on, type your comment, and then select **OK**
* When you’re done, select **Stop Record**
* Review the record of the steps you followed to make sure it shows what you want it to show. Select **Save**, name the .zip file, choose where to save it, and then select **Save**. Now you can attach and send this .zip file to the person helping you troubleshoot the problem on your PC. It can be viewed in any web browser.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.themspkb.com/resources/technical-resources/msp-toolkit/screen-capture/problem-screen-recorder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.