Nope... bootable USB sticks *Still* fail with UEFI Secure Boot enabled.
Backupper is a decent app for disk/partition image backups, but in the case of a disk/SSD failure, you need to have the full version installed in another copy of Windows, either on a Windows to Go drive that you know will boot the PC/laptop that experienced the failure, or attach the replacement drive to another PC/laptop before you install it. You can disable secure boot, then go through the [2 step in my experience] process re-enabling it, but you shouldn't have to, and if the reason for restoring a backup is you were bit by malware, you probably shouldn't.
Anyway, installed Backupper in a Win11 VM, created the Linux & WinPE USB sticks, & gave them a try just in case AOMEI fixed things. They haven't. Going the extra mile, I created an ISO in Backupper so I could give the new [just out] version of Rufus a try -- Rufus is a small app that can take an ISO and put it on a bootable USB stick. This is the message I got from Rufus:
Rufus detected that the ISO you have selected contains a UEFI bootloader that has been revoked and that will produce a Windows Recovery Screen (BSOD) with 'Error code: 0xc0000428', when Secure Boot is enabled on a fully up to date UEFI system.
As mentioned in an earlier post, or just Google "fix for CVE-2023-24932" [w/out quotes], Microsoft is redoing the way Windows boots. Their fix includes changing the way the BIOS connects to &/or uses the boot loader. I think there's a possibility that turning off secure boot to use the Backupper USB sticks may not work once that fix is pushed out to all the Win10 & 11 devices, but we probably won't know until then. If you choose to go the route of turning off Secure Boot to use those USB sticks, you'll need to test them again at that time.
giveawayoftheday[.]com/forums/topic/470687