What does HRESULT 0x80270265 (E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This content can only be moved to a folder. To move the content to this drive, please choose or create a folder.

Previous	Next
E_SKYDRIVE_UPDATE_AVAILABILITY_FAIL	TPM_E_ERROR_MASK

E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED

Within Windows cloud-file and sync-engine infrastructure, E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED reports that the sync root was pointed at a volume root instead of a child folder. Diagnosis of E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED should follow the original owner and generation rather than treating the visible symptom as the cause.

Mechanism behind the code

During a E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED investigation, 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. For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, 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.

For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, a provider root needs a bounded directory it can own without taking responsibility for the entire volume. When E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED is returned, the volume root also contains system and unrelated user objects outside the sync engine’s namespace.

For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, 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.

High-value telemetry

Capture	Diagnostic value
Requested path and canonical root for E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED.	For `E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED`, this provides a stable comparison across retries or another machine and helps test the Windows cloud-file and sync-engine infrastructure boundary.
Volume GUID path for E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED.	For `E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED`, this identifies the exact object or resource generation involved and helps test the Windows cloud-file and sync-engine infrastructure boundary.
Existing child folders for E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED.	For `E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED`, this places the failure on the lifecycle or transaction timeline and helps test the Windows cloud-file and sync-engine infrastructure boundary.
Registration request for E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED.	For `E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED`, this separates caller input from environment and service state and helps test the Windows cloud-file and sync-engine infrastructure boundary.

Decision table

Second supported path for the same stable item: For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, keep account, remote item version, and client build fixed.
Reduced failing operation: If E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED follows the reduced step, the rejecting transition is localized. Hold constant: For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, retain requested path and canonical root and remove only unrelated work.
Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: create a dedicated child directory. Hold constant: For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, keep the original E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED sample available for the final regression test.

Safe reduction procedure

When E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED is returned, use a disposable control object, repository copy, file, or device association where the subsystem permits it.

First: Create a dedicated child directory.
Next: Apply least-privilege ACLs to that directory.
Then: Register the child path, not the drive root.
Finally: Test provider boundary handling.

Do not erase the distinction

During a E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED investigation, FILE_SYSTEM_NOT_SUPPORTED concerns the volume format; this code rejects the path level even on supported NTFS.

For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED, do not hide the root behind a trailing component, junction, or alternate path syntax.

Successful outcome

Verify E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED with the original scenario, one boundary case, and one deliberate failure; success means a dedicated folder registers and only its subtree is observed and synchronized.

Technical references

The references below define the API family or storage/protocol behavior used to interpret E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED.

For E_SKYDRIVE_ROOT_TARGET_VOLUME_ROOT_NOT_SUPPORTED: Microsoft: Build a Cloud Files sync engine
Microsoft: Determine cloud placeholder state
Microsoft: Restrictions and limitations in OneDrive and SharePoint
Microsoft: StorageProviderSyncRootManager

Looking for a different code? Search another status or error code.