Microsoft-Windows-CloudFiles-Filter

4 events across 1 channel

Event	Title	Channel	Sample
1	CLDFLT driver entry failed.	Operational	N
2	CLDFLT registration succeeded	Operational	Y
3	CLDFLT failed to attach to volume 'VolumeName' with error message: NTStatus.	Operational	N
4	CLDFLT unload succeeded	Operational	N

Event ID 1: CLDFLT driver entry failed.

Provider: Microsoft-Windows-CloudFiles-Filter
Channel: Operational

Description

CLDFLT driver entry failed. Error message: ErrorMsg, Error code: NTStatus.

Message #

CLDFLT driver entry failed. Error message: %1, Error code: %2

Fields #

Name	Description
`ErrorMsg` UnicodeString
`NTStatus` HexInt32	NTSTATUS reference

Event ID 2: CLDFLT registration succeeded

Provider: Microsoft-Windows-CloudFiles-Filter
Channel: Operational
Level: Informational

Description

CLDFLT registration succeeded.

Message #

CLDFLT registration succeeded

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-CloudFiles-Filter",
    "event_id": 2,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "time_created": "2026-05-27T19:31:57.0493335+00:00",
    "computer": "DESKTOP-FF3N5XK.ludus.domain",
    "channel": "Microsoft-Windows-CloudFiles-Filter"
  },
  "event_data": {}
}

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

Provider: Microsoft-Windows-CloudFiles-Filter
Channel: Operational

Description

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

Message #

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

Fields #

Name	Description
`NTStatus` HexInt32	NTSTATUS reference
`VolumeNameLength` UInt16
`VolumeName` UnicodeString

Event ID 4: CLDFLT unload succeeded

Provider: Microsoft-Windows-CloudFiles-Filter
Channel: Operational

Description

CLDFLT unload succeeded.

Message #

CLDFLT 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 4580bb06-baed-5b62-a4d5-92fa7156e7db

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

Observed on:

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

Downloads

Microsoft-Windows-CloudFiles-Filter registered manifest XML (in the Win11-26200.6584 manifest pack, 2.0 MB) manifest-xml

`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-CloudFiles-Filter

Event ID 1: CLDFLT driver entry failed.

Description

Message #

Fields #

Event ID 2: CLDFLT registration succeeded

Description

Message #

Example Event #

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

Description

Message #

Fields #

Event ID 4: CLDFLT unload succeeded

Description

Message #

Provenance

Downloads

Keyboard shortcuts

Search operators