> 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/pdfm-ug/v20-es-es/guia-del-usuario-de-parallels-desktop-para-mac-20/uso-de-windows-en-su-mac/proteccion-de-sus-datos/aislar-windows-de-mac.md).

# Aislar Windows de Mac

Puede aislar Windows de macOS para que así ya no compartan carpetas, perfiles y aplicaciones y para que los dispositivos externos que conecte ya no sean accesibles automáticamente por parte de Windows. Asimismo, Windows y Mac dejarán de sincronizar el contenido del volumen y tampoco podrá copiar o mover objetos entre Windows y macOS. Aislar Windows de macOS puede proporcionar un nivel más elevado de seguridad, ya que no se permite que elementos confidenciales de un SO estén en contacto con el otro.

Para aislar Windows de macOS

1. Realice una de las siguientes acciones:
   * Haga clic en el icono de Parallels Desktop en la barra de menús y seleccione **Configurar**.
   * Si en la parte superior de la pantalla puede ver la barra de menús de Parallels Desktop, seleccione **Acciones** > **Configurar**.
2. Haga clic en **Seguridad**.
3. Seleccione **Aislar Windows de Mac**.


---

# 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 dynamically 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/pdfm-ug/v20-es-es/guia-del-usuario-de-parallels-desktop-para-mac-20/uso-de-windows-en-su-mac/proteccion-de-sus-datos/aislar-windows-de-mac.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 `build a script that syncs our docs to a CMS` 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.