PXE Boot affected by Microsoft sbat desaster

Hi.

It just happened to me on a freshly installed and subsequently patched W11 Machine which is set to boot PXE primarily, that after the Patch, it wouldn't even start PXE any longer. I have a (very blurry) image of the error. Essentially, it doesn't like the NBP file (ZCM 24.02).

"NBP file downloaded succesfully.
Verifying shim SBAT data failed: Security Policy Violation
Somethung has gone seriously wrong: SBAT self-check failed: Security Policy Violation"

Like I said, the only change between succesful PXE imaging via Winpe , and this message on booting, was Windows Updates for the fresh W11.


Disabling Secure Boot helps. Just notifying.

Parents Reply Children
  • 0   in reply to   

    As the problem occurs well before any difference between Linux and PE even comes into play, still inside the PXE stack, both are affected *by this* problem. E.G, you can't even get to manually invoke the PXE menu.
    Of course, once there is a working NBP file, it is still possible that afterwards the Linux Kernel would still fail too.