Microsoft-User Experience Virtualization-SQM Uploader

17 events across 2 channels

Event	Title	Channel	Sample
1	The UE-V SQM Uploader started.	Operational	N
2	The UE-V SQM Uploader ended.	Operational	N
3	An error occurred while initializing COM.	Debug	N
4	An error occurred while uploading the SQM data files.	Debug	N
5	The user has not opted into the UE-V CEIP program.	Operational	N
6	SQM data file filename was successfully uploaded (HTTP response http).	Debug	N
7	There was an error (hr) uploading SQM data file filename (HTTP response http).	Debug	N
8	There was an error uploading the SQM data files.	Operational	N
9	The SQM data files were successfully uploaded.	Operational	N
10	An error of type std::exception occurred while uploading the SQM data files.	Debug	N
11	An unknown exception was caught during the upload of SQM data files.	Debug	N
12	uint32 SQM data file(s) will be uploaded.	Operational	N
13	SQM data files matching the following pattern will be uploaded: "WString1".	Debug	N
14	The SQM library could not be initialized due to the following error: error.	Debug	N
108	No SQM files matching the specified file pattern were found.	Debug	N
268	No network connectivity was detected and so no attempt will be made to upload …	Operational	N
2566	The SQMAPI was not initialized.	Debug	N

Event ID 1: The UE-V SQM Uploader started.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Operational
Opcode: Start

Description

The UE-V SQM Uploader started.

Message #

The UE-V SQM Uploader started.

Event ID 2: The UE-V SQM Uploader ended.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Operational

Description

The UE-V SQM Uploader ended.

Message #

The UE-V SQM Uploader ended.

Event ID 3: An error occurred while initializing COM.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

An error occurred while initializing COM.

Message #

An error occurred while initializing COM.
Error: %1

Fields #

Name	Description
`hresult` UInt32

Event ID 4: An error occurred while uploading the SQM data files.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

An error occurred while uploading the SQM data files.

Message #

An error occurred while uploading the SQM data files.
Error: %1

Fields #

Name	Description
`WString1` UnicodeString

Event ID 5: The user has not opted into the UE-V CEIP program.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Operational

Description

The user has not opted into the UE-V CEIP program. The SQM Uploader will now exit without uploading any SQM data.

Message #

The user has not opted into the UE-V CEIP program. The SQM Uploader will now exit without uploading any SQM data.

Event ID 6: SQM data file filename was successfully uploaded (HTTP response http).

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

SQM data file filename was successfully uploaded (HTTP response http).

Message #

SQM data file %2 was successfully uploaded (HTTP response %3).

Fields #

Name	Description
`hr` UInt32
`filename` UnicodeString
`http` Int32

Event ID 7: There was an error (hr) uploading SQM data file filename (HTTP response http).

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

There was an error (hr) uploading SQM data file filename (HTTP response http).

Message #

There was an error (%1) uploading SQM data file %2 (HTTP response %3)

Fields #

Name	Description
`hr` UInt32
`filename` UnicodeString
`http` Int32

Event ID 8: There was an error uploading the SQM data files.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Operational

Description

There was an error uploading the SQM data files.

Message #

There was an error uploading the SQM data files.
SQMAPI error code: %1

Fields #

Name	Description
`error` UInt32

Event ID 9: The SQM data files were successfully uploaded.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Operational

Description

The SQM data files were successfully uploaded.

Message #

The SQM data files were successfully uploaded.

Event ID 10: An error of type std::exception occurred while uploading the SQM data files.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

An error of type std::exception occurred while uploading the SQM data files.

Message #

An error of type std::exception occurred while uploading the SQM data files.
Error: %1

Fields #

Name	Description
`String1` AnsiString

Event ID 11: An unknown exception was caught during the upload of SQM data files.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

An unknown exception was caught during the upload of SQM data files.

Message #

An unknown exception was caught during the upload of SQM data files.

Event ID 12: uint32 SQM data file(s) will be uploaded.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Operational

Description

uint32 SQM data file(s) will be uploaded.

Message #

%1 SQM data file(s) will be uploaded.

Fields #

Name	Description
`uint32` UInt32

Event ID 13: SQM data files matching the following pattern will be uploaded: "WString1".

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

SQM data files matching the following pattern will be uploaded: "WString1".

Message #

SQM data files matching the following pattern will be uploaded: "%1"

Fields #

Name	Description
`WString1` UnicodeString

Event ID 14: The SQM library could not be initialized due to the following error: error.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

The SQM library could not be initialized due to the following error: error.

Message #

The SQM library could not be initialized due to the following error: %1

Fields #

Name	Description
`error` UInt32

Event ID 108: No SQM files matching the specified file pattern were found.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

No SQM files matching the specified file pattern were found.

Message #

No SQM files matching the specified file pattern were found.

Event ID 268: No network connectivity was detected and so no attempt will be made to upload the SQM data files.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Operational

Description

No network connectivity was detected and so no attempt will be made to upload the SQM data files.

Message #

No network connectivity was detected and so no attempt will be made to upload the SQM data files.

Event ID 2566: The SQMAPI was not initialized.

Provider: Microsoft-User Experience Virtualization-SQM Uploader
Channel: Debug

Description

The SQMAPI was not initialized.

Message #

The SQMAPI was not initialized.

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 57003e21-269b-4bdc-8434-b3bf8d57d2d5

Defined in Microsoft.Uev.EventLogMessages.dll, which carries the event manifest.

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)