Jump to content

f4pf4p

Member
  • Content Count

    3
  • Joined

  • Last visited

  • Medals

Posts posted by f4pf4p


  1. some extra information btw,

    ive been looking into Test-signing on windows thats causing the problem,

    i HAVE test-signing turned off... here are my bcdedit settings:

    Windows Boot Manager

    --------------------

    identifier {bootmgr}

    device partition=\Device\HarddiskVolume2

    path \EFI\Microsoft\Boot\bootmgfw.efi

    description Windows Boot Manager

    locale en-US

    inherit {globalsettings}

    integrityservices Enable

    flightsigning Yes

    default {current}

    resumeobject {a0c0ae4d-952f-11e4-9bef-b0198c7409f5}

    displayorder {current}

    toolsdisplayorder {memdiag}

    timeout 0

    Windows Boot Loader

    -------------------

    identifier {current}

    device partition=C:

    path \WINDOWS\system32\winload.efi

    description Windows Technical Preview

    locale en-US

    inherit {bootloadersettings}

    recoverysequence {a0c0ae4b-952f-11e4-9bef-b0198c7409f5}

    integrityservices Enable

    recoveryenabled Yes

    testsigning No

    isolatedcontext Yes

    flightsigning Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \WINDOWS

    resumeobject {a0c0ae4d-952f-11e4-9bef-b0198c7409f5}

    nx OptIn

    bootmenupolicy Standard

    so as the bcdedit says: testsigning NO.

    this might be something battleye is ignoring.

    if anyone else of you want to try this:

    open cmd as an admin and type: Bcdedit.exe -set TESTSIGNING OFF

×