How to fix Error 1064 on Windows 11

Windows Error 1064: An Exception Occurred in the Service When Handling the Control Request

Why This Error Happens

Error 1064 typically occurs when a Windows service crashes or throws an unhandled exception while processing a start, stop, pause, or control command from the Service Control Manager (SCM). This is often caused by corrupted service binaries, missing or misconfigured dependencies (such as .NET Framework components or DLLs), or insufficient permissions for the service account to access required registry keys or files. In some cases, third-party software conflicts or outdated drivers tied to the service can also trigger this exception on Windows 11.

Step-by-Step Resolution Guide

  1. Check the Event Viewer for details: Press Win + X → select Event Viewer → navigate to Windows Logs > System and Windows Logs > Application. Look for the exact error tied to Event ID 1064 and note the faulting service name and exception details.

  2. Verify service permissions: Open services.msc, right-click the affected service → Properties → Log On tab. Ensure it’s set to “Local System” (or the correct account) and that the account has proper permissions. If needed, reset via:

   sc sdset [ServiceName] D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)
  1. Run System File Checker and DISM to repair corrupted system files:
   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Restart the machine after completion.

  1. Reinstall or repair the service’s dependencies: If the service relies on .NET Framework, Visual C++ Redistributables, or a specific driver, reinstall these components via Settings > Apps > Optional Features, or download the latest redistributable from Microsoft’s official site.

  2. Check for conflicting or outdated drivers: Open Device Manager, look for any devices with warning icons related to the service, and update or roll back drivers accordingly. Reboot after changes.

Alternative or Verification Steps

  • Verify the fix: Restart the service via services.msc or run net start [ServiceName] in an elevated Command Prompt — it should start without triggering Event ID 1064 in Event Viewer.
  • Alternative fix: If the issue persists, perform a clean boot (via msconfig) to rule out third-party interference, or use System Restore to roll back to a point before the error began occurring.