Maciej Szeptuch

Works fine for me, it must be something either with the values you're trying to set or maybe your firmware doesn't like some flag that we're setting by default :thinking:...

I think I fixed this with https://github.com/Neverous/efibooteditor/pull/98, can you try latest build from https://github.com/Neverous/efibooteditor/releases/tag/latest ?

Awesome, thank you. Closing this then. Feel free to reopen in case it resurfaces.

Do you see anything, is the timeout registered correctly? Can you share the raw dump (`Help -> Dump raw EFI data`) if it has anything? What's the motherboard model? BIOS...

Yeah, completely nothing :disappointed: Interesting, if there are no errors showing up, not sure what could that be, maybe some option in the BIOS to limit the OS access as...

For what to install I recommend reading https://github.com/Neverous/efibooteditor/blob/master/INSTALL.md. None of the artifacts are guaranteed to work outside of the build environment but I've been pushing the `EFIBootEditor-*-windows-2022-qt-*-MSVC.msi` to winget and...

For now, yes :crossed_fingers:

Yeah, everything looks normal :confused: I adjusted some things and added additional debug output to raw dump. Could you try raw dump (`Help -> Dump raw EFI data`) from [this](https://github.com/Neverous/efibooteditor/actions/runs/9620724708/artifacts/1626689407)...

Oh, you're right I'm putting the wrong runtime libraries (release versions) in the debug packages :construction_worker:

[This one](https://github.com/Neverous/efibooteditor/actions/runs/9723351200/artifacts/1651218754) should be able to start.