Capturing VM screenshots Stay organized with collections Save and categorize content based on your preferences.

This page describes how to capture a screenshot from a virtual machine (VM) instance by using the VM screenshot tool.

Capturing a screenshot from a VM can help you troubleshoot a VM that is not otherwise accessible. For example, a VM might not be accessible if it is booting or has a disk image that is corrupted.

Windows-based operating systems

VM screenshots can help to troubleshoot failed RDP connections to Windows VMs, by identifying if the instance has started successfully. For information about troubleshooting RDP connections, see Troubleshooting RDP.

Privacy considerations with remote desktop clients

The VM screenshot tool uses the display adapter of the VM to capture a screenshot of the local console session through a remote desktop client. Capturing a screenshot through the local console session might capture sensitive information from the user's desktop or browser.

If you are concerned about exposing sensitive information as part of a screenshot, configure your respective remote desktop client in the following way so that it does not use the local console session:

• Chrome Remote Desktop: If you are using Chrome Remote Desktop, be sure to enable Curtain mode so that it does not connect to the local console session.

• Microsoft RDP: RDP clients connect by using Windows Remote Desktop Services (RDS). Windows RDS lets RDP clients choose whether to start a new console session or connect to the existing one, and because of this, there might be privacy implications. For information about customizing RDS so that it does not connect to the local console session, see Supported Remote Desktop RDP file settings.

Before sharing screenshots with Google Support, make sure to review them for sensitive information.

Before you begin

• Enable virtual displays on your VM.
• If you haven't already, set up 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:

  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

  1. Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:

     gcloud init

     If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

     Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
  2. Set a default region and zone.

  REST

  To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.

  Install the Google Cloud CLI.

  If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

  For more information, see Authenticate for using REST in the Google Cloud authentication documentation.

Limitations

• The instance must be in the RUNNING life cycle state.

• The maximum rate for capturing screenshots is 20 per second, which is the API rate limit.

• You can't initiate a screenshot while one is in progress.

• You can capture one screenshot at a time.

Capturing a screenshot from a VM

Use the following procedures to capture a screenshot from a VM.

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.instances.getScreenshot

gcloud compute instances get-screenshot VM_NAME \
  --destination=JPEG_FILENAME \
  --zone=ZONE

GET https://compute.googleapis.com/compute/v1/projects/PROJECT/zo
nes/ZONE/instances/VM_NAME/screenshot

Example VM screenshots

The Compute Engine UEFI loading the boot manager

The following screenshot shows a Windows Server VM that is unavailable while the boot manager is loading:

[The UEFI loading the boot manager]

[uefi.png]

Windows Server 2016 Datacenter performing updates

The following screenshot shows a Windows Server 2016 VM that is unavailable while completing updates:

[Windows Server 2016 Datacenter performing updates.]

[updating.png]

Windows Server 2016 loading system services

The following screenshot shows a Windows Server 2016 VM that is unavailable while loading system services:

[Windows Server 2016 loading system services.]

[services.png]

Login screen for Windows Server 2016 Datacenter

The following screenshot shows a Windows Server 2016 VM that has completed startup and is ready to login:

[Login screen for Windows Server 2016 Datacenter.]

[login.png]

Sysprep process of Windows Server 2019 Core

The following screenshot shows the sysprep process of a Windows Server 2019 Core VM instance:

[Sysprep process for Windows Server 2019 Core.]

[windows-ss-1.png]

Blue screen error from Windows Server 2016 Datacenter

The following screenshot shows a blue screen error from a Windows Server 2016 Datacenter VM instance:

[Blue screen from Windows Server 2016 Datacenter.]

[bsod.png]

What's next

• Learn how to collect diagnostic information from a VM.

• Learn how to troubleshoot Windows instances.