Microsoft-Windows-Devices-AccessBroker

15 events across 1 channel

Event ID 100 — %1 (pid = %2) successfully accessed %3.

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) successfully accessed %3.

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath

Event ID 101 — %1 (pid = %2) successfully accessed %3, the device interface class is unrestricted and allows access for LPAC apps.

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) successfully accessed %3, the device interface class is unrestricted and allows access for LPAC apps.

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath

Event ID 102 — %1 (pid = %2) successfully accessed %3, the device interface class is unrestricted.

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) successfully accessed %3, the device interface class is unrestricted.

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath

Event ID 103 — %1 (pid = %2) successfully accessed %3, the app is granted unrestricted access based on its capabilities.

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) successfully accessed %3, the app is granted unrestricted access based on its capabilities.

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath

Event ID 104 — %1 (pid = %2) successfully accessed %3, the device container grants this app unrestricted access.

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) successfully accessed %3, the device container grants this app unrestricted access (i.e. legacy privileged app).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath

Event ID 105 — %1 (pid = %2) successfully accessed %3, the system is in embedded mode and the app has the low level devices capability.

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) successfully accessed %3, the system is in embedded mode and the app has the low level devices capability.

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath

Event ID 200 — %1 (pid = %2) failed to access %3 (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3 (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 201 — %1 (pid = %2) failed to access %3, the user cannot access the device (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the user cannot access the device (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 202 — %1 (pid = %2) failed to access %3, the interface class is unrestricted but does not allow LPAC apps access (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the interface class is unrestricted but does not allow LPAC apps access (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 203 — %1 (pid = %2) failed to access %3, the interface class is restricted and the app is LPAC (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the interface class is restricted and the app is LPAC (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 204 — %1 (pid = %2) failed to access %3, the interface class is custom and nothing gives the app access (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the interface class is custom and nothing gives the app access (error = %4).

                 One of the following methods may be used to grant an app access to a custom device:
                 - an interface class may define access policy for either allowing unrestricted access or access restricted to a specific capability
                 - a device interface instance may grant access to apps based on well-known or custom capabilities
                 - (Deprecated) Privileged App Support: device metadata may grant access to specific PFNs associated to device container's PnP state

                 Note: custom capabilities are typically the correct way to enable an app to access a custom device.

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 205 — %1 (pid = %2) failed to access %3, the interface class is restricted by policy (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the interface class is restricted by policy (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 206 — %1 (pid = %2) failed to access %3, the interface instance is restricted (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the interface instance is restricted (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 207 — %1 (pid = %2) failed to access %3, the interface class does not allow raw handles to the device (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the interface class does not allow raw handles to the device (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error

Event ID 208 — %1 (pid = %2) failed to access %3, the capability access check was denied (error = %4).

Provider
Microsoft-Windows-Devices-AccessBroker
Channel
System

Message

%1 (pid = %2) failed to access %3, the capability access check was denied (error = %4).

Fields

NameDescription
ClientFileName
ClientPid
InterfacePath
Error