Share via

SQL Server 2022 installation fails with error code 1639

Cullen Sharp 0 Reputation points
2025-07-21T22:13:54.97+00:00

I've been trying to install SQL Server 2022 on Windows 10 Enterprise. Each time I try, the installer fails with error code 1639.

Each time I attempt to reinstall I

  1. Uninstall all SQL Server related items in the control panel
  2. Remove SQL Server folders in Program Files and Program Files (x86)
  3. Remove all registry keys related to SQL Server

This process follows https://www.sql-easy.com/learn/how-to-uninstall-sql-server/

I will attach the logs from C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20250721_145706

(01) 2025-07-21 14:57:31 Slp: Error result: -2068052377
(01) 2025-07-21 14:57:31 Slp: Result facility code: 1212
(01) 2025-07-21 14:57:31 Slp: Result error code: 1639
(01) 2025-07-21 14:57:31 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
(01) 2025-07-21 14:57:32 Slp: WER: Result of the submission:: 'WerReportQueued'
(01) 2025-07-21 14:57:32 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
(01) 2025-07-21 14:57:32 Slp: WER: Result of the submission:: 'WerReportQueued'
(01) 2025-07-21 14:57:32 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
(01) 2025-07-21 14:57:32 Slp: WER: Result of the submission:: 'WerReportQueued'
(01) 2025-07-21 14:57:32 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
(01) 2025-07-21 14:57:32 Slp: WER: Result of the submission:: 'WerReportQueued'
(01) 2025-07-21 14:57:32 Slp: WER: Submitted 4 of 4 failures to the Watson data repository
(01) 2025-07-21 14:57:32 Slp: SetupTelemetry: Closing Telemetry Session
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\SQMClient
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to get registry value MachineId
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\160
(01) 2025-07-21 14:57:32 Slp: SetupTelemetry: Not creating telemetry audit log. Value 'UserRequestedLocalAuditDirectory' doesn't exist in 'HKLM\Software\Microsoft\Microsoft SQL Server\160
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\160
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2025-07-21 14:57:32 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2025-07-21 14:57:32 Slp: SetupTelemetry: Telemetry has an active session with 50 events.

Also, the logs from summary

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20250721_145706\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639
  Feature:                       SQL Browser
  Status:                        Passed
  Feature:                       SQL Writer
  Status:                        Passed
  Feature:                       Setup Support Files
  Status:                        Passed
Rules with failures or warnings:
Rules report file:               C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20250721_145706\SystemConfigurationCheck_Report.htm
SQL Server | Other

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Thumu Sai Pranay 0 Reputation points
    2025-11-21T11:57:42.2+00:00

    Hi @Cullen Sharp ,

    Thanks for sharing the logs. Error 1639 means the SQL Server setup is failing due to an invalid installation parameter, not because of leftover files or registry keys. This typically comes from a previous install that saved a corrupted ConfigurationFile.ini, or from incomplete setup media.

    Please try the steps below:

    1. Go to: C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log* Delete any existing ConfigurationFile.ini files before reinstalling.
    2. Download a fresh SQL Server 2022 installer directly from Microsoft Download Center and avoid previously saved/modified media.
    3. Run the installation using setup.exe as Administrator, without using a configuration file or edited parameters. (Do not run individual MSI files.)
    4. When selecting the instance name, use only letters/numbers (example: MSSQLSERVER).
    5. Ensure Windows 10 has the latest updates installed, then retry setup.

    If the issue persists after these steps, please let us know we are happy to assist you to resolve the issue.

    Thank you.

    0 comments

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.