Closed skyblaster closed 6 days ago
What issues are you seeing? I have not verified the details, but certificates for codesigning only have to be valid at the time of signing, as long as the signing timestamp is included, this is done by Microsoft, so it would be a horrible oversight if they missed that.
As such, even if any part of the chain is now after the NotAfter timestamp, it shouldn't be relevant.
False alarm. My issue is with Hyper-V where I see the following:
On a Lenovo X390, I was able to boot the same boot.wim successfully.
Looks like the cert expired on 2024-10-16. Hopefully it's not too long of a process to renew.
EDIT: My apologies, it's the "Microsoft Windows UEFI Driver Publisher" cert that has expired.