Hi Fabian, I was affected by this. After an update, one Dell R710 server that I maintain, failed to boot. The error I saw was the same as someone else who also posted here. I didn't know how to fix it, and needed the server to be running, so I just reinstalled it, and switched to biosboot while at it. Fortunately, this was a backup server, so the impact was low. It has a production counterpart, but I don't dare update it, and I cannot risk it failing to boot after an update. Regards, Anand On 06/12/2018 10:44, Fabian Arrotin wrote: > > We got some reports from people unable to reboot their nodes after > updating to 7.6.1810, and basically to newer shim (v15). > It seems to affect only nodes in UEFI mode, but without SecureBoot. > > We wrote that in the ReleaseNotes, including a link to the bug report : > https://bugs.centos.org/view.php?id=15522 > > We have now a workaround in that bug report, and also a new interim > build (not signed by Microsoft yet) but we need feedback , as the only > node on which I could test this myself is my old 2008 iMac computer .. :-( > > Once we'll have enough positive (but also negative) feedback about this > new build, we'll be able to send to Microsoft for signing and so > consider that bug closed. Worth also noticing that if we can have that > ready in the updates, we'll be able to spin a monthly iso that will then > work on such uefi nodes too. > > Kind Regards, > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >