Getting Support for Windows Instances

This guide covers some common issues with Windows instances on Google Compute Engine, and shows you how to get support.

If you have paid support with Google Cloud Platform, file a report through one of the support channels. If you do not have paid support, you can:

Known issues

The following are known issues with Windows images:

  • Although Windows instances can use the NVMe interface with local SSD, support for NVMe on Windows is in Beta and we do not guarantee the same performance as Linux instances.
  • On Windows 2008 R2, installing Python 2.7.9 or newer requires Visual C++. Python 2.7.8 avoids this dependency but we recommend installing the latest version.
  • Compute Engine does not yet support IPv6. Even if you enable IPv6 by selecting the option in a Windows instance, the setting is ignored.
  • Once a new instance is created, you cannot connect to it instantly. All new Windows instances use the System Preparation (sysprep) tool to set up your instance, which can take 5-10 mins to complete.
  • Windows Server images cannot activate without a network connection to, and stop functioning if they do not initially authenticate within 30 days. Software activated by the KMS must reactivate every 180 days, but the KMS attempts to reactivate every 7 days. Create an external IP for your Windows instances so they can authenticate periodically.
  • Kernel software accessing non-emulated Model Specific Registers will generate General Protection Faults, which can cause a system crash depending on the guest operating system.
Was this page helpful? Let us know how we did:

Send feedback about...

Compute Engine Documentation