Surprising to see the (intel based) Aurora-R12 on that list but there it is (it starts with yours).

You are always welcome to Wait and/or Do Nothing.

As long as you don't buy-stuff online or do online-banking ... you should be fine.

 

But you did post this message, so if you want me to take a look at your Summary Report,

https://www.dell.com/community/en/conversations/xps-desktops/xps-8930-purchased-2018-2023-secure-boot-certificates/699cdb010daada5e7a6c379f?commentId=6a1a2ebe5e24e611a5a521fc

... just post it here in this thread and I'll be glad to take a look. That is the only way I could possibly to give you anything even resembling a definitive answer. 

Since you have an Aurora-R12, I was thinking we should keep your stuff here, in this thread.

May I ask the year when you purchased it?

This is the CA2023 Report you posted:

 

As new as it is, and with the recently dated BIOS-Firmware available (and installed) ... it is interesting that the (motherboard linked) KEK is missing ... from Default (and therefore can't be loaded into Current by automation).

 

This leads me to believe that ALL the UEFI-class Auroras (R12 and older, like back to at least R5) with the Pegatron-made motherboards are missing a valid 2023 KEK. I know my Aurora-R6 was.

The rest looks pretty good (notice all the other Green and Success in Current categories).

Like the XPS-8930 owners, I suggest you go ahead and manually update your KEK. 

https://www.dell.com/community/en/conversations/xps-desktops/xps-8930-purchased-2018-2023-secure-boot-certificates/699cdb010daada5e7a6c379f?commentId=6a1de953e9dae665cdc6064a

@Tesla1856​ 

Thank you for all the help you’ve given to me and the other users facing this issue, I really appreciate you sharing your knowledge.

I’ll go ahead and look into updating the KEK as you suggested, but I’m going to make a backup first. Instructions in the linked thread seem clear but I’ll get back to you if I have any questions/issues.dell has no plans push a KEK cert update :/

Thanks again and have a great day.

@Tesla1856​ 

Hello! Giving an update as I did try manually updating the KEK as suggested with not so wondrous results. Not your fault but just wanted to document it here in case you have suggestions and/or anyone else comes across this thread.

I followed @swf-uk’s June 12th, 2026 instructions in the thread you previously linked (page 7) as they were the most clear and concise to me. I did follow all steps correctly, including unblocking the file before copying and appending the file, but on restart ran into the "Secure Boot Violation - Invalid Signature Detected" screen.

What fixed this for me was following this Reddit thread that specifically is about the Aurora R12, and it got my computer running back in secure boot mode like before I attempted this manual update.

https://www.reddit.com/r/Alienware/comments/1tsv8qq/secure_boot_violation_invalid_signature_detected/


However when running the check again, the "Current UEFI DBX" area has changed now, instead showing the following (apologies that I can't upload images at this moment):

Current UEFI DBX
2025-10-14 (v1.6.0) : FAIL: 404 failures, 27 successes detected
Windows Bootmgr SVN : None
Windows cdboot SVN  : None
Windows wdsmgfw SVN : None

I was hoping for your advice on my situation and what this specific error could mean. I was also wondering if you were familiar with garlin's PowerShell scripts for updating Secure Boot CA 2023, which is another option for updating my certs I might try later. But for now until I learn more about the Aurora R12 in particular, I will hold off on updating my certs. Thank you again.

@Tesla1856​ 

Thank you for all your help in assisting me with my questions.

I’ll do as suggested in the other thread and let the carts rebuild before attempting another update. I probably won’t try for a bit. But it’s good to know I have options to restore the secure boot validity through either the key reset or the USB drive options.

I’ll reply to this thread if I have further questions. Your help in this community is truly appreciated!

@Tesla1856​ 

Hi Tesla, apologies for pinging you on this thread again.

After having to fix my keys, my Current UEFI DBX section is still showing as “2025-10-14 (v1.6.0) : FAIL: 404 failures, 27 successes detected” when previously it showed as “2026-06-09 [AMD64] : SUCCESS : 443 successes detected.”

You mentioned in your last reply that “The DBX will need to rebuild,” but I was wondering how exactly does that happen? Is that part of Windows’ Monthly Security Update and it will automatically happen? Or do I need to trigger it manually through BIOS and/or the Script-Package “Apply DBX update.cmd” in a way?

Thank you if you’re able to respond.

@PumpkinPiePot​ ,

 

@Tesla1856​ 

1. Hi Tesla, apologies for pinging you on this thread again.

2. After having to fix my keys, my Current UEFI DBX section is still showing as “2025-10-14 (v1.6.0) : FAIL: 404 failures, 27 successes detected” when previously it showed as “2026-06-09 [AMD64] : SUCCESS : 443 successes detected.”

3. You mentioned in your last reply that “The DBX will need to rebuild,” but I was wondering how exactly does that happen? Is that part of Windows’ Monthly Security Update and it will automatically happen? Or do I need to trigger it manually through BIOS and/or the Script-Package “Apply DBX update.cmd” in a way?

Thank you if you’re able to respond.

1. No problem. Would be nice to get that Aurora-R12 back in the game.

2. Yeah, I see you went off-script and played with your \EFI folder. I'm guessing your current situation has something to do with that or the derailment during the original Append attempt.

3. Yes, your DBX still needs updating.

In the Script-Package, try running "Apply DBX update.cmd" as Admin.

Then use computer normally, run Windows-Update, do some Reboots.
Periodically, check for progress by running the CA-2023 Reporting script. It should eventually be a number in the 400's and say Success in green.