SetVariable called security violation / Setup_Var

Hello, does anyone know what this means??

SetVariable called security violation

When i tried to unlock FPRR and BIOS Lock with
AmiSetupWriter.efi 0x1C 0x0

What can i do?

No one?

Obviously not.
What about entering „setup_var“ into the Forum‘s search box?

How about you search Setup_Var in the search box, and realize nothing comes up about this error, im would’ve not make a new thread if i could have found the answer.

I tried:
AmiSetupWriter.efi
UVT (UefiVarTool)
Normal Setup_Var
And RU.efi

All Setup_Var give Security Violation.
RU.efi straight up reverts the changes.

Hi there! What’s your machine and BIOS/UEFI version? I’ve never seen that message from setup_var. There’s also an EFI command line tool you could try. Perhaps your BIOS has additional security measures blocking you from changing these values.

Hi, thank you for answering!
I have encountered this issue with both my PC and my friends laptop.
My mobo is a: ProArt Z790-CREATOR WIFI.
My friends laptop: ASUS TUF 15 Gaming FX506HM
I tried dumping the bios using Intel FPT, and using (UEFI Editor), and there is an option called: “UEFI Variables Runtime protection”.
This on both PC’s.
My friend already buyed an external programmer, in case that’s the only solution available.

I’m not familiar with that UEFI variables runtime protection. You could use the programmer and change the default value of that variable, but I can’t say for sure it could work.

You can always check the EDK2 specifications for error codes:


So the variable you wanna write has the attribute EFI_VARIABLE_TIME_BASED_AUTHENTICATED_WRITE_ACCESS or EFI_VARIABLE_ENHANCED_AUTHENTICATED_ACCESS set. setup_var has no checks for this / doesn’t follow the specs, it just blindly tries to set the new variable value. Either write your own application to do that and follow the specs or edit the variable value in the dump (maybe your firmware has more checks in place though, I don’t know).

Thank you so much, im gonna look deeper in this! :smiley: