> 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/definicion-del-modo-en-que-windows-interactua-con-macos/configuracion-de-windows-para-que-ocupe-toda-la-pantalla.md).
# Configuración de Windows para que ocupe toda la pantalla
Puede configurar Windows para que ocupe toda su pantalla, para así tener la misma experiencia que si trabajara en un PC Windows. En modo de pantalla completa, se ocultará macOS y todos los controles de Parallels Desktop.
Para pasar al modo de Pantalla Completa:
* Estando en modo Coherence, haga clic en el icono de Parallels Desktop presente en la barra de menús y seleccione **Ver** > **Salir de Coherence**. Haga clic en el menú **Ver** y seleccione **Pasar a pantalla completa**.
* Desde el modo Ventana, seleccione **Ver** > **Pasar a pantalla completa** o haga clic en el icono Pantalla completa (verde) en la esquina superior izquierda de la ventana de la máquina virtual.
Para salir del modo de pantalla completa, realice una de las siguientes acciones:
* Presione Comando-Control-F.
* Mueva el puntero a la parte superior de la pantalla hasta que aparezca la barra de menús de macOS y haga clic en **Ver** > **Salir de pantalla completa**. Si está utilizando el modo de pantalla completa optimizado para juegos, pulse Control-Opción (Alt) para mostrar la barra de menús 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 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/definicion-del-modo-en-que-windows-interactua-con-macos/configuracion-de-windows-para-que-ocupe-toda-la-pantalla.md?ask=&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.
