How to fix “The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured the hosting process must be restarted in order to start this service. [ERROR_INCOMPATIBLE_SERVICE_SID_TYPE (0x50A)]” – Error Code 1290



lightbulb

Error Code 1290

Error code Error Code 1290 is a common Windows issue that typically arises from “The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured the hosting process must be restarted in order to start this service. [ERROR_INCOMPATIBLE_SERVICE_SID_TYPE (0x50A)]”.

Overview

In this article, we’ll focus on resolving the issue described as: “The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured the hosting process must be restarted in order to start this service. [ERROR_INCOMPATIBLE_SERVICE_SID_TYPE (0x50A)]”. This error, identified by the error code Error Code 1290, can impede your system’s performance, and here’s how you can fix it.

Identifying the Problem

Error Code 1290 is typically triggered by a mismatch in service SID (Security Identifier) types within a service host process. SID types are used to identify services and regulate their access permissions. When services with incompatible SID types are hosted together, it can lead to this error.

Common scenarios that may cause Error Code 1290:

  • Installing software that creates a new service with a different SID type
  • Modifying the SID type of an existing service
  • System updates or changes that affect service SID configurations

Common Fixes

Restart the Service Host Process

  1. Identify the process hosting the affected service:
  2. Open Task Manager (Ctrl+Shift+Esc)
  3. Click on the “Services” tab
  4. Locate the service experiencing the error
  5. Note the “PID” (Process ID) for the service

  6. Restart the host process:

  7. Open Command Prompt (cmd) as administrator
  8. Run the following command:
    taskkill /pid [PID] /f
  9. Replace [PID] with the Process ID you noted earlier

  10. Restart the affected service:

  11. Open Services (services.msc) as administrator
  12. Locate the affected service
  13. Right-click on the service and select “Start”

Modify Service SID Type

  1. Open Registry Editor (regedit) as administrator
  2. Navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\[ServiceName]
  3. Replace [ServiceName] with the name of the affected service

  4. Create or modify the following DWORD value:

  5. Name: SidType
  6. Value:

    • 0: Restricted Service SID Type
    • 1: Unrestricted Service SID Type
  7. Restart the service host process as mentioned in the previous fix.

Advanced Troubleshooting

Check Group Policy Settings

Group Policy settings can influence service SID types. Verify the following settings:

  • Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options
  • Ensure that “Restrict SID to the same account as the service” is disabled
  • Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment
  • Check if the service account has the “Act as part of the operating system” privilege

Consider a System Restore

If the above solutions fail, consider performing a System Restore to a point before the error occurred. This will revert system settings and configurations, potentially resolving the issue.

Conclusion

Error Code 1290 can be resolved effectively by following the provided fixes. Remember to restart the affected service and its host process after implementing any changes. Preventing this error in the future involves maintaining consistent SID type configurations and applying system updates promptly. By following these guidelines, you can ensure the smooth operation of your system.