| Previous | Next |
| ERROR_PROCESS_MODE_NOT_BACKGROUND | ERROR_NOT_A_CLOUD_SYNC_ROOT |
ERROR_CLOUD_FILE_PROVIDER_TERMINATED
The provider disappeared while the platform still had pending work
ERROR_CLOUD_FILE_PROVIDER_TERMINATED is more specific than provider-not-running: it indicates that a connected provider exited unexpectedly while requests or the communication channel were active. Pending hydration, validation, enumeration, or notification work can no longer be completed by that process.
Collect the provider exit code, crash dump, service-control events, and the outstanding CFAPI callback set at termination. On restart, reconnect the root and rebuild request-independent state from durable provider metadata; do not attempt to reuse old connection or transfer keys. Also verify that shutdown ordering is correct, because terminating worker threads before disconnecting and draining callbacks can mimic a crash during normal update or sign-out.
What to inspect
- Capture crash or exit diagnostics together with outstanding callback types.
- Reconnect with a new connection key and discard all old transfer keys.
- Drain or explicitly fail provider work before orderly process termination.
References
- Microsoft: connection keys for provider channels
- Microsoft: disconnect behavior with callbacks in flight
- Microsoft sample: provider shutdown sequence
Looking for a different code? Search another status or error code.