Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Linux
Windows
En esta página, se describe cómo realizar una captura de pantalla desde una instancia de máquina virtual (VM) mediante la herramienta de captura de pantalla de VM.
Realizar una captura de pantalla de una VM puede ayudarte a solucionar problemas en una VM a la que no se pueda acceder de otra manera. Por ejemplo, es posible que no se pueda acceder a una VM si se está iniciando ni si hay una imagen de disco dañada.
Sistemas operativos basados en Windows
Las capturas de pantalla de VM pueden ayudar a solucionar problemas con las conexiones de RDP que no se realizaron a las VM de Windows, ya que identifican si la instancia se inició de manera correcta. Para obtener información sobre la solución de problemas de las conexiones de RDP, consulta Soluciona problemas de RDP.
Consideraciones de privacidad con clientes de escritorio remoto
La herramienta de captura de pantalla de VM usa el adaptador de pantalla de la VM para realizar una captura de pantalla de la sesión de la consola local a través de un cliente de escritorio remoto.
Realizar una captura de pantalla a través de la sesión de la consola local puede capturar información sensible desde el navegador o el escritorio del usuario.
Si te preocupa exponer información sensible como parte de una captura de pantalla, configura el cliente de escritorio remoto correspondiente de la siguiente manera para que no use la sesión de la consola local:
Microsoft RDP: los clientes de RDP se conectan mediante los Servicios de Escritorio remoto (RDS) de Windows. RDS de Windows permite que los clientes de RDP elijan si desean iniciar una sesión nueva en la consola o conectarse a la existente. Como consecuencia, es posible que existan implicaciones de privacidad. Para obtener información sobre cómo personalizar RDS a fin de que no se conecte a la sesión de la consola local, consulta Configuración admitida del archivo RDP de Escritorio remoto.
Antes de compartir capturas de pantalla con la Atención al cliente de Google, asegúrate de revisarlas para detectar información sensible.
Si aún no lo hiciste, configura la autenticación.
La autenticación verifica tu identidad para acceder a los Google Cloud servicios y las APIs. Para ejecutar código o muestras desde un entorno de desarrollo local, puedes autenticarte en Compute Engine seleccionando una de las siguientes opciones:
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and
APIs, you don't need to set up authentication.
gcloud
Instala Google Cloud CLI.
Después de la instalación,
inicializa Google Cloud CLI ejecutando el siguiente comando:
En la página Instancias de VM, haz clic en el nombre de la instancia de VM en la que deseas realizar una captura de pantalla.
En la página Detalles de instancia de VM, haz clic en la pestaña Captura de pantalla.
Haz clic en Actualizar para generar una captura de pantalla desde la VM. Si no habilitaste una pantalla virtual, la consola deGoogle Cloud no muestra una captura de pantalla.
VM_NAME: El nombre de la VM desde la que se realiza una captura de pantalla
JPEG_FILENAME: El nombre de archivo opcional del archivo jpeg para el resultado de la captura de pantalla. Si no especificas un nombre de archivo, los datos jpeg sin procesar se envían a la salida estándar (stdout)
ZONE: la zona de la VM desde la que se realiza una captura de pantalla
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis page provides instructions on how to use the VM screenshot tool to capture screenshots from virtual machine (VM) instances, which can be helpful for troubleshooting inaccessible VMs or failed RDP connections.\u003c/p\u003e\n"],["\u003cp\u003eThe VM screenshot tool captures the local console session through a remote desktop client, potentially exposing sensitive information, so users should configure their remote desktop client (like Chrome Remote Desktop or Microsoft RDP) to avoid using the local console session.\u003c/p\u003e\n"],["\u003cp\u003eTo take a screenshot, the VM must be in the \u003ccode\u003eRUNNING\u003c/code\u003e state, the maximum capture rate is 20 screenshots per second, and only one screenshot can be captured at a time, with the process requiring specific permissions.\u003c/p\u003e\n"],["\u003cp\u003eUsers can capture a screenshot through the Google Cloud console, using the \u003ccode\u003egcloud compute instances get-screenshot\u003c/code\u003e command, or by making a \u003ccode\u003einstances.getScreenshot\u003c/code\u003e request through the Compute Engine API.\u003c/p\u003e\n"],["\u003cp\u003eBefore sharing screenshots, users are encouraged to check them for sensitive data, and are also provided with links to more information regarding diagnostics and troubleshooting.\u003c/p\u003e\n"]]],[],null,["# Capturing VM screenshots\n\nLinux Windows\n\n*** ** * ** ***\n\nThis page describes how to capture a screenshot from a virtual machine (VM)\ninstance by using the VM screenshot tool.\n\nCapturing a screenshot from a VM can help you troubleshoot a VM that is not\notherwise accessible. For example, a VM might not be accessible if it is booting\nor has a disk image that is corrupted.\n\nWindows-based operating systems\n-------------------------------\n\nVM screenshots can help to troubleshoot failed RDP connections to Windows VMs,\nby identifying if the instance has started successfully. For information about\ntroubleshooting RDP connections, see [Troubleshooting\nRDP](/compute/docs/troubleshooting/troubleshooting-rdp#vm-screenshot).\n\nPrivacy considerations with remote desktop clients\n--------------------------------------------------\n\nThe VM screenshot tool uses the display adapter of the VM to capture a\nscreenshot of the local console session through a remote desktop client.\nCapturing a screenshot through the local console session might capture sensitive\ninformation from the user's desktop or browser.\n\nIf you are concerned about exposing sensitive information as part of a\nscreenshot, configure your respective remote desktop client in the following way\nso that it does not use the local console session:\n\n- [Chrome Remote Desktop](https://remotedesktop.google.com/): If you are using\n Chrome Remote Desktop, be sure to enable [Curtain\n mode](https://support.google.com/chrome/a/answer/2799701) so that it does\n not connect to the local console session.\n\n- [Microsoft RDP](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients):\n RDP clients connect by using [Windows Remote Desktop Services\n (RDS)](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/welcome-to-rds). Windows RDS lets RDP clients choose whether to start a new\n console session or connect to the existing one, and because of this, there might\n be privacy implications. For information about customizing RDS so that it does\n not connect to the local console session, see [Supported Remote Desktop RDP file\n settings](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/rdp-files).\n\nBefore sharing screenshots with [Google\nSupport](https://cloud.google.com/support-hub), make sure to review them for\nsensitive information.\n\nBefore you begin\n----------------\n\n- [Enable virtual displays on your VM](/compute/docs/instances/enable-instance-virtual-display).\n- If you haven't already, set up [authentication](/compute/docs/authentication). Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:\n\n Select the tab for how you plan to use the samples on this page: \n\n ### Console\n\n\n When you use the Google Cloud console to access Google Cloud services and\n APIs, you don't need to set up authentication.\n\n ### gcloud\n\n 1.\n [Install](/sdk/docs/install) the Google Cloud CLI.\n\n After installation,\n [initialize](/sdk/docs/initializing) the Google Cloud CLI by running the following command:\n\n ```bash\n gcloud init\n ```\n\n\n If you're using an external identity provider (IdP), you must first\n [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n | **Note:** If you installed the gcloud CLI previously, make sure you have the latest version by running `gcloud components update`.\n 2. [Set a default region and zone](/compute/docs/gcloud-compute#set_default_zone_and_region_in_your_local_client).\n\n ### REST\n\n\n To use the REST API samples on this page in a local development environment, you use the\n credentials you provide to the gcloud CLI.\n 1. [Install](/sdk/docs/install) the Google Cloud CLI. After installation, [initialize](/sdk/docs/initializing) the Google Cloud CLI by running the following command: \n\n ```bash\n gcloud init\n ```\n 2. If you're using an external identity provider (IdP), you must first [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n\n\n For more information, see\n [Authenticate for using REST](/docs/authentication/rest)\n in the Google Cloud authentication documentation.\n\nLimitations\n-----------\n\n- The instance must be in the `RUNNING` [life cycle\n state](/compute/docs/instances/instance-life-cycle).\n\n- The maximum rate for capturing screenshots is 20 per second, which is the [API\n rate limit](/compute/docs/api-rate-limits).\n\n- You can't initiate a screenshot while one is in progress.\n\n- You can capture one screenshot at a time.\n\nCapturing a screenshot from a VM\n--------------------------------\n\nUse the following procedures to capture a screenshot from a VM.\n\n#### Permissions required for this task\n\nTo perform this task, you must have the following\n[permissions](/iam/docs/overview#permissions):\n\n\n- `compute.instances.getScreenshot` \n\n### Console\n\n1. In the Google Cloud console, go to the **VM instances** page.\n\n [Go to VM instances](https://console.cloud.google.com/compute/instances)\n2. From the **VM instances** page, click the name of the VM instance to\n capture a screenshot from.\n\n3. On the **VM instance details** page, click the **Screenshot** tab.\n\n4. Click **Refresh** to generate a screenshot from the VM. If you have not\n [enabled a virtual\n display](/compute/docs/instances/enable-instance-virtual-display), the\n Google Cloud console does not show a screenshot.\n\n### gcloud\n\nCapture a screenshot from a VM by using the [`gcloud compute\ninstances get-screenshot` command](/sdk/gcloud/reference/compute/instances): \n\n```\ngcloud compute instances get-screenshot VM_NAME \\\n --destination=JPEG_FILENAME \\\n --zone=ZONE\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e: name of the VM to capture a screenshot\n from.\n\n- \u003cvar translate=\"no\"\u003eJPEG_FILENAME\u003c/var\u003e: optional filename of the jpeg for\n the screenshot output. If you do not specify a filename, the raw jpeg data\n is sent to standard output (stdout).\n\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: zone of the VM to capture a screenshot from.\n\n### REST\n\nWith the Compute Engine API, capture a screenshot from a VM by using the\n[`instances.getScreenshot`\nrequest](/compute/docs/reference/rest/v1/instances/getScreenshot): \n\n```\nGET https://compute.googleapis.com/compute/v1/projects/PROJECT/zo\nnes/ZONE/instances/VM_NAME/screenshot\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e: ID of the project containing the VM to\n capture a screenshot from.\n\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: zone containing the project.\n\n- \u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e: name of the VM to capture a screenshot\n from.\n\nExample VM screenshots\n----------------------\n\n### The Compute Engine UEFI loading the boot manager\n\nThe following screenshot shows a [Windows\nServer](/compute/docs/images/os-details#windows_server) VM that is unavailable\nwhile the boot manager is loading:\n\n### Windows Server 2016 Datacenter performing updates\n\nThe following screenshot shows a [Windows Server\n2016](/compute/docs/images/os-details#windows_server) VM that is unavailable\nwhile completing updates:\n\n### Windows Server 2016 loading system services\n\nThe following screenshot shows a [Windows Server\n2016](/compute/docs/images/os-details#windows_server) VM that is unavailable\nwhile loading system services:\n\n### Login screen for Windows Server 2016 Datacenter\n\nThe following screenshot shows a [Windows Server\n2016](/compute/docs/images/os-details#windows_server) VM that has completed\nstartup and is ready to login:\n\n### Sysprep process of Windows Server 2019 Core\n\nThe following screenshot shows the [sysprep\nprocess](/compute/docs/instances/windows/creating-windows-os-image#create_server_image)\nof a [Windows Server 2019\nCore](/compute/docs/images/os-details#windows_server) VM instance:\n\n### Blue screen error from Windows Server 2016 Datacenter\n\nThe following screenshot shows a blue screen error from a [Windows Server\n2016 Datacenter](/compute/docs/images) VM instance:\n\nWhat's next\n-----------\n\n- Learn how to [collect diagnostic information from a\n VM](/compute/docs/instances/collecting-diagnostic-information).\n\n- Learn how to [troubleshoot Windows\n instances](/compute/docs/troubleshooting/troubleshooting-windows)."]]