How to fix Error 1300 on Windows 11

by

Why This Error Happens

Error 1300 occurs when the Windows security subsystem cannot map all the required privileges or Security Identifiers (SIDs) to the account attempting to perform a privileged operation. This typically happens because the user account lacks specific User Rights Assignments (such as “Restore files and directories” or “Manage auditing and security log”) in the Local Security Policy, or because the account’s token was generated before a recent Group Policy update was applied. It can also occur when a service or scheduled task is configured to run under an account that was deleted or has corrupted group membership data in the Security Accounts Manager (SAM).

Step-by-Step Resolution Guide

Step 1: Verify and Assign Required User Rights

  • Press Win + R, type secpol.msc, and hit Enter to open Local Security Policy.
  • Navigate to Security Settings > Local Policies > User Rights Assignment.
  • Locate the specific privilege mentioned in the failing operation (e.g., “Back up files and directories,” “Take ownership of files or other objects,” or “Manage auditing and security log”).
  • Double-click the policy and click Add User or Group, then add the affected user or service account.

Step 2: Refresh Group Policy and Security Token

  • Open Command Prompt as Administrator.
  • Run gpupdate /force to reapply all Group Policy settings immediately.
  • Log the affected user out completely and log back in (or reboot the machine) to force Windows to regenerate the security access token with the updated privileges.

Step 3: Check the Service or Task Account Configuration

  • Press Win + R, type services.msc, and press Enter.
  • Right-click the relevant service, select Properties, and go to the Log On tab.
  • Ensure the account listed (e.g., Local System, Network Service, or a custom domain account) is valid and re-enter the password if using a custom account.
  • If using Task Scheduler, open taskschd.msc, locate the task, and under General, ensure “Run with highest privileges” is checked if administrative rights are needed.

Step 4: Repair Corrupted Local Security Database

  • Boot into Safe Mode if the system is unstable.
  • Open Command Prompt as Administrator and run sfc /scannow to repair corrupted system files, including security policy components.
  • Restart the machine normally once the scan completes.

Alternative or Verification Steps

  • To verify the fix, attempt the original action (e.g., backup job, service start, or administrative task) again and check the Event Viewer (eventvwr.msc) under Windows Logs > System for the absence of Event ID 1300.
  • If the error persists, use whoami /priv in Command Prompt to confirm the current user’s token actually includes the required privilege; if it’s missing, the account needs to be re-added to the appropriate security group (e.g., Administrators or Backup Operators) via lusrmgr.msc.