SOLVED

[ISSUE] b20262 Hyper-V MMC havoc after IPU from b20257

MVP

affected build: b20262

previous build without issues: b20257

upgrade method: setup /auto upgrade /dynamicupdate enable

 

After opening the Hyper-V MMC I saw one duplicate of each VMs with a critical saved issue.

The VMs were set to saved before the IPU (of course). This is the first build where this is happening since the first LTSC vServer Next version.

 

Closing and opening again some more duplicate appeared.

The saved VMs are fine though (thankfully).

 

K_Wester-Ebbinghaus_0-1605749396934.png

 

 

2 Replies

Dear @Elden Christensen are there other reports like this? 

Upgraded to b20270 but this will not revert the issue.

K_Wester-Ebbinghaus_0-1607012817261.png

 

best response confirmed by Karl_Wester-Ebbinghaus (MVP)
Solution

good news: b20282 does allow to delete the orphans in Hyper-V MMC

https://aka.ms/AAaum04

1 best response

Accepted Solutions
best response confirmed by Karl_Wester-Ebbinghaus (MVP)
Solution

good news: b20282 does allow to delete the orphans in Hyper-V MMC

https://aka.ms/AAaum04

View solution in original post