How to Fix ERROR_INCOMPATIBLE_WITH_GLOBAL_SHORT_NAME_REGISTRY_SETTING

The error code ERROR_INCOMPATIBLE_WITH_GLOBAL_SHORT_NAME_REGISTRY_SETTING (304 or 0x130) indicates that short name settings cannot be changed on a specific volume due to a global registry setting. This error often occurs when trying to enable or disable 8.3 short names on a volume, which is a feature used for backward compatibility with older software that relies on the 8.3 filename convention.

If you encounter this error, it means that the global registry setting for short names is preventing any changes to the short name settings on the volume in question. To resolve this, you might need to adjust the global registry setting or use a different volume where short names are enabled.

How do I fix ERROR_INCOMPATIBLE_WITH_GLOBAL_SHORT_NAME_REGISTRY_SETTING?

1. Change the 8.3 name creation value in the Registry

NOTE

Modifying the registry can have significant effects on your system. Be sure to back up the registry before making any changes.

1. Press Win + R, type regedit, and press Enter.
2. Go to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
3. Find the NtfsDisable8dot3NameCreation entry.
4. Double-click it and change its value to 0 to enable 8.3 name creation globally, or 1 to disable it.
5. Restart your computer to apply the changes.

2. Check the volume-specific setting

1. Click the Start button, type cmd and select Run as administrator to start Command Prompt with full privileges.
2. Use the following command and press Enter to check the current setting for the specific volume: fsutil 8dot3name query <volume>
3. If needed, use fsutil 8dot3name set <volume> 0 to enable or fsutil 8dot3name set <volume> 1 to disable 8.3 name creation on that volume.

That’s it! After you apply one of the solutions above, you should be able to get rid of the ERROR_INCOMPATIBLE_WITH_GLOBAL_SHORT_NAME_REGISTRY_SETTING issue on your PC.

As you can see, although it has a long name, the ERROR_INCOMPATIBLE_WITH_GLOBAL_SHORT_NAME_REGISTRY_SETTING is not really that damaging or hard to fix.

You may also check the BSoD log if you want to learn more about this problem. For more information, our article on the causes of BSoD will provide the extra resources.

We hope that by applying our methods, your PC is in the clear and it works fine. If you have any additional related issues, use the comments section below to let us know.