Cannot uninstall SQL Server 2022 Express instances on Windows 11 (instance corrupted, not visible in Installation Center)

Mohammad Bimo Nurcahyo 20 Reputation points
2025-10-02T12:51:19.5433333+00:00

Hello Microsoft Support,

I am experiencing an issue with SQL Server 2022 Express installation on my Windows 11 Home (build 26100).

🔹 Problem

I previously attempted multiple installs of SQL Server 2022 Express.

Now I have several instances (SQLEXPRESS, SQLEXPRESS01, SQLEXPRESS02, etc.).

Some instances appear corrupted:

They do not show up in SQL Server Installation Center → Remove SQL Server instance.

  They also cannot be fully uninstalled from **Programs and Features**.
  
  When I try to install a new instance, I get the error: **“Could not find the Database Engine startup handle”**.
  
  • I found in the logs: Error result: -2061893607 Reason for failure: Could not find the Database Engine startup handle
    I also suspect this might be related to the 4KB sector size issue mentioned in Microsoft docs: Troubleshoot OS 4KB disk sector size.

🔹 What I already tried

Uninstalled all SQL Server-related apps from Installed Apps and Programs and Features.

Used Microsoft Program Install and Uninstall Troubleshooter – it removed SQL Server 2022 Setup and VSS Writer successfully.

Manually deleted leftover folders in C:\Program Files\Microsoft SQL Server.

Tried Repair via setup, but Database Engine Services always fails.

Restarted laptop multiple times.

Did not touch the Windows Registry manually (I don’t want to risk system instability).

🔹 What I need

A safe method to completely remove all corrupted SQL Server 2022 instances without editing the registry manually.

Guidance whether applying CU21 (SQL Server 2022 cumulative update) would bypass this issue, or if I should downgrade to SQL Server 2019.

System details:

Windows 11 Home Single Language 64-bit

  • SQL Server 2022 Express (multiple failed instances)

I also suspect this might be related to the 4KB sector size issue mentioned in Microsoft docs:
Troubleshoot OS 4KB disk sector size.

  • 🔹 What I already tried

Uninstalled all SQL Server-related apps from Installed Apps and Programs and Features.

Used Microsoft Program Install and Uninstall Troubleshooter – it removed SQL Server 2022 Setup and VSS Writer successfully.

Manually deleted leftover folders in C:\Program Files\Microsoft SQL Server.

Tried Repair via setup, but Database Engine Services always fails.

Restarted laptop multiple times.

Did not touch the Windows Registry manually (I don’t want to risk system instability).

  • 🔹 What I need

A safe method to completely remove all corrupted SQL Server 2022 instances without editing the registry manually.

Guidance whether applying CU21 (SQL Server 2022 cumulative update) would bypass this issue, or if I should downgrade to SQL Server 2019.

System details:

Windows 11 Home Single Language 64-bit

  SQL Server 2022 Express (multiple failed instances)
  
     Logs show multiple instance IDs: `SQLEXPRESS`, `SQLEXPRESS01`, `SQLEXPRESS02`, `SQLEXPRESS03`.
     
  • Logs show multiple instance IDs: SQLEXPRESS, SQLEXPRESS01, SQLEXPRESS02, SQLEXPRESS03.
SQL Server Database Engine
0 comments No comments
{count} votes

Answer accepted by question author
  1. Erland Sommarskog 129.6K Reputation points MVP Volunteer Moderator
    2025-10-02T19:46:04.0533333+00:00

    This is not Microsoft Support, but a peer-to-peer forum. If you want to talk to Microsoft Support, you need to open a support case (which would only be an option, if you are in a corporate environment, and your organisation has a support contract.)

    You may want to look at this article: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/. Some people have reported success when they have followed the directions in the article. (Although the article may include registry edits.)

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.