EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

Hope someone can help. I have only been using KDE Neon for the last three months, single boot, no more Windows, and so far so good. However, I noticed a warning message yesterday (but thought it might have gone away today) when I booted my machine in the morning. It’s just showing for a few seconds, before it boots into the login screen - here’s a picture of the message:


About my System - from Info Centre:
Operating System: KDE neon 6.3
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-19-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Memory: 6.7 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: Acer
Product Name: Aspire A315-41
System Version: V1.18

I have searched the internet and found a lot of old and contradicting advice, and I am worried that whatever I try to fix it might fail and break my system.
Has anybody come across this warning recently and managed to fix it?
Any help is greatly appreciated. Thanks!

1 Like

Hi - I’m not a daily Neon user myself, but this does seem to have come up as a broader issue on some other Ubuntu-based distributions as well. Maybe some of the ideas tried for those would be helpful here too? boot - EFI stub: WARNING: Failed to measure data for event 1: 0800000000000000b EFI stub - Ask Ubuntu

Thank you. I’ll try the approach described in this link and let you know. :crossed_fingers:

1 Like

Hi John, so I booted into my BIOS ready to follow these steps. However, when I entered the Security Screen there was no option to change Standard to Custom, and therefore, none of the other steps described in the link would apply. Here’s a picture of the Secure Boot Mode of my machine:


I don’t know what any of the options will do exactly and whether any change will break my machine. So will need to do more research. As always, any guidance is greatly appreciated. Thank you :+1:

Did more research, lots of information out there, although, no clear statement anywhere that restoring Secure Boot to Factory Default is safe.

However, I read through the 4 steps that a Kubuntu user posted to fix this issue, again and again (see link above posted by @johnandmegh), and it finally hit me that in my case I may not have to follow all the steps, as the warning wasn’t due to a modified secure boot key in EFI (I certainly never attempted any modification). Therefore, I just tried the very last step, disabling Secure Boot in my BIOS, and to my surprise it worked :+1: The error message disappeared :slightly_smiling_face:
I’ll mark this post as resolved.

Can anyone help? After yesterday’s system update in KDE Neon the same message shows up again during boot, despite having Secure Boot disabled. In the boot folder there are two files that were updated as part of the system update:

  1. initrd.img
  2. initrd.img-6.8.0-56-generic

It’s likely that other files were updated but these were the only files updated in the boot folder.
None of the tips I found after extensive search helped to fix it.
If anyone has any idea why this happens and how to fix it I would be very grateful.
Latest system info from Info Centre (changed to original post in bold):
Operating System: KDE neon 6.3
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-19-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Memory: 6.7 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: Acer
Product Name: Aspire A315-41
System Version: V1.18

Or is it time to raise a bug, and how would I go about it?
Thanks everyone.

1 Like

Finally had time to look for further guidance and came across a post that suggested to use:

sudo apt autoremove

That fixed it for my machine, and it also freed up ca. 2.7GB (incl. numerous old kernels) in the clean up process :+1:

Thank you for your post and solution as it also worked for me. It is a concern as one of the unused applications removed must be executed as part of the grub boot. All control file and app references should have been automatically updated. Maybe a dependency missing from the definition of an app.

1 Like

sudo apt autoremove worked for me also.

1 Like