Microsoft-Windows-Bluetooth-Policy

12 events across 1 channel

Event	Title	Channel	Sample
1	A Bluetooth policy has changed.	Operational	N
2	Bluetooth radio enablement has been PolicyState due to policy …	Operational	N
3	Bluetooth radio has PolicyState advertising due to policy PolicyPath\PolicyName.	Operational	N
4	Bluetooth radio has PolicyState discoverability due to policy …	Operational	N
5	Bluetooth radio has PolicyState radio name as RadioName due to policy …	Operational	N
6	Process Service has attempted to pair to radio BtAddr.	Operational	N
7	Bluetooth has Accepted service ServiceGuid on remote device BtAddr due to policy …	Operational	N
8	Bluetooth has Accepted PSM Psm on remote device BtAddr due to policy …	Operational	N
9	A connection to a remote device bthAddr was successfully established.	Operational	N
10	An attempt to connect to a remote device bthAddr failed.	Operational	N
11	The minimum encryption key size requirement of requiredKeySize octets was …	Operational	N
12	A connection to the remote device bthAddr was rejected because it did not meet …	Operational	N

Event ID 1: A Bluetooth policy has changed.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

A Bluetooth policy has changed. Policy PolicyPath\PolicyName has value of: PolicyValue.

Message #

A Bluetooth policy has changed.  Policy %1\%2 has value of: %3

Fields #

Name	Description
`PolicyPath` UnicodeString
`PolicyName` UnicodeString
`PolicyValue` UnicodeString

Event ID 2: Bluetooth radio enablement has been PolicyState due to policy PolicyPath\PolicyName.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

Bluetooth radio enablement has been PolicyState due to policy PolicyPath\PolicyName.

Message #

Bluetooth radio enablement has been %3 due to policy %1\%2.

Fields #

Name	Description
`PolicyPath` UnicodeString
`PolicyName` UnicodeString
`PolicyState` UnicodeString

Event ID 3: Bluetooth radio has PolicyState advertising due to policy PolicyPath\PolicyName.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

Bluetooth radio has PolicyState advertising due to policy PolicyPath\PolicyName.

Message #

Bluetooth radio has %3 advertising due to policy %1\%2.

Fields #

Name	Description
`PolicyPath` UnicodeString
`PolicyName` UnicodeString
`PolicyState` UnicodeString

Event ID 4: Bluetooth radio has PolicyState discoverability due to policy PolicyPath\PolicyName.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

Bluetooth radio has PolicyState discoverability due to policy PolicyPath\PolicyName.

Message #

Bluetooth radio has %3 discoverability due to policy %1\%2.

Fields #

Name	Description
`PolicyPath` UnicodeString
`PolicyName` UnicodeString
`PolicyState` UnicodeString

Event ID 5: Bluetooth radio has PolicyState radio name as RadioName due to policy PolicyPath\PolicyName.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

Bluetooth radio has PolicyState radio name as RadioName due to policy PolicyPath\PolicyName.

Message #

Bluetooth radio has %3 radio name as %4 due to policy %1\%2.

Fields #

Name	Description
`PolicyPath` UnicodeString
`PolicyName` UnicodeString
`PolicyState` UnicodeString
`RadioName` UnicodeString

Event ID 6: Process Service has attempted to pair to radio BtAddr.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

Process Service has attempted to pair to radio BtAddr.

Message #

Process %2 has attempted to pair to radio %1.

Fields #

Name	Description
`BtAddr` UInt64
`Service` UnicodeString

Event ID 7: Bluetooth has Accepted service ServiceGuid on remote device BtAddr due to policy PolicyPath\PolicyName.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

Bluetooth has Accepted service ServiceGuid on remote device BtAddr due to policy PolicyPath\PolicyName...

Message #

Bluetooth has %1 service %2 on remote device %3 due to policy %4\%5...

Fields #

Name	Description
`Accepted` UnicodeString
`ServiceGuid` GUID
`BtAddr` UInt64
`PolicyPath` UnicodeString
`PolicyName` UnicodeString

