Secure Boot Logo test "VerifyBootServicesVariableBehavior" Failure RRS feed

  • Question

  • Hello everyone,

    I'm testing MB with WHCK and i can't pass secure boot logo test. It fails on "VerifyBootServicesVariableBehavior", everything else is OK. I have installed default PKpub, KEK, db, dbx keys.

    Part of the log:

    <Error File="Need_Symbols" Line="0" ErrCode="0x0" ErrType="" ErrorText="Error 0x00000000" UserText="AreNotEqual(0, 0) - After ExitBootServices(), attempting to call GetVariable() on an existing variable with attributes "NV,BS" should fail." CA="14041839" LA="14041988"><Data><WexTraceInfo ThreadId="3180" ProcessId="3164" TimeStamp="2546190488"/><WexContext>Verify</WexContext></Data><rti id="1172693215"/><ctx id="233224479"/></Error><EndTest Title="Microsoft.UefiSecureBootLogo.Tests.VerifyBootServicesVariableBehavior" TUID="" Result="Fail" Repro="" CA="14048162" LA="14048272"><Data>

    Maybe someone had experienced this problem, and know possible ways to fix it?

    i tried BIOS update, MB with different revision.

    Thank you.

    Wednesday, January 16, 2013 2:42 PM

All replies

  • After configuring and enabling Secure Boot, did you perform a Windows restart?  If you did not, then please restart Windows ("shutdown /r") and re-run the test.  If you did, this is a firmware bug.  It existed in older builds of Tiano Core and the EDK/UDK.  

    When Windows 8 boots on a UEFI system with Secure Boot Enabled, a variable with attribute NV+BS (0x3) is created prior to ExitBootServices().  This test case attempts to Get that variable after ExitBootServices() is called.  The UEFI Specification says that this should fail.  On your system(s), this succeeded which is a firmware bug.  Refer to UEFI Specification Version 2.3.1, Errata C, June 27, 2012, Section 7.2, GetNextVariableName(), page 215.

    Best Regards, J Cox [Microsoft] “This posting is provided AS IS with no warranties, and confers no rights.”

    • Proposed as answer by JJ Cox Monday, January 21, 2013 3:53 PM
    Friday, January 18, 2013 6:00 PM
  • Thank you for the answer. Yes, i have restarted windows, but problem still persists. I'll ask the manufacturer for new firmware.
    Monday, January 21, 2013 7:17 AM