What does Windows error code 1464 (ERROR_SYMLINK_NOT_SUPPORTED) mean?

 
Previous Next
ERROR_SYMLINK_CLASS_DISABLED ERROR_XML_PARSE_ERROR

ERROR_SYMLINK_NOT_SUPPORTED

The operation cannot handle this symbolic-link case.

ERROR_SYMLINK_NOT_SUPPORTED is Win32 error 1464 (0x5B8). The path contains a symbolic link, but the application, file-system operation, protocol, or destination does not support the requested behavior. This is different from a missing target and from policy that disables following an otherwise supported link class.

Situations to investigate

  • a copy, backup, archive, or synchronization tool cannot preserve link objects
  • the destination file system lacks the required reparse-point behavior
  • an API follows links while the caller expected to operate on the link itself
  • a remote protocol or server does not implement the requested link semantics
  • the application intentionally rejects links to prevent path-escape attacks

What to record

Capture the source and destination file-system types, local or remote status, operation and flags, link path, target path, reparse tag, caller identity, and whether the desired behavior is follow, copy-as-link, replace, or inspect. For recursive operations, record the exact path component where traversal stopped.

Diagnostic sequence

Inspect the path using APIs that can open the reparse point itself and identify the link type. Read the documentation for the requested operation’s symbolic-link behavior. Test the same operation on a simple local link and on the actual destination to separate application limitations from file-system or protocol limitations.

Decide explicitly whether links should be followed. Following them can escape the intended tree, create loops, duplicate large data sets, or cross trust boundaries. Preserving them requires the destination to support suitable metadata and the caller to have required privileges.

Recovery options

Choose a supported mode: dereference and copy the target, preserve the link with a link-aware tool and compatible destination, or reject the item with a clear report. Never silently replace a link with target contents when that changes backup, deployment, or security semantics.

Related results

ERROR_SYMLINK_CLASS_DISABLED indicates policy blocking traversal based on local/remote class. ERROR_CANT_RESOLVE_FILENAME or file-not-found values can arise when the target cannot be resolved. Error 1464 says the requested operation does not support the encountered link behavior.

Example

A packaging tool copies a directory to a destination that cannot represent Windows symbolic links. It requests preservation of the link object and receives 1464. The product must either require a compatible destination or offer an explicit, audited dereference mode.

References

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