Once secure boot has been disabled updates will be installed without issues, once updates have been deployed Secure Boot can be safely enabled once again, unfortunately, to do so you need to shut down the VM so think about it in advance.
Secure boot can be disabled accessing the VM settings and under the Firmware section untick the Enable Secure Boot checkbook: In the machine log files I could not find anything relevant or that could help me solve the issue and what I found weird was that I was experiencing this issue only with Generation 2 Hyper-V machines this ringed a bell as in the past I already experienced some “weird” interactions between Hyper-V secure boot, a feature enabled by default in Generation 2 VMs, and the guest Operating System, I have tried to disable secure boot et voila the update process went through correctly and I was able to install updates in my Windows 2012 R2 machine. I let the VM run for some time, around 30 minutes, and unfortunately, nothing happened the server seemed completely stuck, as this was just a test system I just deleted the VM and recreated from scratch but again after updates I was welcomed by the WE couldn’t complete the updates message.
Today I was deploying some new VMs to my lab as part of the deployment work I was updating the Windows 2012 R2 template with latest OS updates, the download and installation update worked correctly but when I rebooted the server I noticed updates installation was failing with the not so specific error message W e couldn’t complete the updates Undoing changes below a screenshot of the issue:
0 kommentar(er)
