| Previous | Next |
| E_SYNCENGINE_FOLDER_INACCESSIBLE | E_SYNCENGINE_UNSUPPORTED_MARKET |
E_SYNCENGINE_UNSUPPORTED_FOLDER_NAME
The scope of E_SYNCENGINE_UNSUPPORTED_FOLDER_NAME is Windows cloud-file and sync-engine infrastructure: a directory component violates the local or remote sync naming contract. Preserve 0x8802D002 beside the returning call before cleanup or retry creates a more generic secondary failure.
Read the boundary first
When it is returned, a Windows sync engine coordinates local NTFS objects, provider metadata, remote identifiers, quota and naming rules, placeholder hydration, network authentication, and asynchronous upload or download state. During a this result investigation, the same Explorer action can cross several of those boundaries, so diagnosis must retain the first failing stage rather than treating every code as a generic connectivity problem.
During a this result investigation, folder renaming affects every descendant path and remote identity. Reserved names, characters, trailing spaces/dots, normalization or service rules should be detected before a large subtree is queued.
The first owner to inspect is the local sync root, placeholder state, file-system operation, provider request, network exchange, account policy, or remote storage operation that produced the HRESULT.
Keep neighboring conditions separate
When it is returned, UNSUPPORTED_FILE_NAME affects one file; a folder-name correction can change an entire subtree.
Do not sanitize the folder name without collision and descendant analysis.
Incident record for this HRESULT
| Capture | Diagnostic value |
|---|---|
| Exact folder component and Unicode points for it. | This provides a stable comparison across retries or another machine and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Descendant count for it. | This identifies the exact object or resource generation involved and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Normalized/case-collision state for it. | This places the failure on the lifecycle or transaction timeline and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Remote naming rule for it. | This separates caller input from environment and service state and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
Reproduce without destroying evidence
The investigation should change one variable at a time and keep the original failing sample.
- First: Validate the single component.
- Next: Preview descendant path effects.
- Then: Rename atomically through the engine.
- Finally: Reconcile remote IDs after the rename.
Three useful controls
- Second supported path for the same stable item: for it, a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: for it, keep account, remote item version, and client build fixed.
- Reduced failing operation: If this result follows the reduced step, the rejecting transition is localized. Hold constant: for it, retain exact folder component and unicode points and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: validate the single component. Hold constant: for it, keep the original this result sample available for the final regression test.
Definition of done
Closure for it requires the renamed subtree preserves identity and all descendants remain within naming and path limits; then repeat the next lifecycle operation to detect stale state.
Technical references
The references below define the API family or storage/protocol behavior used to interpret this result.
- Microsoft: Build a Cloud Files sync engine
- Microsoft: Naming files, paths, and namespaces
- Microsoft: Cloud Filter API reference
- Microsoft: Determine cloud placeholder state
Looking for a different code? Search another status or error code.