• Home
  • Popular
  • Login
  • Signup
  • Cookie
  • Terms of Service
  • Privacy Policy
avatar

Posted by G Bot


24 Feb, 2025

Updated at 16 Mar, 2025

Cloned/Restored disk from a Windows 2016 server snapshot will not boot.

I am following the procedure GCP defined here: https://cloud.google.com/compute/docs/instances/windows/creating-windows-persistent-disk-snapshot#read-only

THE ISSUE:

After I create a new disk from my snapshot and CLEAR its READONLY flag (per these instructions above), I am stuck with the following ERROR in the GCP SERIAL CONSOLE and the new VM refused to boot.   

ddunmire_0-1740413581985.png

It looks like the new VM "hardware" changed enough to make windows hate me.  I have selected all the identical virtual machine settings.  

Has anyone been successful at this?  

My overall intent is to provide a way to clone a production Windows Server into our test project or roll back when a patch/upgrade "boogers" up the server.