| Previous | Next |
| ERROR_RESOURCE_NAME_NOT_FOUND | ERROR_NOT_ENOUGH_QUOTA |
ERROR_RESOURCE_LANG_NOT_FOUND
No matching language entry exists for the resource.
ERROR_RESOURCE_LANG_NOT_FOUND is Win32 error 1815 (0x717). A PE resource can have multiple language leaves under one type and name. The requested resource exists, but the lookup or enumeration operation cannot find the specified language identifier or an acceptable variant for that API path.
Causes of a language-level miss
- the language pack or MUI satellite containing the requested locale was not installed
- the resource script defines only a neutral or different locale than the caller requests
- an explicit language ID prevents the normal fallback chain from selecting another variant
- the base executable and language pack are from different versions or products
- package cleanup removed a satellite file while leaving locale configuration behind
Locale evidence to record
Capture the module and satellite paths, file versions and hashes, resource type and name, requested LANGID, user and system UI languages, preferred-language list, installed language packs, and the language IDs enumerated for the item. Represent LANGIDs numerically as well as by locale name because several names can map through fallback rules.
Troubleshooting steps
Enumerate the language entries for the known type and name in the selected image. Determine whether the caller intentionally requests an exact language or expects Windows resource fallback. Then verify that the MUI file chosen for the process belongs to the same version as the base binary.
Reproduce under a language known to exist and compare process preferred UI language settings. If the neutral resource is present but an exact lookup fails, correct the API usage or resource contract rather than duplicating every resource unnecessarily. If no relevant leaf exists, inspect the localization build and package manifest.
Recovery and localization guidance
Install or restore the matching language resource, rebuild the missing language leaf, or use the documented fallback API for optional localization. Do not copy a satellite DLL from another product build because resource IDs and binary expectations can differ.
Localization pipelines should verify that every required type/name pair has the intended language coverage and that base and MUI packages share version identity. Applications should provide a safe neutral-language fallback for noncritical text while surfacing missing mandatory resources.
Difference from a missing resource name
ERROR_RESOURCE_NAME_NOT_FOUND means no item with the requested name or ID exists under the type. Error 1815 confirms that the item exists and narrows the failure to its language leaves or selection rules.
Example
A French MUI package from the previous release remains beside a newly updated executable. The application finds the dialog type and ID but receives 1815 for the expected French language entry. Installing the matching current language package fixes the issue without changing the dialog ID.
References
Looking for a different code? Search another status or error code.