sodcalculator

10 Tech How-To

Fix User Has Not Been Authenticated Error in Windows 11/10/Server

Guide 10-47896 · Updated · Step by step

The “User has not been authenticated” error in Windows 11, 10, and Server typically appears when a service, scheduled task, or application tries to access a network resource or run a process without valid credentials. The fix is to update the logon credentials for the affected service or task, or to reconfigure the security policy that is blocking authentication. Below are the exact steps to resolve this error across common scenarios.

What Causes the Error

This error is not a single failure but a symptom of several underlying issues. The most common causes are:

  • Stale service credentials – A Windows service (like SQL Server, IIS AppPool, or a custom application) has a saved password that was changed or expired.
  • Group Policy restrictions – The “Deny log on locally” or “Deny access to this computer from the network” policies may block the account.
  • Corrupted user profile – The profile that the service uses is damaged or missing.
  • Kerberos or NTLM issues – Time skew between the client and domain controller, or a missing SPN (Service Principal Name) can cause authentication failures.
  • UAC or Protected Process Light – Some system processes run under a protected account that cannot be used for network logons.

In Windows Server environments, the error often appears in Event Viewer under System or Application logs with Event ID 7038 or 7000, but the message itself can appear in a dialog box when starting a service or in a command-line tool.

How Authentication Works in Windows Services

Windows services run under a security context, usually LocalSystem, NetworkService, LocalService, or a specific user account. When you set a service to run under a domain account, Windows stores the password in the Local Security Authority (LSA) secrets. If that password changes or the account is locked out, the service cannot log on, and the system throws the authentication error.

For scheduled tasks, the same principle applies: the task stores credentials in the Task Scheduler, and if they are invalid, the task fails with this message. For IIS application pools, the worker process identity must authenticate to the content or database, and a misconfigured identity will cause the error.

How to Fix It (Step-by-Step)

Follow these steps in order, testing after each one.

  1. Identify the failing component – Open Event Viewer (eventvwr.msc), go to Windows Logs > System and Application, and look for errors around the time the issue occurred. Note the source (e.g., Service Control Manager, .NET Runtime) and the exact error message.
  2. Update the service logon – Open Services.msc, find the service, right-click > Properties > Log On tab. Enter the correct password for the account, click Apply, then start the service. If you don’t know the password, you may need to reset it in Active Directory or on the local machine.
  3. For scheduled tasks – Open Task Scheduler, right-click the task > Properties > General tab. Click “Change User or Group” and re-enter the password. Check the “Run whether user is logged on or not” option and store the password.
  4. Check Group Policy – Run gpedit.msc (Pro/Enterprise) or use the Group Policy Management console on a domain. Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment. Ensure the account is not in “Deny log on locally” or “Deny access to this computer from the network”.
  5. Reset the account password – If the account is a domain account, reset its password in Active Directory Users and Computers. Then update all services and tasks that use it. For local accounts, use net user username newpassword in an elevated command prompt.
  6. Repair the user profile – If the profile is corrupted, back up the user’s files, then delete the profile in System Properties > Advanced > User Profiles. Recreate it by logging in once with that account.
  7. Check time synchronization – Ensure the machine’s clock is within 5 minutes of the domain controller. Run w32tm /resync in an elevated command prompt.
  8. Verify SPNs – If the error is Kerberos-related, run setspn -L accountname to list SPNs. If missing, add the correct SPN (e.g., setspn -A HTTP/servername domain\account).

After each step, restart the service or task and check if the error clears.

Common Variations and Their Fixes

The error appears in different contexts, and the fix varies slightly:

  • IIS Application Pool – Open IIS Manager, select the application pool, click Advanced Settings, and set the Identity to a valid account. Ensure the password is correct and that the account has read access to the site’s physical path.
  • SQL Server Agent – In SQL Server Configuration Manager, right-click SQL Server Agent > Properties > Log On tab, update the password, and restart.
  • Windows Update or Backup – These services often run as SYSTEM, but if you’ve changed them, revert to the default logon (LocalSystem) unless you have a specific reason.
  • Network Drive Mapped in a Service – Services cannot see mapped drives by default. Use a UNC path (\server\share) instead, and grant the service account permissions on the share.

How to Prevent It from Happening Again

Prevention is easier than troubleshooting. Implement these practices:

  • Use Group Policy to enforce strong passwords and regular password rotation for service accounts.
  • Prefer Managed Service Accounts (MSA) or Group Managed Service Accounts (gMSA) in Active Directory – these have automatically rotated passwords and no manual updates.
  • Document every service and task that uses a specific account, so when the password changes, you know what to update.
  • Set up alerts in Event Viewer for Event ID 7038 (service logon failure) to catch issues early.

When to Use a Managed Service Account

If you are on a domain and have Windows Server 2008 R2 or later, consider switching to a gMSA. These accounts are tied to the computer objects, and their passwords are automatically changed every 30 days by the domain controller. This eliminates the “password changed” problem entirely. To use one, you need to install the Active Directory module for PowerShell, create the account, and then assign it to the service. The process is more complex upfront but saves time in the long run.

Frequently Asked Questions

Q: Why does the error appear even after I enter the correct password?
A: The account may be locked out, disabled, or denied logon rights. Check the account status in Active Directory or Local Users and Groups. Also, ensure the password has no trailing spaces and that the “User must change password at next logon” option is unchecked for service accounts.

Q: Can I run a service with no password?
A: Yes, but only under built-in accounts like LocalSystem or NetworkService. These do not require passwords but have limited access to network resources. If you need network access, use a domain account or a gMSA.

Q: The error occurs in a scheduled task, not a service. What’s different?
A: Scheduled tasks store credentials in the Task Scheduler’s secure store. If the task was created under one user and the password changed, you must re-enter it. Also, check that the task is set to “Run whether user is logged on or not” – otherwise it may not run at all.

Q: Does this error affect Windows 11 Home?
A: Yes, but Home edition lacks Local Group Policy Editor (gpedit.msc). You can still fix services and tasks via the Services and Task Scheduler consoles. For policy checks, use the command line with secpol.msc (which is available in Home) or edit the registry directly.

Q: Is there a way to bypass this error for testing?
A: You can temporarily set the service to log on as LocalSystem to see if the issue is account-specific. However, this is not a long-term fix because LocalSystem has elevated privileges and may not have network access. Always revert to a properly configured account.

Q: What if the error is caused by a corrupted Windows profile?
A: Create a new local administrator account, log in with it, and see if the error persists. If it does not, migrate your files and settings to the new profile. Do not delete the old profile until you are sure everything works.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →