> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/ioexception-the-process-cannot-access-the-file.md).

# IOException - the process cannot access the file

Fix the IOException process cannot access the file error on RDP recordings by adding a date or time variable to the recording file name.

```
IOException - The process cannot access the file 'C:\Users*User*\AppData\Local\Temp\RDM\record.mp4' because it is being used by another process.
```

### Solution

This error can be avoided by adding a variable to the name of your recording. That way, Remote Desktop Manager will not have issues trying to overwrite an already existing recording. In general, we recommend using variables such as `$DATE_TEXT$` or `$TIME_TEXT$` to identify recording.

For example, if you changed your path to:

*`C:\Users*User\AppData\Local\Temp\RDM\record-$DATE_TEXT$-$TIME-TEXT$.mp4`*

The name of your recording would look something like `record-2202020-100257.mp4`. This will ensure that each recording has a unique name.


---

# 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.devolutions.net/rdm/knowledge-base/troubleshooting-articles/ioexception-the-process-cannot-access-the-file.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.