locked
Windows Store app not in custom driver privilege list

    Question

  • I posted this in the Tailoring your Windows Store app for hardware and devices forum but that is not a forum that receives priority support so I have re-posted here.  Hope that's okay!

    I am developing a Windows Store App that communicates with a driver like the sample here http://code.msdn.microsoft.com/windowsapps/Custom-device-access-sample-43bde679. 

    I have followed the example but get an E_ACCESSDENIED when calling ICreateDeviceAccessAsync::GetResult().

    Here is a sanitized TraceView dump of deviceaccess.dll using my Windows Store App and custom driver:

    DeviceAccess	DeviceBroker: Opening handle for instance path \\?\ACPI#XXX3400#2&daba3ff&1#{0043cbde-43a1-481a-a5a7-30e23f38321e}
    DeviceAccess	DeviceInterfaceAccessCheck:  Entering for class GUID {0043CBDE-43A1-481A-A5A7-30E23F38321E}.
    DeviceAccess	DeviceInterfaceAccessCheck: Device interface path \\?\ACPI#XXX3400#2&daba3ff&1#{0043cbde-43a1-481a-a5a7-30e23f38321e} is restricted.
    DeviceAccess	DeviceInterfaceAccessCheck: Opening restricted interface; checking for AppID match.
    DeviceAccess	DeviceInterfaceAccessCheck: Checking for package "abcd.efgh.ijkl_gyer1wweeafyy" in privileged list for path \\?\ACPI#XXX3400#2&daba3ff&1#{0043cbde-43a1-481a-a5a7-30e23f38321e}.
    DeviceAccess	DeviceInterfaceAccessCheck: Container for path \\?\ACPI#XXX3400#2&daba3ff&1#{0043cbde-43a1-481a-a5a7-30e23f38321e} is {00000000-0000-0000-FFFF-FFFFFFFFFFFF}.
    DeviceAccess	DeviceBroker: Failed access check with hr 80070005.
    DeviceAccess	DeviceBroker: Exiting OpenDeviceFromInterfacePath with hr 80070005.

    Note that the privileged app list does not have any entries!

    For comparison, TraceView dump of deviceaccess.dll using the custom device access example (I have an OSR USB-FX-2 learning kit):

    DeviceAccess	DeviceBroker: Opening handle for instance path \\?\USB#VID_0547&PID_1002#6&58d4601&0&2#{573e8c73-0cb4-4471-a1bf-fab26c31d384}
    DeviceAccess	DeviceInterfaceAccessCheck:  Entering for class GUID {573E8C73-0CB4-4471-A1BF-FAB26C31D384}.
    DeviceAccess	DeviceInterfaceAccessCheck: Device interface path \\?\USB#VID_0547&PID_1002#6&58d4601&0&2#{573e8c73-0cb4-4471-a1bf-fab26c31d384} is restricted.
    DeviceAccess	DeviceInterfaceAccessCheck: Opening restricted interface; checking for AppID match.
    DeviceAccess	DeviceInterfaceAccessCheck: Checking for package "microsoft.sdksamples.customdeviceaccess.cs_8wekyb3d8bbwe" in privileged list for path \\?\USB#VID_0547&PID_1002#6&58d4601&0&2#{573e8c73-0cb4-4471-a1bf-fab26c31d384}.
    DeviceAccess	DeviceInterfaceAccessCheck: Container for path \\?\USB#VID_0547&PID_1002#6&58d4601&0&2#{573e8c73-0cb4-4471-a1bf-fab26c31d384} is {BC1A0B61-1886-11E2-BE9A-888888888788}.
    DeviceAccess	DeviceInterfaceAccessCheck: Found privileged app list.
    DeviceAccess	DeviceInterfaceAccessCheck: Found package "Microsoft.SDKSamples.CustomDeviceAccess.JS_8wekyb3d8bbwe" in privileged list; not a match.
    DeviceAccess	DeviceInterfaceAccessCheck: Found package match.
    DeviceAccess	DeviceBroker: Successfully brokered handle.
    DeviceAccess	DeviceBroker: Exiting OpenDeviceFromInterfacePath with hr 0.

    I followed the exact same Driver->Device Metadata->Authoring, reboot, disable driver signiture enforcement, install driver, steps in both cases.

    Is the driver metadata information compiled into the driver .sys file or is it part of the install process?  I ask because my driver was converted over from a build.exe command line project and the installer package used is not the same as that provided by VS2012 by adding a Driver Install Package project.  Further complicating matters is that the install package installs six different .sys files, but only one needs to grant access to my Windows Store app.

    Is there anything else I can do to debug/resolve why my driver does not have a privileged apps list?

    Thanks!

    • Moved by Mike Feng Tuesday, October 23, 2012 11:10 AM windows Store App (From:.NET Platform Architecture Development Discussions)
    Monday, October 22, 2012 10:46 PM

All replies

  • Hi Shiftlook,

    Sorry for that you don't get response at that forum.

    But this thread is off-topic here, it is needed to be moved the right forum to wait the responses.

    Thank you for your understanding and support.

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, October 23, 2012 11:09 AM
  • Friday, November 02, 2012 4:53 AM
  • Thanks for the link Lisa.  However, the thread does not contain any documentation on how to create PC-internal metadata and how to load it.  A quick internet search for "PC-internal metadata" doesn't return anything relevant.

    Can you point me to documentation for PC-internal metadata?

    Friday, November 02, 2012 3:10 PM