Hyper-V Manager / Windows 10

Hyper-V Manager: failed to change state. The operation failed with error code ‘32788’

Ulv Bjørnsson5 Comments

Now you are likely here, because you are currently getting this error message: 32788.

2017-05-04_13-29-13.png

Most likely you’ve recently played around with your “Network Adapters”

2017-05-04_13-23-02.png

or you’ve been in the “Virtual Switch Manager” and perhaps deleted a “Virtual Switch.”

So to resolve it, quick and easy. You can do the following:

Navigate to the affected Virtual Machine in your Hyper-V Manager:

mmc_2017-05-04_13-30-32.png

 

Now if you look at the “Network Adapter” you can see it says “Configuration Error”

2017-05-04_13-32-06.png

This means that there has been a change to your “Network Adapter/Adapter Settings” or a change to your “Virtual Switch Manager”.

So all the way to the right in the “Actions”-panel in your Hyper-V Manager you’ll open the “Virtual Switch Manager”.

2017-05-04_13-35-28.png

If you have “Virtual Switches” you can change to, do that and your Virtual Machine should be up and running when powering it on again, removing error code 32788.

If not, we need to set up a new “Virtual Switch“. For me in this example we’ll be picking “External” as I want this VM to be connect through my physical network adapter, and access a physical network.

2017-05-04_13-38-37.png

Then to proceed choose “Create Virtual Switch”

2017-05-04_13-43-23.png

Create the “Virtual Switch” and go back to “Settings” on the affected VM(s)

mmc_2017-05-04_13-30-32.png

 

Pick the “Virtual Switch” we just created and let’s get that VM up and running!

mmc_2017-05-04_13-45-51.png

Power on your VM and the messagebox with error code: 32788 should now be gone and you should see your OS running again:

2017-05-04_13-48-19.png

 

Got more articles in the pipeline, if you have any suggestions do tweet me at @UlvBjornsson or leave a comment.

 

5 thoughts on “Hyper-V Manager: failed to change state. The operation failed with error code ‘32788’”

    • Please feel free to elaborate! What other errors causes it or have you experienced it and/or resolved it with? The depicted above was just how I experienced and resolved it for myself in correlation with the changes that had happened on my PC

      Like

      Reply

  2. Please follow below the mentioned steps for resolve above issue.
    1) Copy old .VHD file on different path.
    2) Then after create new Virtual Machine.
    3) User existing . VHD file with same configuration.
    4) Power on machine. It will be showing your Virtual Machine as it is.

    Liked by 1 person

    Reply

Leave a comment