0XC000019E: Short Name Registry Locked on NTFS Volume

You're trying to run fsutil behavior set disable8dot3 1 or tweak the short name (8.3 filename) generation on a volume, and Windows slaps you with 0XC000019E. That's annoying. Let's fix it.

The Direct Fix

The error means a global registry policy has locked short name settings at the volume level. Here's what to do:

1. Open regedit as Administrator.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
3. Find NtfsDisable8dot3NameCreation. If it doesn't exist, create it as a DWORD (32-bit).
4. Set its value to 2 — this means "per volume setting" (controlled by fsutil or disk properties).
5. Reboot.

Now you can run fsutil behavior set disable8dot3 1 for a specific volume without getting the 0XC000019E error.

Why This Works

What's actually happening here is that NtfsDisable8dot3NameCreation has a hierarchy of control. When it's set to 0 (enable 8.3 names globally) or 1 (disable globally), Windows treats that as an immutable policy for ALL volumes. Any attempt to override it per-volume triggers the STATUS_INCOMPATIBLE_WITH_GLOBAL_SHORT_NAME_REGISTRY error because the system sees a conflict between a global mandate and a local request.

Setting it to 2 tells Windows: "Hey, don't enforce a global policy — let each volume decide." Then fsutil and the volume-level settings work as intended. This is documented in Microsoft's NTFS behavior reference, but it's easy to miss when you're in the middle of fixing a short-name issue.

Less Common Variations

You might see this error in other scenarios:

• Group Policy override: If you're on a domain-joined machine, a Group Policy object might enforce a specific NtfsDisable8dot3NameCreation value. Check gpedit.msc under Computer Configuration\Administrative Templates\System\Filesystem\NTFS for the "Disable 8.3 name creation" policy. You can't override that via registry — you'd need admin access to change the GPO.
• Third-party tools: Some disk utilities or antivirus software hook into the file system and set this registry key themselves. If you change it and it reverts, check your installed software for anything that manages NTFS settings.
• Corrupted registry hive: Rare, but if the key exists and you can't modify it (access denied), the registry hive might be corrupted. Run sfc /scannow or DISM /Online /Cleanup-Image /RestoreHealth from an admin command prompt.

Prevention

Short names were a compatibility crutch for old DOS and Windows 3.1 apps. On modern Windows 10/11 systems with NTFS, you almost never need them. If you're building a new system or imaging a deployment:

• Set NtfsDisable8dot3NameCreation to 2 in your base image. This keeps flexibility without locking you into a global policy.
• Don't touch fsutil unless you have a specific app that requires short names. Most apps that needed them (like 16-bit installers) are dead or have modern replacements.
• If you're a sysadmin deploying via Group Policy, use the 2 value in your GPO so individual servers or workstations can override if needed.

Honestly, the only time I've seen someone need this fix is when they're migrating old application data and some ancient installer bombs without short names. Otherwise, leave it alone.