I recently updated my home machine where I run my lab to Windows 10 Anniversary Update. I went to try out creating my lab fresh in Lability again, and I noticed that Hyper-V did not like the image hash of WS2016 TP5 image (Id: 2016TP5_x64_Standard_EN) on first boot when I recreated the lab. It tries to do a PXE network boot via IPv4, then it comes up to a screen with a message that list the boot order and next to the SCSI disk (which is listed first) it has a message "The image's hash was denied (DBX)." (I made sure to use freshly downloaded ISO's and hotfixes and everything.)

Even if I turn off secure boot, I get a different error message from the boot window: "Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. Choose your language settings, then click 'Next.' 3. Click 'Repair your computer.'"

WS 2012 R2 and latest W10 media appear to still be totally fine, it was just WS2016 TP5 that had this issue. (Didn't try TP4.) Also I assume Windows 8.1 is probably fine, too.

Curious if anyone else ran into this issue with the latest W10 Anniversary Update on their host machine, and WS 2016 TP5 as a guest? (Btw this issue was present before I added / tried out change in #129 PR which adds June 28, 2016 CU to WS 2016 TP5 media hotfixes. Adding that had no effect.)