Deactivating "Secure boot" should solve the issue. Within my English blog post Patchday: Windows 11/Server 2022 Updates (February 14, 2023) I've added the following warning:Īddendum: I got several reports from German blog readers, saying, that their virtual machines can't boot either due to a "security violation" or due to a missing boot manager. I then pointed Dennis to the discussion on the blog. A server in VM version 16 was not affected, there was no secure boot option. Interestingly, the 3 requirements had to coincide in my case. If I now disable the security boot in the VM options, the server starts again as usual: Using the console, you can still see the following before going into the boot options: I have the following problem with a customer (Server 2022): If there is a VM in version 19, the server member is a domain and receives the February update (KB5022842), the server does not survive the next reboot. I don't know if we are a unique case, but since today we have a problem that I would like to share with you. also contacted me by e-mail and reported the error at the VMs:įirst of all, thank you for your website, it has helped me a few times. By disabling VBS and Secure Boot the VM boots up again. User #4: Same problem with our Win 2022 server VMs.
update and will not boot.įirst comes: Windows Boot Manager… Security ViolationĪfter update the server is running, after further bootĭisabling the Secure Boot solves the problem User #2: Windows Server 2022 with Secure Boot / VBS enabled in the VMware are having problems after the Feb. User #1: My template Win 2022 VM does not boot up after the update once you turn it off. Shortly after the German edition of this post was published, users already came forward reporting issues (I've translated the comments).
Did you had any other components installed such as Microsoft hotfix( ), Microsoft iSCSI initiator boot version etc.I had presented the security update KB5022842 released for Windows Server 2022 in the blog post Patchday: Windows 11/Server 2022 Updates (February 14, 2023). ClassGUID, Service, DriverPackageId etc) manually. INF file for various device-ids, added some of them in CDDB with usual values (i.e. How to add entries in CDDB? I don't think there is any tool that does this. Did you added Service entry inside registry and copied. I did both of these things manually in addition to using PnPutil.
How did you install the driver for new NIC? Using PnPUtil? Because it neither creates Service entry in registry nor copies the.
Infact, lot of other forums also say that adding only CDDB entries does not solve this problem and hence this is still vastly unanswered.Īssuming, I must have entered wrong Device-ids in CDDB, I've few questions for you:ġ. You actually got this to work? Adding few Device-Id entries into CDDB did not solve my problem.
0 kommentar(er)
