Microsoft-Windows-Containers-BindFlt

4 events across 1 channel

Event ID 1: BINDFLT filter registratiion failed with error message: NTStatus.

#
Provider
Microsoft-Windows-Containers-BindFlt
Channel
Operational

Description

BINDFLT filter registratiion failed with error message: NTStatus.

Message #

BINDFLT filter registratiion failed with error message: %1

Fields #

NameDescription
NTStatus HexInt32NTSTATUS reference

Event ID 2: BINDFLT filter registration succeeded

#
Provider
Microsoft-Windows-Containers-BindFlt
Channel
Operational
Level
Informational

Description

BINDFLT filter registration succeeded.

Message #

BINDFLT filter registration succeeded

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Containers-BindFlt",
    "guid": "{FC4E8F51-7A04-4BAB-8B91-6321416F72AB}",
    "event_source_name": "",
    "event_id": 2,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": -9223372036854775808,
    "time_created": "2026-05-29T16:32:53.9712592+00:00",
    "event_record_id": 16,
    "correlation": {},
    "execution": {
      "process_id": 4,
      "thread_id": 176
    },
    "channel": "Microsoft-Windows-Containers-BindFlt/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {},
  "message": "BINDFLT filter registration succeeded"
}

Event ID 3: BINDFLT filter failed to attach to volume 'VolumeName' with error message: NTStatus.

#
Provider
Microsoft-Windows-Containers-BindFlt
Channel
Operational

Description

BINDFLT filter failed to attach to volume 'VolumeName' with error message: NTStatus.

Message #

BINDFLT filter failed to attach to volume '%3' with error message: %1

Fields #

NameDescription
NTStatus HexInt32NTSTATUS reference
VolumeNameLength UInt16
VolumeName UnicodeString

Event ID 4: BINDFLT filter unload succeeded

#
Provider
Microsoft-Windows-Containers-BindFlt
Channel
Operational

Description

BINDFLT filter unload succeeded.

Message #

BINDFLT filter unload succeeded

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 fc4e8f51-7a04-4bab-8b91-6321416f72ab

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

Observed on:

  • WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.3451, captured 2026-06-02
  • Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.5074, captured 2026-06-02

Downloads