How to fix Error 1362 on Windows 11

by

Troubleshooting Guide: Error 1362 – “The Requested Action Is Restricted for Use by Logon Processes Only”

Why This Error Happens

Error 1362 occurs when a security-related API call (such as LsaLogonUser or LsaRegisterLogonProcess) is invoked by a process that lacks the necessary trust level to interact with the Local Security Authority (LSA). This is typically triggered by third-party authentication software, custom scripts, or security tools attempting to perform logon operations without proper registration as a trusted logon process. It can also surface due to corrupted security policies or misconfigured privilege assignments within the Local Security Authority Subsystem Service (LSASS).

Step-by-Step Resolution Guide

Step 1: Verify the Application Requesting Logon Access

  • Identify which application or service is throwing Error 1362 by checking the Event Viewer (eventvwr.msc) under Windows Logs > System and Windows Logs > Security.
  • Look for correlating Event IDs (such as 4624 or 6167) around the same timestamp to identify the calling process.
  • Confirm if the software is third-party (e.g., VPN clients, custom SSO tools, or legacy authentication agents) rather than a native Windows component.

Step 2: Run the Application with Elevated/Trusted Privileges

  • Right-click the application executable and select Run as Administrator to test if elevation resolves the trust issue.
  • If the app is a service, open services.msc, locate the service, go to Properties > Log On tab, and ensure it is set to Local System Account rather than a restricted user account.
  • Restart the service after applying changes:
  net stop [ServiceName]
  net start [ServiceName]

Step 3: Check and Repair Local Security Policy Settings

  • Open the Local Security Policy editor by running secpol.msc.
  • Navigate to Local Policies > User Rights Assignment.
  • Verify that “Act as part of the operating system” policy includes the necessary service account (this right is required for legitimate logon process registration).
  • Apply changes with gpupdate /force and restart the machine.

Step 4: Repair Corrupted System Files

  • Open Command Prompt as Administrator and run the System File Checker to rule out corruption in LSASS-related components:
  sfc /scannow
  • Follow up with a DISM health restore if SFC finds unrepairable errors:
  DISM /Online /Cleanup-Image /RestoreHealth
  • Reboot Windows 11 once both scans complete successfully.

Alternative or Verification Steps

  • Verify the Fix: Reproduce the original action that triggered Error 1362 (e.g., relaunch the third-party logon software) and confirm the Event Viewer no longer logs the error under System logs.
  • Alternative Solution: If the error persists, uninstall and reinstall the offending third-party authentication software, as it may need to re-register its logon process handlers with a fresh installation.