Jump to page content

Googler’s Haven technical tips



File History unable to start a backup cycle for configuration

File History in Windows 10 can spontaneously stop working, reporting event FileHistory-Core 200 into the File History backup log: “File History unable to start a backup cycle for configuration C:\Users\…\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config”. (This log, Microsoft-Windows-FileHistory-Engine/BackupLog, is found at Applications and Services Logs → Microsoft → Windows → FileHistory-Engine.)

The first step to resolving this is to restart the File History Service (fhsvc), as sometimes it stops working.

Another cause of the problem is a sharing violation on C:\Users\…\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Catalog1.edb which can be observed in Process Monitor during an attempted backup. For some reason this file gets opened by other processes; at work, it’s File Explorer, and at home it’s Mozilla Firefox. Attempts to close the file handle in Process Explorer are completely ignored; the offending process must be closed to release the file handle. After this, File History backups will resume normally.

Event log scheduled task completely ignored

After creating a scheduled task that fires when an event log entry is created, you may find that it is completely ignored. The task may sit forever in a “not yet run” state (“last run” result of 0x41303).

The “On an event” trigger type has three key properties: Log, Source and Event ID. Source is a combo box, suggesting erroneously that you can type in or paste in the source name. This does not work. To make the event work, select the source from the combo box’s dropdown menu and save. Typed in or pasted in source names are saved but are not recognised, not in Windows 10 anyway.