What does Windows error code 1253 (ERROR_BAD_USER_PROFILE) mean?

 
Previous Next
ERROR_OVERRIDE_NOCHANGES ERROR_NOT_SUPPORTED_ON_SBS

ERROR_BAD_USER_PROFILE

The specified account has no valid loadable user profile.

ERROR_BAD_USER_PROFILE is Win32 error 1253 (0x4E5). Profile-dependent work cannot proceed because Windows considers the user profile missing, damaged, inconsistent, or otherwise unsuitable for the requested operation. The account itself can still exist and authenticate successfully.

Profile components to distinguish

  • the profile directory and its access control list
  • the user registry hive, commonly represented by NTUSER.DAT
  • the profile mapping and state stored by the Profile Service
  • roaming, mandatory, temporary, or containerized profile configuration
  • disk, network, and synchronization dependencies needed during load

Evidence to collect

Record the user SID rather than only the account name, profile type, resolved profile path, session type, Profile Service event IDs, and whether Windows substituted a temporary profile. Include disk free space, hive load errors, path reachability, and the last known successful logon. Do not copy the user’s hive or personal files into general application logs.

Diagnostic sequence

Confirm that the account SID resolves and that the profile path belongs to that SID. Inspect User Profile Service events around the failing logon or LoadUserProfile call. Verify that the directory and hive exist, are not held open by an abandoned process, and have expected ownership and permissions.

For roaming or profile-container deployments, test the storage path and synchronization layer from the affected machine and account context. Compare with another user on the same machine and the same user on another machine to separate local profile corruption from centralized profile storage problems.

Recovery approach

Preserve user data before rebuilding anything. A temporary profile can allow sign-in but should not be treated as successful recovery because changes may be lost at sign-out. Repair permissions or storage first; if the profile state is irreparable, create a new profile mapping and migrate only verified user data instead of copying the damaged hive wholesale.

Developer recommendations

  • do not assume profile paths can be constructed from user names
  • handle services and noninteractive accounts that intentionally have no normal profile
  • close registry and file handles before unloading a profile
  • surface temporary-profile use as a visible degraded state

Related errors

ERROR_UNKNOWN_REVISION or registry-specific errors can describe damage inside profile data. ERROR_PATH_NOT_FOUND identifies a missing path without the broader profile validation. Error 1253 means the user profile as a whole is not valid for loading.

Example

A scheduled task calls LoadUserProfile for a domain account after a storage migration. The account authenticates, but the old roaming path is unreachable and the local mapping is incomplete, producing 1253. Correcting the profile path and permissions is safer than retrying the task under a temporary profile.

References

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