Problem
Enabling the Windows virtual file provider can create a directory placeholder that Windows reports as having corrupt and unreadable cloud file metadata. The provider then fails while traversing the sync root, so the integration cannot start reliably.
Expected behavior
Cloud Files directory placeholders use valid filesystem metadata, remain readable through Win32 and Java filesystem APIs, and survive provider startup and restart. Existing provider failures must be reported without claiming that integration is active.
Acceptance criteria
- A Windows integration test registers a temporary sync root, creates a directory placeholder, starts the provider, and reads the directory.
- Placeholder filesystem metadata follows the CFAPI contract for attributes, size, and timestamps.
- Affected startup paths fail closed and do not leave a claimed-active provider.
- Windows desktop tests and MSI packaging pass.
Problem
Enabling the Windows virtual file provider can create a directory placeholder that Windows reports as having corrupt and unreadable cloud file metadata. The provider then fails while traversing the sync root, so the integration cannot start reliably.
Expected behavior
Cloud Files directory placeholders use valid filesystem metadata, remain readable through Win32 and Java filesystem APIs, and survive provider startup and restart. Existing provider failures must be reported without claiming that integration is active.
Acceptance criteria