> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/reference/step-definitions/restore-user-state-with-usmt.md).

# Restore user state with USMT

{% hint style="info" %}
Applies to: DeployR 1.4 and later.
{% endhint %}

The **Restore user state with USMT** step uses the User State Migration Tool (USMT) `LoadState` command to restore the user state captured by the [Capture user state with USMT](/deployr/reference/step-definitions/capture-user-state-with-usmt.md) step. It reads the hardlink state store at `C:\_2P\StateCapture`, then deletes the store.

This step has no options. Run it in the full OS of the newly installed operating system, after the **Configure operating system** step.

### Details

* If there is no state store at `C:\_2P\StateCapture`, the step fails.
* The USMT files come from the built-in **DeployR USMT files for x64** or **DeployR USMT files for arm64** content item, depending on the device architecture.
* `LoadState` runs with the same `MigDocs.xml` and `MigApp.xml` rules used for the capture, with `/hardlink /nocompress /lac /c`. The `/lac` switch creates local accounts that were captured but do not exist yet on the new OS. They are created disabled.
* After the restore, the state store is removed with `usmtutils.exe /rd`, because a hardlink store cannot reliably be deleted any other way.
* Logs are written to `C:\_2P\logs\LoadState.log` and `C:\_2P\logs\LoadStateProgress.log`.
* Exit code 3 (success with non-fatal errors) is treated as success. Any other non-zero exit code fails the step.

For domain-joined devices, join the new OS to the domain before this step so that domain user profiles are restored for the right accounts.


---

# 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://documentation.2pintsoftware.com/deployr/reference/step-definitions/restore-user-state-with-usmt.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.