> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/general-virtual-machine-management/encrypt-decrypt-a-virtual-machine.md).

# Encrypt/Decrypt a Virtual Machine

{% hint style="info" %}
**Note**: These commands are not supported for macOS virtual machines.
{% endhint %}

**prlctl encrypt** <*vm\_id* | *vm\_name*> \[**--dry-run**]

Encrypts the specified virtual machine. You can use the the **--dry-run** option to check preconditions for successful encryption. The **encrypt** command will encrypt the specified virtual machine and all its data. A user will be prompted to enter an encryption password after the command is executed. The password will be required to decrypt the virtual machine later. The encryption password can be modified for an encrypted virtual machine using the **change-passwd** command (see below).

**prlctl decrypt** <*vm\_id* | *vm\_name*> \[**--dry-run**]

Decrypts the specified encrypted virtual machine. You can use the **--dry-run** option to check preconditions for successful decryption. The **decrypt** command will decrypt the specified virtual machine. A user will have to enter a password that was specified when the virtual machine was encrypted.

**prlctl change-passwd** <*vm\_id* | *vm\_name*>

Changes the encryption password for the specified virtual machine. A user will be asked to enter the current and the new password.


---

# 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.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/general-virtual-machine-management/encrypt-decrypt-a-virtual-machine.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.