Microsoft-Windows-Kernel-IO

14 events across 2 channels

Event ID 1: Windows has started processing the volume mount request.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Also via
realtime ETW trace
Level
Informational
Task
VolumeMount
Opcode
Start

Description

Windows has started processing the volume mount request.

Message #

Windows has started processing the volume mount request.

           Volume GUID: %1
           Volume Name: %3

Fields #

NameDescription
VolumeGuid GUID
VolumeNameLength UInt16
VolumeName UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Kernel-IO",
    "guid": "{ABF1F586-2E50-4BA8-928D-49044E6F0DB7}",
    "event_source_name": "",
    "event_id": 1,
    "version": 0,
    "level": 4,
    "task": 1,
    "opcode": 1,
    "keywords": -9223372036854775807,
    "time_created": "2026-06-13T14:12:00.0150855+00:00",
    "event_record_id": 9917,
    "correlation": {},
    "execution": {
      "process_id": 6740,
      "thread_id": 4324
    },
    "channel": "Microsoft-Windows-Kernel-IO/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-19"
    }
  },
  "event_data": {
    "VolumeGuid": "{4b41a8d4-e67f-11f0-964b-806e6f6e6963}",
    "VolumeNameLength": "2",
    "VolumeName": "D:"
  },
  "message": "Windows has started processing the volume mount request.\r\n\r\n           Volume GUID: {4b41a8d4-e67f-11f0-964b-806e6f6e6963}\r\n           Volume Name: D:\r\n"
}

Event ID 2: The volume has been successfully mounted.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Level
Informational
Task
VolumeMount
Opcode
Stop

Description

The volume has been successfully mounted.

Message #

The volume has been successfully mounted.

           Volume GUID: %1
           Volume Name: %3

Fields #

NameDescription
VolumeGuid GUID
VolumeNameLength UInt16
VolumeName UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Kernel-IO",
    "guid": "{ABF1F586-2E50-4BA8-928D-49044E6F0DB7}",
    "event_source_name": "",
    "event_id": 2,
    "version": 0,
    "level": 4,
    "task": 1,
    "opcode": 2,
    "keywords": -9223372036854775807,
    "time_created": "2026-06-13T10:41:37.8437748+00:00",
    "event_record_id": 9412,
    "correlation": {},
    "execution": {
      "process_id": 5200,
      "thread_id": 8140
    },
    "channel": "Microsoft-Windows-Kernel-IO/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "event_data": {
    "VolumeGuid": "{00000000-0000-0000-0000-000000000000}",
    "VolumeNameLength": "0",
    "VolumeName": ""
  },
  "message": "The volume has been successfully mounted.\r\n\r\n           Volume GUID: {00000000-0000-0000-0000-000000000000}\r\n           Volume Name: \r\n"
}

Event ID 3: Windows failed to mount the volume.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Also via
realtime ETW trace
Level
Warning
Task
VolumeMount
Opcode
Stop

Description

Windows failed to mount the volume.

Message #

Windows failed to mount the volume.

           Status: %4
           Volume GUID: %1
           Volume Name: %3

Fields #

NameDescription
VolumeGuid GUID
VolumeNameLength UInt16
VolumeName UnicodeString
Error HexInt32Status.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Kernel-IO",
    "guid": "{ABF1F586-2E50-4BA8-928D-49044E6F0DB7}",
    "event_source_name": "",
    "event_id": 3,
    "version": 0,
    "level": 3,
    "task": 1,
    "opcode": 2,
    "keywords": -9223372036854775807,
    "time_created": "2026-06-13T14:12:00.0158348+00:00",
    "event_record_id": 9918,
    "correlation": {},
    "execution": {
      "process_id": 6740,
      "thread_id": 4324
    },
    "channel": "Microsoft-Windows-Kernel-IO/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-19"
    }
  },
  "event_data": {
    "VolumeGuid": "{4b41a8d4-e67f-11f0-964b-806e6f6e6963}",
    "VolumeNameLength": "2",
    "VolumeName": "D:",
    "Error": "0xc0000013"
  },
  "message": "Windows failed to mount the volume.\r\n\r\n           Status: {No Disk}\r\nThere is no disk in the drive.\r\nPlease insert a disk into drive %hs.\r\n           Volume GUID: {4b41a8d4-e67f-11f0-964b-806e6f6e6963}\r\n           Volume Name: D:\r\n"
}

Event ID 1205: Windows is configured to block legacy file system filters.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
System
Opcode
Info

Description

Windows is configured to block legacy file system filters.

Message #

Windows is configured to block legacy file system filters.

           Filter name: %2

Fields #

NameDescription
FilterNameLength UInt16
FilterName UnicodeString

Event ID 1206: Legacy file system filters cannot attach to byte addressable volumes.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
System
Opcode
Info

Description

Legacy file system filters cannot attach to byte addressable volumes.

Message #

Legacy file system filters cannot attach to byte addressable volumes.

           Filter name: %2
           Volume name: %4

Fields #

NameDescription
FilterNameLength UInt16
FilterName UnicodeString
VolumeNameLength UInt16
VolumeName UnicodeString

Event ID 1207: Dumps are disabled on the machine since there was an error enabling dump encryption: DumpEncryptionFailureReason.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
System
Opcode
Info

Description

Dumps are disabled on the machine since there was an error enabling dump encryption: DumpEncryptionFailureReason.

Message #

Dumps are disabled on the machine since there was an error enabling dump encryption: %1.                  
See http://go.microsoft.com/fwlink/?LinkId=824149 for more information on dump encryption

Fields #

NameDescription
DumpEncryptionFailureReason UInt32

Event ID 1212: Failed to automatically attach a VHD during system startup.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
System

Description

Failed to automatically attach a VHD during system startup.

Message #

Failed to automatically attach a VHD during system startup.

          VHD name: %2
          Status: %3

Fields #

NameDescription
NameLength UInt16
Name UnicodeString
Status HexInt32NTSTATUS reference

Event ID 1213: This volume is configured to block legacy file system filters.

#
Provider
Microsoft-Windows-Kernel-IO
Channel
System

Description

This volume is configured to block legacy file system filters.

Message #

This volume is configured to block legacy file system filters.

           Filter name: %2
           Volume name: %4

Fields #

NameDescription
FilterNameLength UInt16
FilterName UnicodeString
VolumeNameLength UInt16
VolumeName UnicodeString

Event ID 1300: LoadBootHotPatchesStart

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Task
LoadBootHotPatches
Opcode
Start

Event ID 1301: LoadBootHotPatchesStop

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Task
LoadBootHotPatches
Opcode
Stop

Event ID 1302: WheaInitializeStart

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Task
WheaInitialize
Opcode
Start

Fields #

NameDescription
Phase UInt32

Event ID 1303: WheaInitializeStop

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Task
WheaInitialize
Opcode
Stop

Event ID 1304: CrashDumpInitializeStart

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Task
CrashDumpInitialize
Opcode
Start

Event ID 1305: CrashDumpInitializeStop

#
Provider
Microsoft-Windows-Kernel-IO
Channel
Operational
Task
CrashDumpInitialize
Opcode
Stop

Fields #

NameDescription
Status UInt32NTSTATUS reference

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 {ABF1F586-2E50-4BA8-928D-49044E6F0DB7}

Defined in Microsoft-Windows-System-Events.dll, which carries the event manifest.

Observed on:

  • WS2022-20348.4893, sample captured from a live trace, binary version 10.0.20348.3932, captured 2026-06-02
  • WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.3932, captured 2026-06-02
  • Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.5074, captured 2026-06-02

Downloads