Anyone having issues with the April patches (KB5082123) causing Server 2019 VDAs on PVS to not boot? Ours are failing to obtain an IP and never actually get to the PVS server to pull the image.

SecureBoot? That's the type of issue I had with 2604.

That's what's confusing me, we don't have Secure Boot enabled in our PVS image template.

Hm ok so SecureBoot is turned off on the VM itself ?

We're an App Layering shop. The template used for packaging VMs does have Secure Boot enabled, but the template used for PVS target devices has it disabled. I'm building a new OS layer version now with a template that has Secure Boot disabled to see if that changes the behavior.

OK also for me, when I install 2604 on an Hyper-V VM, it updated the network drivers killing PVS. Had to rebuild a ref img. So I had 2 issues, this one and then secureBoot. Could be the same for you.

This particular image is running 2402 CU2

They don't make our life easy for sure ... I was on 2402 CU3. Now CU4

For the record, this is what we're seeing

Yeah typical on when the PVS network driver got overwritten because 2604. Anyway it sounds like a network card issue to me.

We're also on VMware ESX 8.0 U2. Not the version that supports the new CA stuff.

I'm Hyper-V, drivers got updated. Reinstalling the PVS target didn't fix it, I could fix a similar issue on XenServer this way.

What exactly was your fix in the end?

I created a new ref image via MDT then converted it to PVS.

Okay. Definitely different for us being on App Layering.

Hm not sure but I've seen this in VMware causing this type of boot issue.

No, I figured out what this is. Whoever created the template for AL fucked it up and included two NICs - an E1000E and a VMXNet 3