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

Collins, John L 20 Reputation points
2026-09-02T13:13:03.4766667+00:00

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

SQL Server Database Engine
Answer accepted by question author
Himaja Y 545 Reputation points Microsoft External Staff Moderator
2026-09-04T11:10:55.87+00:00

Hi @Collins, John L ,

Thank you for reaching out to the Microsoft Q&A forum.

Based on the information provided, the log only confirms that the SQL Server 2022 Express patch/upgrade failed, but it does not show the actual root cause.

The next step is to review the detailed setup and SQL Server logs to determine why the Database Engine Services failed during the update.

Please check the following:

Open the setup log folder:

C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20260902_072017\

Review the detailed setup logs and look for any entries containing "Error", "Failed", or "Exception".

Check the SQL Server error log:

C:\Program Files\Microsoft SQL Server\MSSQL16.PRIMTECH\MSSQL\LOG\ERRORLOG

This file usually contains the exact reason why the SQL Server service could not start.

Verify that the SQL Server service is present in Services.msc and check whether it starts manually. If it fails, note the error message returned.

If the ERRORLOG contains messages related to disk sector size, I/O errors, or startup failures, it may be related to a known Windows 11 compatibility issue that can prevent SQL Server from starting correctly.

At this point, the most helpful information would be the contents of the ERRORLOG file and any detailed error messages found in the setup logs. Once those details are available, we can identify the exact cause and provide targeted troubleshooting steps.

Could you please share the relevant errors from the ERRORLOG file or the detailed setup logs? That will help us investigate further and provide a more accurate solution.

Was this answer helpful?

1 person found this answer helpful.
0 comments

3 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Collins, John L 20 Reputation points
    2026-09-11T20:41:30.1866667+00:00

    The end-user is currently out of office until the 28th. this time I going to fully log in remote to the PC and completely remove SQL and reinstall. I will choose Himaja Y's response as a guide

    Thank you everyone for the responses. I'll return if needed

    Was this answer helpful?

    0 comments
  2. Collins, John L 20 Reputation points
    2026-09-11T20:41:11.02+00:00

    The end-user is currently out of office until the 28th. this time I going to fully log in remote to the PC and completely remove SQL and reinstall. I will choose Himaja Y's response as a guide

    Thank you everyone for the responses. I'll return if needed

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-09-02T13:13:52.23+00:00

    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:

    1. Open the setup log folder for this failed attempt:
      C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20260902_072017\
    2. Review Summary_NADL251702_20260902_072017.txt and search for error or failed. The summary file is intended for that first pass.
    3. 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
    4. 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.
    5. 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.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer 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.