DL380 Gen10 Windows Server 2012 R2 | Vm Failed to change state

[VPeter84]

I first updated firmwares with P52575_001_gen10spp-2022.03.0-SPP2022030.2022_0326.24 SPP, which was recently downloaded, SHA-256 Hash was fine.
- Booting the server from SPP, we installed everything you wanted
After installing Windows Server 2012 R2, I made a unique ISO for the drivers via the HPe Support page - Hash was fine here as well
- Drivers are installed fine, there is no unknown hardware in the device manager
The problem is the following:
- On a RTM 2012 R2 server, with the Hyper-V role enabled and a new VM created
-VM can be started fine.
- Installation of 107 updates from RTM status
-VM can be started fine
- Then in the next update round, the 2022-09 Monthly Security Quality Update for Windows Server 2012 R2 x64-based systems (KB5017367) will be added, and the VM cannot be started then "Failed to change state" is the message in the error window
o Event ID 3040 error
o There are no errors in the Hyper-V-VMMS Event viewer
o Error codes Event ID 3430 and 3040 can be found in the Hyper-V-Worker Event viewer
- If I remove the KB5017367 update, the VM can be started properly.

Pictures from Event LOG:

[support_s]

System recommended content:

1. Microsoft Windows Server 2012 R2 - Support Guides | Microsoft Windows Server 2012 R2 - BugCheck 9F

2. Microsoft Windows Server 2012 R2 - Support Guides | Microsoft Windows Storage Server 2012 R2 – BSOD with BugCheck D1

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[VPeter84]

I looked at the links, but I didn't find a solution to the error there.
Maybe my description was wrong, but the VM itself doesn't start at all.
Fortunately, this is not yet a productive environment, but only a test for now.
If I remove the KB5017367 update from the Hyper-V host, the VM can be started fine.
There is no operating system installed in the VM yet because the VM itself does not boot. The message Failed to change state is displayed on the Hyper-V host. But the host itself works fine, only the Hyper-V role is not working properly.

[pragav]

Hi,

Is this happening on only one server? or multiple?

Since you have mentioned that If you remove kb5017367 it works fine, It could be a issue with this update. Since Microsoft has not posted any known issues regarding this update, I am wondering if this is widespread issue. 

Anyhow can you please try to manually install any of the older rollup updates like August or July 2022 Rollup on this server and check if you still see the same behavior?

[VPeter84]

HI,

It affects several servers, because these are new purchases.
Fortunately, it is not a productive environment, but it would be good to use them in the production environment as soon as possible.

The process itself:
I uninstalled KB5017367 update the server
Then I installed the server KB5008263 2021.12 Monthly Rollup on the server --> Hyper-V VM works fine
I intentionally omitted the 2022.01 Monthly Rollup because it was not installed even in the current productive environment
Then I installed the server KB5010419 2022.02 Monthly Rollup on the server --> Hyper-V VM works fine
Then I installed the server KB5011564 2022.03 Monthly Rollup on the server --> Hyper-V VM works fine
Then I installed the server KB5012670 2022.04 Monthly Rollup on the server --> Hyper-V VM works fine
Then I installed the server KB5014011 2022.05 Monthly Rollup on the server --> Hyper-V VM works fine
Then I installed the server KB5014738 2022.06 Monthly Rollup on the server --> Hyper-V VM does not work properly --> Failed to change state

[pragav]

Hi,

So this has started from June 2022 update, Do you see this issue on any WS 2016 server? We need to isolate this issue if its hardware or software related.

I would recommend logging a case with HPE for deep dive troubleshooting since its affecting multiple servers.

[VPeter84 · Accepted solution]

Hi,

I just installed a Windows Server Standard 2016, then brought it up to date from Windows Update.
Then I installed the Hyper-V role.
Hyper-V VM works fine.

Regard, Peter