Knowledge

ERROR_SHORT_NAMES_NOT_ENABLED_ON_VOLUME - 305 (0x131)

Short names are not enabled on this volume.

Updated: Feb 21, 2026

Technical Background

The error code ERROR_SHORT_NAMES_NOT_ENABLED_ON_VOLUME (305, 0x131) is a specific Windows API error that indicates an attempt to create or access short file names on a volume where short names are not enabled.

Short file names, also known as 8.3 file names, were a feature in older versions of the Windows operating system. They allow long filenames to be represented by shorter, eight-character names with three-character extensions. However, this feature is no longer commonly used and has been deprecated in modern systems.

Error Details

Meaning

This error occurs when an application or API attempts to create a file or directory using short file names on a volume that does not support such names. The system will return this error code if the operation cannot proceed due to the lack of short name support.

Context Dependency

The context in which this error is encountered can vary, but it typically arises when an application expects short file names and encounters a volume that only supports long file names or has short name generation disabled. This can happen during operations such as file creation, directory enumeration, or file renaming.

Common Causes

  • Invalid Parameter Values: The operation was attempted with parameters that expect short file names on a volume that does not support them.
  • Incorrect Object Type: An attempt to operate on an object type (file or directory) where short name generation is disabled.
  • Exceeding Limits: The system may have limitations on the number of short names allowed, and this error can occur if such limits are exceeded.

Real-World Context

This error can be encountered in various scenarios, including:

  • Migrating applications from older Windows versions to newer ones where short file names are not supported by default.
  • Using legacy software that relies on short file names on modern file systems.
  • Attempting to access or modify files on a volume formatted with a file system that does not support short names (e.g., NTFS without the appropriate settings).

Is This Error Critical?

The criticality of this error depends on the application's requirements. If an application strictly relies on short file names, encountering this error can prevent it from functioning correctly. However, for most modern applications, this is not a critical issue since long file names are the norm.

How to Diagnose

Reviewing Operation Context

  • Verify that the volume in question supports short file names by checking its attributes or using command-line tools like fsutil.
  • Ensure that any application attempting to use short file names is configured correctly and does not expect this feature on a volume where it is disabled.

Validating Parameters

  • Check the parameters passed to file operations for correctness, ensuring they do not contain invalid values or expect unsupported features.
  • Validate the object types being operated upon to ensure compatibility with the file system's capabilities.

How to Resolve

Correct Parameter Usage

  • Adjust application configurations to avoid using short file names on volumes that do not support them.
  • Use long file names consistently across all operations involving files and directories.

Adjust Operation Context

  • If possible, format or remount the volume with short name generation enabled. However, this may not be feasible for certain types of file systems or in production environments where data integrity is a concern.
  • For read-only operations, ensure that the application can handle long file names without issues.

Restore Data

  • In cases where data corruption or loss might have occurred due to unsupported short name operations, consider restoring from backups if available.

Developer Notes

Developers should be aware of the deprecation of short file names and avoid relying on this feature in new applications. For backward compatibility with legacy systems, ensure that applications can gracefully handle both long and short file names where appropriate.

Related Errors

FAQ

Q: Why does my application fail when trying to create a file with a short name on an NTFS volume?

A: The NTFS volume may not have short name generation enabled. Check the volume properties or use command-line tools like fsutil to verify and adjust settings as necessary.

Q: Can this error occur on FAT32 volumes?

A: Yes, if short names are disabled on a FAT32 volume, attempting to create files with short names will result in this error. Ensure that the volume supports short file names or use long file names instead.

Summary

The ERROR_SHORT_NAMES_NOT_ENABLED_ON_VOLUME (305) is a specific Windows API error indicating an attempt to use short file names on a volume where such support is not available. This can be encountered in various scenarios, and developers should ensure their applications are compatible with modern file systems that do not support short file names by default.