Keywords: Windows Service | Error 1920 | Privilege Verification | Service Installation | System Policy
Abstract: This article provides a comprehensive analysis of the common Windows service installation error 1920 (service failed to start), exploring root causes from multiple perspectives including privilege verification, system policies, and dependency relationships. Based on real-world cases and best practices, it systematically introduces key technical aspects such as verifying service startup permissions, configuring user rights assignments, and checking system dependencies to help developers thoroughly resolve service deployment challenges.
Technical Background and Problem Analysis of Error 1920
Error code 1920 during Windows service installation is a generic error indicating that the service failed to start successfully. This error is typically related to permission configurations, system policies, or dependency issues. In service deployment scenarios, even when running the installer as administrator and ensuring the service logon account has administrative privileges, this error may still occur.
Core Steps for Privilege Verification
The first step is to confirm whether the service account has been granted appropriate permissions. Checking the "Log on as a service" rights assignment through the Local Security Policy tool (SecPol.msc) is a critical verification step. In "Local Policies"→"User Rights Assignment", locate the "Log on as a service" policy item and ensure the service run account has been added to this policy. If the account is not included, it needs to be manually added and the changes applied.
Dependency and System Configuration Checks
Service startup failures may stem from missing system dependencies. It is recommended to verify .NET Framework version compatibility, ensuring the minimum required version for the service is installed. Simultaneously check the running status of the Windows Management Instrumentation service, which manages system configuration information and its abnormalities may affect the service startup process.
Manual Configuration Verification Method
When the installer displays an error dialog, manual service configuration can be attempted. Open the Service Manager through services.msc, locate the target service, and manually set the username and password in its properties. If the system prompts "User was granted logon as service right", return to the installer and select the retry operation, which typically resolves privilege verification issues.
System Service Status Maintenance
The status of the Windows Installer service is crucial to the installation process. Check if this service is running normally by executing services.msc. If problems are encountered, try re-registering the Windows Installer service: first execute MSIEXEC /UNREGISTER to unregister, then execute MSIEXEC /REGSERVER to re-register. The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools can also be used to repair potentially corrupted system files.
Potential Issues at Code Level
Service startup failures may originate from exceptions in the code. Adding the <generatePublisherEvidence enabled="false"/> element in the service configuration file can avoid certain certificate verification issues. Simultaneously ensure that service initialization code properly handles all possible exception scenarios to prevent startup failures due to unhandled exceptions.
Comprehensive Troubleshooting Strategy
A systematic troubleshooting approach is recommended: first verify permission configurations, then check system dependencies, followed by eliminating code issues, and finally considering system environment factors. Recording detailed error logs helps locate the specific problem root cause. Validating the installation package on multiple test machines can distinguish environment-specific issues from universal problems.