I found this: (01) 2024-06-30 16:46:44 Slp: Sco: File 'C:\SQL2022\Developer_ENU\x64\setup\x64\sql_engine_core_inst.msi' does not exist You are not the first to experience this error. Before I go on, let me ask: was this your first installation attempt, or did you come here first after having tried multiple times, possibly performing some random cleanup attempts in between? I will assume the latter, as it is quite natural path to take. Also, it seems that most people who have seen this error, have also done this. My hypothesis (note the word, to be honest, I don't have that much of a clue), is that this particular error is due to the result of multiple installation attempts where installation caches, registry values etc have become inconsistent. What you can try is to follow the instructions here: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/ . Some people who have followed this page were actually able to install SQL Server successfully, and, in fact I learnt about this page from one of them. Then you could make a new attempt. Or, well, before you do that, read https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size to make sure that you are not victim to this known issue, and which might have been the reason for installation failing initially. By the way, what sort of hardware are you trying to install SQL Server on?

How to fix Unable to install SQL Server (setup.exe). Exit code (Decimal): -2068052377Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.

nguyen hoang 20

User's image

Detail.txt

nguyen hoang 20 Reputation points

2024-06-30T10:35:01.94+00:00

Here is the config file
;SQL Server 2022 Configuration File

[OPTIONS]

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.

ACTION="Install"

; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system.

ENU="True"

; Indicates whether the supplied product key is covered by Service Assurance.

PRODUCTCOVEREDBYSA="False"

; Specifies that SQL Server Setup should not display the privacy statement when ran from the command line.

SUPPRESSPRIVACYSTATEMENTNOTICE="False"

; Setup will not display any user interface.

QUIET="True"

; Setup will display progress only, without any user interaction.

QUIETSIMPLE="False"

; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.

UIMODE="Normal"

; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found.

UpdateEnabled="False"

; If this parameter is provided, then this computer will use Microsoft Update to check for updates.

USEMICROSOFTUPDATE="False"

; Specifies that SQL Server Setup should not display the paid edition notice when ran from the command line.

SUPPRESSPAIDEDITIONNOTICE="False"

; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services.

UpdateSource="MU"

; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install shared components.

FEATURES=SQLENGINE

; Displays the command line parameters usage.

HELP="False"

; Specifies that the detailed Setup log should be piped to the console.

INDICATEPROGRESS="True"

; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), or Analysis Services (AS).

INSTANCENAME="MSSQLSERVER"

; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed.

INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"

; Specify the root installation directory for the WOW64 shared components. This directory remains unchanged after WOW64 shared components are already installed.

INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"

; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance.

INSTANCEID="MSSQLSERVER"

; Startup type for the SQL Server CEIP service.

SQLTELSVCSTARTUPTYPE="Automatic"

; Account for SQL Server CEIP service: Domain\User or system account.

SQLTELSVCACCT="NT Service\SQLTELEMETRY"

; Specify the installation directory.

INSTANCEDIR="C:\Program Files\Microsoft SQL Server"

; Agent account name.

AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"

; Auto-start service after installation.

AGTSVCSTARTUPTYPE="Manual"

; Startup type for the SQL Server service.

SQLSVCSTARTUPTYPE="Automatic"

; Level to enable FILESTREAM feature at (0, 1, 2 or 3).

FILESTREAMLEVEL="0"

; The max degree of parallelism (MAXDOP) server configuration option.

SQLMAXDOP="8"

; Set to "1" to enable RANU for SQL Server Express.

ENABLERANU="False"

; Specifies a Windows collation or an SQL collation to use for the Database Engine.

SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"

; Account for SQL Server service: Domain\User or system account.

SQLSVCACCOUNT="NT Service\MSSQLSERVER"

; Set to "True" to enable instant file initialization for SQL Server service. If enabled, Setup will grant Perform Volume Maintenance Task privilege to the Database Engine Service SID. This may lead to information disclosure as it could allow deleted content to be accessed by an unauthorized principal.

SQLSVCINSTANTFILEINIT="True"

; Windows account(s) to provision as SQL Server system administrators.

SQLSYSADMINACCOUNTS="DESKTOP-HAD5IG5\ADMIN"

; The number of Database Engine TempDB files.

SQLTEMPDBFILECOUNT="8"

; Specifies the initial size of a Database Engine TempDB data file in MB.

SQLTEMPDBFILESIZE="8"

; Specifies the automatic growth increment of each Database Engine TempDB data file in MB.

SQLTEMPDBFILEGROWTH="64"

; Specifies the initial size of the Database Engine TempDB log file in MB.

SQLTEMPDBLOGFILESIZE="8"

; Specifies the automatic growth increment of the Database Engine TempDB log file in MB.

SQLTEMPDBLOGFILEGROWTH="64"

; Provision current user as a Database Engine system administrator for SQL Server 2022 Express.

ADDCURRENTUSERASSQLADMIN="False"

; Specify 0 to disable or 1 to enable the TCP/IP protocol.

TCPENABLED="0"

; Specify 0 to disable or 1 to enable the Named Pipes protocol.

NPENABLED="0"

; Startup type for Browser Service.

BROWSERSVCSTARTUPTYPE="Disabled"

; Use SQLMAXMEMORY to minimize the risk of the OS experiencing detrimental memory pressure.

SQLMAXMEMORY="2147483647"

; Use SQLMINMEMORY to reserve a minimum amount of memory available to the SQL Server Memory Manager.

SQLMINMEMORY="0"
nguyen hoang 20 Reputation points

2024-06-30T10:36:51.9966667+00:00

can someone help
nguyen hoang 20 Reputation points

2024-06-30T10:37:38.7933333+00:00

DESKTOP-HAD5IG5_20240630_164625_Watson.txt
here the summary

Accepted answer

Erland Sommarskog 115.1K Reputation points MVP

2024-06-30T10:57:53.2566667+00:00

I found this:

(01) 2024-06-30 16:46:44 Slp: Sco: File 'C:\SQL2022\Developer_ENU\x64\setup\x64\sql_engine_core_inst.msi' does not exist

You are not the first to experience this error.

Before I go on, let me ask: was this your first installation attempt, or did you come here first after having tried multiple times, possibly performing some random cleanup attempts in between? I will assume the latter, as it is quite natural path to take. Also, it seems that most people who have seen this error, have also done this.

My hypothesis (note the word, to be honest, I don't have that much of a clue), is that this particular error is due to the result of multiple installation attempts where installation caches, registry values etc have become inconsistent.

What you can try is to follow the instructions here: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/. Some people who have followed this page were actually able to install SQL Server successfully, and, in fact I learnt about this page from one of them. Then you could make a new attempt. Or, well, before you do that, read https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size to make sure that you are not victim to this known issue, and which might have been the reason for installation failing initially.

By the way, what sort of hardware are you trying to install SQL Server on?
Please sign in to rate this answer.

1 person found this answer helpful.
nguyen hoang 20 Reputation points

2024-06-30T11:18:17.3333333+00:00

yes i have install multi time and when i tried to install again this error thanks for the link to uninstall the sql let me follow the guide, thanks again
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix Unable to install SQL Server (setup.exe). Exit code (Decimal): -2068052377Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.

0 additional answers

Your answer