Event ID 8: Bluetooth has Accepted PSM Psm on remote device BtAddr due to policy PolicyPath\PolicyName.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

Bluetooth has Accepted PSM Psm on remote device BtAddr due to policy PolicyPath\PolicyName...

Message #

Bluetooth has %1 PSM %2 on remote device %3 due to policy %4\%5...

Fields #

Name	Description
`Accepted` UnicodeString
`Psm` Int16
`BtAddr` UInt64
`PolicyPath` UnicodeString
`PolicyName` UnicodeString

Event ID 9: A connection to a remote device bthAddr was successfully established.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

A connection to a remote device bthAddr was successfully established.

Message #

A connection to a remote device %1 was successfully established.

Fields #

Name	Description
`bthAddr` UInt64

Event ID 10: An attempt to connect to a remote device bthAddr failed.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

An attempt to connect to a remote device bthAddr failed.

Message #

An attempt to connect to a remote device %1 failed.

Fields #

Name	Description
`bthAddr` UInt64

Event ID 11: The minimum encryption key size requirement of requiredKeySize octets was enforced on a connection to the remote device bthAddr.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

The minimum encryption key size requirement of requiredKeySize octets was enforced on a connection to the remote device bthAddr. The key size is actualKeySize octets.

Message #

The minimum encryption key size requirement of %2 octets was enforced on a connection to the remote device %1. The key size is %3 octets.

Fields #

Name	Description
`bthAddr` UInt64
`requiredKeySize` UInt8
`actualKeySize` UInt8

Event ID 12: A connection to the remote device bthAddr was rejected because it did not meet the minimum encryption key size requirement of requiredKeySize octets.

Provider: Microsoft-Windows-Bluetooth-Policy
Channel: Operational
Opcode: Info

Description

A connection to the remote device bthAddr was rejected because it did not meet the minimum encryption key size requirement of requiredKeySize octets. The key size was actualKeySize octets.

Message #

A connection to the remote device %1 was rejected because it did not meet the minimum encryption key size requirement of %2 octets. The key size was %3 octets.

Fields #

Name	Description
`bthAddr` UInt64
`requiredKeySize` UInt8
`actualKeySize` UInt8

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID 0602ecef-6381-4bc0-aeda-eb9bb919b276

Defined in bthport.sys, the binary that emits these events.

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02
Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

Microsoft-Windows-Bluetooth-Policy

Event ID 1: A Bluetooth policy has changed.

Description

Message #

Fields #

Event ID 2: Bluetooth radio enablement has been PolicyState due to policy PolicyPath\PolicyName.

Description

Message #

Fields #

Event ID 3: Bluetooth radio has PolicyState advertising due to policy PolicyPath\PolicyName.

Description

Message #

Fields #

Event ID 4: Bluetooth radio has PolicyState discoverability due to policy PolicyPath\PolicyName.

Description

Message #

Fields #

Event ID 5: Bluetooth radio has PolicyState radio name as RadioName due to policy PolicyPath\PolicyName.

Description

Message #

Fields #

Event ID 6: Process Service has attempted to pair to radio BtAddr.

Description

Message #

Fields #

Event ID 7: Bluetooth has Accepted service ServiceGuid on remote device BtAddr due to policy PolicyPath\PolicyName.

Description

Message #

Fields #

Event ID 8: Bluetooth has Accepted PSM Psm on remote device BtAddr due to policy PolicyPath\PolicyName.

Description

Message #

Fields #

Event ID 9: A connection to a remote device bthAddr was successfully established.

Description

Message #

Fields #

Event ID 10: An attempt to connect to a remote device bthAddr failed.

Description

Message #

Fields #

Event ID 11: The minimum encryption key size requirement of requiredKeySize octets was enforced on a connection to the remote device bthAddr.

Description

Message #

Fields #

Event ID 12: A connection to the remote device bthAddr was rejected because it did not meet the minimum encryption key size requirement of requiredKeySize octets.

Description

Message #

Fields #

Provenance

Downloads