How to fix Error 1341 on Windows 11

by

Why This Error Happens

Error 1341 typically occurs when a background Windows service required by the application—often the Windows Installer service or a dependent server component (such as the Server service or a related COM+ system service)—has been manually disabled or set to a startup type that prevents it from running. This can happen after a Group Policy change, a security hardening script, or manual tweaking in the Services console. Without this service active, the installer or application cannot communicate with the required server process, triggering the “server is currently disabled” message.

Step-by-Step Resolution Guide

Step 1: Verify the Service Status

  • Press Win + R, type services.msc, and press Enter.
  • Locate the Server service and the Windows Installer service in the list.
  • Check the Status column to confirm if either shows blank (stopped) or the Startup Type is set to Disabled.

Step 2: Re-Enable and Start the Required Service

  • Right-click on the Server service (or the relevant dependent service) and select Properties.
  • Change Startup type from Disabled to Automatic.
  • Click Apply, then click Start to launch the service immediately.
  • Repeat the same process for the Windows Installer service if it is also disabled.

Step 3: Check Group Policy for Service Restrictions

  • Press Win + R, type gpedit.msc, and press Enter.
  • Navigate to Computer Configuration > Windows Settings > Security Settings > System Services.
  • Ensure the relevant service is Not Defined or set to Automatic, rather than being forcibly disabled by policy.
  • Run gpupdate /force in Command Prompt (Admin) to apply changes.

Step 4: Restart the System

  • Reboot Windows 11 to ensure all service dependencies reload correctly.
  • After reboot, retry the action (installation, application launch, or network operation) that originally triggered Error 1341.

Alternative or Verification Steps

  • Open Event Viewer (eventvwr.msc) and check the System log for Event ID 1341 to confirm the service now starts without errors.
  • If the issue persists, run sfc /scannow in an elevated Command Prompt to repair any corrupted system files that may be preventing the service from initializing properly.