Skip to content

Event ID 206: MftRecordRead VolumeId: …, BaseFileId: …, FileId: …, CacheHit

Windows Event ID Lookup: What Windows event IDs mean: 4625, 4624, 4740, 6008, 41, 7045, 1102 and 3,000 more, with Windows' own message text, the fields and what to check.

Look up a Windows event ID from Event Viewer, a SIEM alert or a log export: what it means, the fields it records, and what to check. Many IDs are used by more than one source (event 41 is both a Kernel-Power crash and a boot error), so every definition is shown, the one people usually mean first. The message text is Windows' own, read from the event providers of Windows 10.0.26200.0, 2026-10-28; the notes are ours, based on Microsoft's security auditing reference.

Try: 4625, 4624, 4740, 6008, 41, 1074, 7045, 1102, 4104, 1149

MftRecordRead VolumeId: …, BaseFileId: …, FileId: …, CacheHit

Event 206
Ntfs
System log
Information
Message and fields (as Event Viewer shows them)
MftRecordRead VolumeId: …, BaseFileId: …, FileId: …, CacheHit: …

Dispatching a read request.

Event 206
StorPort
System log
Information
Message and fields (as Event Viewer shows them)
Dispatching a read request.

The Kerberos client used a hash algorithm for the PKINIT protocol that is being audited

Event 206
Security-Kerberos
System log
Warning
Message and fields (as Event Viewer shows them)
The Kerberos client used a hash algorithm for the PKINIT protocol that is being audited: ….

The URL "…" in BITS job "…" does not support the HTTP HEAD verb, which is required for BITS bandwidth throttling.

Event 206
Bits-Client
Bits-Client/Operational log
Warning
Message and fields (as Event Viewer shows them)
The URL "…" in BITS job "…" does not support the HTTP HEAD verb, which is required for BITS bandwidth throttling. The URL will be downloaded without throttling.