Installed SQL server 2022 express on windows 11 PC - Database engine services failed

Question

Installed SQL server 2022 express on windows 11 PC - Database engine services failed

Collins, John L 0

After the install have "Completed with failures" with "Database Engine Services" with Failed status

I just a desktop tech and do not know much about SQL server express and the end-user does not either but needs this software installed.

Please assistance if possible on how to resolve this issue

Thank you!

this is the contents of the "Summary_NADL251702_20260902_072017.txt" file:

Overall summary:

Final result: The patch installer has failed to update the following instance: PRIMTECH. To determine the reason for failure, review the log files.

Exit code (Decimal): -2061893558

Start time: 2026-09-02 07:20:17

End time: 2026-09-02 07:20:48

Requested action: Patch

Instance PRIMTECH overall summary:

Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.

Exit code (Decimal): -2061893558

Start time: 2026-09-02 07:20:31

End time: 2026-09-02 07:20:46

Requested action: Patch

Machine Properties:

Machine name: NADL251702

Machine processor count: 20

OS version: Microsoft Windows 11 Enterprise (10.0.26200)

OS service pack:

OS region: United States

OS language: English (United States)

OS architecture: x64

Process architecture: 64 Bit

OS clustered: No

Product features discovered:

Product Instance Instance ID Feature Language Edition Version Clustered Configured

SQL Server 2022 PRIMTECH MSSQL16.PRIMTECH Database Engine Services 1033 Express Edition 16.0.1000.6 No Yes

SQL Server 2022 PRIMTECH MSSQL16.PRIMTECH SQL Server Replication 1033 Express Edition 16.0.1000.6 No Yes

Package properties:

Description: Microsoft SQL Server 2022

ProductName: SQL Server 2022

Type: RTM

Version: 16

SPLevel: 0

KBArticle: KB5102334

KBArticleHyperlink: https://support.microsoft.com/?kbid=5102334

PatchType: GDR

AssociatedHotfixBuild: 4262

Platform: x64

PatchLevel: 16.0.1190.2

ProductVersion: 16.0.1000.6

GDRReservedRange: 16.0.1100.0:16.0.3999.0

Installation location: C:\859b3e876fb99bb9e064d06c07bf\x64\setup\

Updated product edition:

Instance Edition

PRIMTECH Express

User Input Settings:

ACTION: Patch

ALLINSTANCES: true

CLUSTERPASSIVE: false

CONFIGURATIONFILE:

ENU: true

HELP: false

IACCEPTSQLSERVERLICENSETERMS: true

IACKNOWLEDGEENTCALLIMITS: false

INDICATEPROGRESS: false

INSTANCEID: <empty>

INSTANCENAME: <empty>

QUIET: true

QUIETSIMPLE: false

SUPPRESSPAIDEDITIONNOTICE: false

SUPPRESSPRIVACYSTATEMENTNOTICE: false

UIMODE: Normal

Rules with failures or warnings:

Rules report file: C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20260902_072017\SystemConfigurationCheck_Report.htm

Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-09-02T13:33:06.73+00:00

In the folder C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20260902_072017 there should also be a file detail.txt. Can you attach this file? (Please do not paste into the posting window. It is far too long for that.)
Collins, John L 0 Reputation points

2026-09-03T19:47:12.12+00:00

To:Erland Sommarsk: Here is the details files sorry for long delay

Detail.txt

thank you!
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-09-03T21:21:25.0133333+00:00

Unfortunately, the log did only say that patching failed. Maybe I would need yet another log file.

But you are no applying the right patch in my opinion anyway. This is a security patch for the RTM version of SQL 2022, which your user should not be running. I suggest that you instead download and install Cumulative Update 26, which is the most recent CU and which includes lots of bug fixes and enhancements. I would not be surprised if this fails too, but it would be more relevant to investigate that case.

1 answer

Your answer

Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-09-02T13:33:06.73+00:00

In the folder C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20260902_072017 there should also be a file detail.txt. Can you attach this file? (Please do not paste into the posting window. It is far too long for that.)
Collins, John L 0 Reputation points

2026-09-03T19:47:12.12+00:00

To:Erland Sommarsk: Here is the details files sorry for long delay

Detail.txt

thank you!
Erland Sommarskog 137.1K Reputation points MVP Volunteer Moderator

2026-09-03T21:21:25.0133333+00:00

Unfortunately, the log did only say that patching failed. Maybe I would need yet another log file.

But you are no applying the right patch in my opinion anyway. This is a security patch for the RTM version of SQL 2022, which your user should not be running. I suggest that you instead download and install Cumulative Update 26, which is the most recent CU and which includes lots of bug fixes and enhancements. I would not be surprised if this fails too, but it would be more relevant to investigate that case.

Answer 1

The summary shown is only telling that the patch failed. The next step is to identify why the SQL Server service did not start during patching.

Use this path:

Open the setup log folder for this failed attempt:
C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20260902_072017\
Review Summary_NADL251702_20260902_072017.txt and search for error or failed. The summary file is intended for that first pass.
Then check the SQL Server error log for the instance because setup specifically relies on that when Database Engine startup fails:
C:\Program Files\Microsoft SQL Server\MSSQL16.PRIMTECH\MSSQL\LOG\ERRORLOG
Verify the SQL Server service startup configuration and credentials:
- Confirm whether the SQL Server service startup type is Automatic or Manual.
- Verify the service account and password are valid and not expired.
If the ERRORLOG contains a message like:
There have been 256 misaligned log IOs which required falling back to synchronous IO then this matches a known Windows 11 disk sector size issue that can prevent SQL Server from starting.

Important note: if the issue is the Windows 11 disk sector size problem, the documented guidance is to use the published workaround for that condition. Also, if setup failed to complete configuration, uninstalling the instance and then running setup again after applying the fix is the simpler path.

If the summary log for the upgrade contains this exact message, repair is supported:

SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, and then repair your installation.

If the summary log instead contains this exact message, repair is not supported and uninstall/reinstall is required:

SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem.

For this case, the most useful file to inspect next is ERRORLOG under the PRIMTECH instance log folder.