Microsoft-Windows-FileHistory-Service

10 events across 1 channel

Event ID 1: ConfigurationLoadStart

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
ConfigurationLoad
Opcode
Start

Event ID 2: ConfigurationLoadStop

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
ConfigurationLoad
Opcode
Stop

Fields #

NameDescription
Result Int32
ConfigFilePath UnicodeString

Event ID 3: CatalogLoadStart

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
CatalogLoad
Opcode
Start

Fields #

NameDescription
CatalogPath1 UnicodeString
CatalogPath2 UnicodeString

Event ID 4: CatalogLoadStop

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
CatalogLoad
Opcode
Stop

Fields #

NameDescription
Result Int32
CatalogPath1 UnicodeString
CatalogPath2 UnicodeString

Event ID 5: ConfigurationSaveStart

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
ConfigurationSave
Opcode
Start

Fields #

NameDescription
ConfigFilePath UnicodeString

Event ID 6: ConfigurationSaveStop

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
ConfigurationSave
Opcode
Stop

Fields #

NameDescription
ConfigFilePath UnicodeString

Event ID 7: BackupCycleStart

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
BackupCycle
Opcode
Start

Fields #

NameDescription
ConfigFilePath UnicodeString
BackupType UInt32

Event ID 8: BackupCycleStop

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
BackupCycle
Opcode
Stop

Fields #

NameDescription
ConfigFilePath UnicodeString

Event ID 9: BackupStopStart

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
BackupStop
Opcode
Start

Fields #

NameDescription
ConfigFilePath UnicodeString
StopSync Boolean

Event ID 10: BackupStop

#
Provider
Microsoft-Windows-FileHistory-Service
Channel
Debug
Task
BackupStop
Opcode
Stop

Fields #

NameDescription
ConfigFilePath UnicodeString
StopSync Boolean

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 b447b4e0-7780-11e0-ada3-18a90531a85a

Defined in fhsvc.dll, which carries the event manifest.

Observed on:

  • Win11-26200.6584 · schema read from the registered manifest · binary version 10.0.26100.1 · captured 2026-06-02

Downloads

Credits

  • Microsoft - authored the ETW manifests and PDBs the schema comes from
  • jdu2600 - the event-schema TSV format this catalog adopted
  • nasbench - the tool that dumps registered providers and manifests