What does HRESULT 0x80045399 (FSRM_E_EXPIRATION_VOLUME_NOT_NTFS) mean?

 
Previous Next
FSRM_E_EXPIRATION_PATH_TOO_LONG FSRM_E_FILE_MANAGEMENT_JOB_DEPRECATED

FSRM_E_EXPIRATION_VOLUME_NOT_NTFS

FSRM_E_EXPIRATION_VOLUME_NOT_NTFS is the failure HRESULT 0x80045399 (signed decimal -2147200103, unsigned decimal 2147767193). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0x5399.

The expiration directory must reside on NTFS

This HRESULT means the configured file expiration directory is located on a volume whose file system is not NTFS. Microsoft documents NTFS as a requirement for the expiration destination and for FSRM file-management namespace roots. A directory that exists and is writable on ReFS, FAT, or another file system still fails this contract.

AllStat records the official condition as: “The expiration directory must be on a volume formatted with the NTFS file system.” The wording should be interpreted at this FSRM stage, not as a generic file-system or COM failure.

Where the failure boundary lies

The check applies to the destination volume that will hold moved files and their preserved directory structure and ACLs. It is not a generic statement that the whole server lacks NTFS, nor does it identify the source volume. File-system labels and drive letters are insufficient evidence when mount points or redirected paths are involved.

Likely causes to separate

  • The expiration root was created on ReFS or another non-NTFS data volume.
  • A mount point or volume replacement changed the file system under an unchanged directory path.
  • Deployment selected a removable or temporary volume without verifying its format.
  • A migration copied the job definition to a server where the same drive letter maps to a different file system.

Evidence worth preserving

  • Resolve the exact volume backing the expiration directory and record its volume GUID, file-system type, and mount path.
  • Capture the configured path from the job rather than relying on an administrator’s intended destination.
  • Record whether the path crosses a reparse point or mount point that changes the underlying volume.
  • Preserve destination ACL and retention requirements before selecting a replacement volume.

Diagnostic sequence

  • Query the file-system type of the actual destination volume on the FSRM server.
  • Trace mount points and reparse points so the reported drive or directory is not mistaken for the backing volume.
  • Confirm that the replacement NTFS location is local, writable by the service identity, and outside the job scope.
  • Estimate capacity for expired files and generated directory structure before enabling the task.
  • Run a controlled move and verify that ACLs and original hierarchy are preserved as expected.

Retry and recovery

Move the expiration root to a supported local NTFS volume and update the job. Converting or reformatting a production volume is a separate storage project and should not be performed solely to clear this HRESULT without backup and downtime planning. A retry is valid only after the path resolves to NTFS.

What this HRESULT does not establish

The result does not imply that ReFS is generally unhealthy or unsuitable for all workloads; it states that this FSRM operation requires NTFS. It also does not confirm that the new NTFS destination has adequate access or path length.

Difference from nearby FSRM results

FSRM_E_VOLUME_UNSUPPORTED is a broader unsupported-volume result. This code is specifically tied to the expiration destination’s NTFS requirement.

Practical scenario

A server migration maps the old expiration drive letter to a new ReFS volume. The path exists and an administrator can write to it, but saving the job returns this HRESULT. A dedicated NTFS volume is mounted at a short local path, permissions are applied, and the expiration test succeeds.

Guidance for software and telemetry

Provisioning should resolve and validate the volume file system after all mount points are created. Store volume identity in deployment evidence so later storage remapping cannot silently invalidate the job.

Official Microsoft references

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