| Previous | Next |
| DXGI_STATUS_PRESENT_REQUIRED | MSG_CI_MASTER_MERGE_COMPLETED |
MSG_CI_MASTER_MERGE_STARTED
MSG_CI_MASTER_MERGE_STARTED is an informational catalog event. A master merge combines accumulated index components into the master index, so increased disk and CPU activity around this event can be expected and should be interpreted in the context of catalog maintenance.
Track merge duration and the catalog named in the event
- Record the catalog, start time, free disk space, and indexing backlog when the event appears.
- Pair the start event with completion, abort, restart, or cannot-start events instead of treating it as a standalone failure.
- When investigating query latency, compare the time window with merge activity before attributing every slowdown to crawling or filters.
Microsoft’s Indexing Service documentation describes a master merge as combining shadow indexes with a persistent, disk-resident master index optimized for querying. Windows Search has a different product history, but these catalog event constants retain the merge terminology. The event is useful as a lifecycle marker: the abnormal condition is a merge that repeatedly aborts, restarts, or never progresses, not the mere fact that consolidation started.
Merging indexes · Forcing a master merge · Indexing process
Looking for a different code? Search another status or error code.