Unable to install SQL Server (setup.exe), VS Shell installation has failed with exit code 1638.

Question

Detail:

(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderConsole' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus' has been registered
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.PackageData.Package.xml'
(01) 2017-10-19 02:14:41 Slp: Reading schema resource 'Microsoft.SQL.Chainer.Package.Package.xsd'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.PackageData.Package.xml' validated with schema 'Microsoft.SQL.Chainer.Package.Package.xsd' has been successfuly loaded into datastore path '/Datastore/Package'
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: ReadProductXML
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.Product.Product.xml'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.Product.Product.xml' validated with schema 'Microsoft.SQL.Chainer.Product.Product.xsd' has been successfuly loaded into datastore path '/Datastore/Product'
(01) 2017-10-19 02:14:41 Slp: Completed Action: ReadProductXML, returned True
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: LoadExtensions
(01) 2017-10-19 02:14:42 Slp: Loading extension 'MSI' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.MsiExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'MSI' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Config' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Config' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Common' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.ExtensionCommon.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Common' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlConfigBase' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SqlConfigBase.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlConfigBase' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Slp' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SetupExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Slp' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'RulesEngine' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.RulesEngineExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'RulesEngine' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'WorkflowData' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.WorkflowData.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'WorkflowData' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SlpConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SlpExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SlpConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Clst' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Cluster.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Clst' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'AgentConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.AgentExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'AgentConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlPowershellConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.PowershellExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlPowershellConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SSISConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SSISExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SSISConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISMasterConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISMasterExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISMasterConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISWorkerConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISWorkerExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISWorkerConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'DReplayConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'DReplayConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ASConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ASExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ASConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ReplConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ReplConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsAdvancedConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsAdvancedConfig' version '14.0.1000.169' loaded

Answer 1

Hi Venandyka,

 

The exit code 1638 means "Another version of this program is already installed", this error message is provided by Windows Installer, please check if you have installed other later version of VS Shell on your machine.

 

Besides, have you installed Visual Studio 2017 on your machine? Based on my experience, this can also affect the installation of SQL Server 2017. The version of VS Shell inside some versions of Visual Studio 2017 is later than the VS Shell inside SQL Server, as a result, you will meet this problem, please check it.

 

As a workaround for it, you can first uninstall Visual Studio 2017, then install SQL Server 2017, after that, install Visual Studio 2017 again.

Best Regards,

Teige

 

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 2

Please check the LOG. I have the same issue (VS SHELL), but checking the log file I found that I have

Microsoft Visual C++ 2017 and 2012, NOT 2015

Uninstall 2017 and install 2015 and after 2017.

After these operations you can install SQL Server.

Answer 3

The problem is likely that there's a newer version of the Visual C++ Redistributable than SQL Server is trying to install, e.g., from Visual Studio 2017. So another way to address this, if you don't need the latest C++ redistributable, is to go to Add or Remove Programs and uninstall all references to Visual C++ 2017 Redistributable. After this, the SQL Server installation should proceed without errors.

Answer 4

Sorry, I got the same problem, I uninstall my Visual Studio 2017, but still, I have the same error "VS Shell installation has failed with exit code". Any other idea?

I would really appreciate if there is something else I can do

Answer 5

I just fixed this issue because of this thread. I uninstalled 2 references to Visual C++ 2017 Redistributable from Add/Remove Programs. I've tried a million things, but that finally worked!
 Thanks @IdleHands!

Answer 6

Excelente, fue lo que me funcionó, busque y busque y  lo  mejor fue esta respuesta. 

 uninstalled 2 references to Visual C++ 2017 Redistributable from Add/Remove Programs

Answer 7

Thanks! This helped me install SQL Server 2017 on my machine.

Answer 8

Perfect! As you described to us. SQL Express Setup succeeded! Big thank you! 

Answer 9

Perfect solution i have uninstalled both microsoft visual c++ Redistributable 2017 x86 and x64 after that every thing installed fine, and after installation i installed redistibutable again

Answer 10

I'm glad to see a work-around that works for everyone, but I hardly call it a solution.  SQL Server should just handle this, it is completely ridiculous to even need to uninstall VS 2017 C++ redist.  This is an embarrassing way to "fix" SQL installation, Microsoft.

Answer 11

We can just repair this, don't need to remove. It says that something was wrong on the installation of visual studio, very common with VS2017

Answer 12

Thank you.

this one worked perfect for me.

SQLSERVER 2017

Answer 13

Thanks ... i did the same thing as well and it worked. 

Answer 14

Just uninstalling Microsoft Visual C++ 2017 was enough for me.

Answer 15

Yes this fixed my installation issue. Thanks

---

Suresh

Answer 16

This helped me as well

Answer 17

I did some further investigation and it turns out (more specifically) the c++ dev environment was already installed. Microsoft Visual C++ (year) Redistributable. So yes, un-installing Visual Studio, then installing SQL server, then re-installing Visual Studio should do.

Answer 18

Yes, it worked! Thanks for sharing!

Answer 19

Thank you so much. uninstalling the two files you mentioned solved the installation issue

Answer 20

This worked for me. 

Answer 21

This worked for me.

Answer 22

repair solved our problem you don't need to uninstall.

Answer 23

I just replaced installations file of the c++ 2015 by new one with same names from 

https://visualstudio.microsoft.com/downloads/

(look in Other Tools and Frameworks/Microsoft Visual C++ Redistributable for Visual Studio 2017).

And it worked for me.



---

Wut?

Answer 24

Teige,

I am not happy with the proposed answer.  

WHY

VS 2017 takes about two hours to install and the same to uninstall.  SQL Server 2017 is ten to fifteen minutes if the only part of the installation is the Database Engine.  My question would be - are we sure it is VS2017 and not SSMS 2017?   

BETTER ANSWER

I like the answer that Luc Reid has given.   Perhaps the moderator can check the validity of the answer given by IdleHands and if it is valid, mark it as the proposed answer.  Removing the C++ Distributable for 2017 takes about a half a minute.  If it messes up Visual Studio 2017, there is something called "Repair".   IdleHands solution is short, quick, and more to the point, saves time.

VS 2017 C++ Distritributable Repair.  Okay well, it wound up a bit more complicated but still simpler than uninstalling and later, reinstalling VS 2017... explanation follows

Click the VS 2017 XXX in Control Panel and select "Change"  Add the "Desktop Development with C++" from the upper right corner (or repair it if you already installed it).  Its a 360 MB download and install and it doesn't take two hours.  I see others with similar solutions.  We aren't talking brain surgery with this fix.  It just takes a bit of planning to save you about a 1/2 day of installation time.

MAYBE AN ANALOGY HELPS

When I go out for a meal and have to wait for my food, the wait is worth it when the food is good.  But when the wait turns to hours and causes frustration, it no longer matters whether the meal is good or not.   Some things are just not worth the wait.

RESULTS

1) Uninstalled the 2017 C++ Distributable 2) Installed SQL 2017 (no problems) 3) Repaired Visual Studio 2017 - VOILA - the 2017 C++ Distributables are back.  YAY!

I expect that since my main goal was to get the Database Engine running, its likely the Anaconda, R, Python, etc installation may also fail compatibility as well.  Remains to be seen.  

Thanks Luc Reid.  You saved me half a day.   Terrific Answer.  Visual Studio has taken ages to install in the past - this VS version, 2017, is one where you turn it on and go do something else for the rest of the day.   It takes forever.

---

R, J

Answer 25

great solution   it makes sense and it works

Answer 26

thank you

Answer 27

I just replaced installations file of the c++ 2015 by new one with same names from 

https://visualstudio.microsoft.com/downloads/

(look in Other Tools and Frameworks/Microsoft Visual C++ Redistributable for Visual Studio 2017).

And it worked for me.



---

Wut?

thank you

Answer 28

Men, como vas, esta es la solucion mas efectiva, eliminar las dos instalaciones de VS 2017 C++ Redistributable y de una funciona, no se pongan a desisntalar todo el visual studio, no es necesario, excelente men.

Answer 29

I have the similar issue with SQL 2017 installation. However I was adding an instance into an existing SQL 2017 server, and I didn't found VC 2017 on it.

What interesting is I tried to install VC 2017 and then the installation succeeded. Attached the failed log here if anyone need:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052378
  Start time:                    2019-04-18 14:11:46
  End time:                      2019-04-18 14:18:23
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  DALYLAB-SQL
  Machine processor count:       4
  OS version:                    Microsoft Windows Server 2019 Datacenter (10.0.17763)
  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 2017      DALYLABSQL           MSSQL14.DALYLABSQL             Database Engine Services                 1033                 Enterprise Edition   14.0.1000.169   No         Yes       
  SQL Server 2017      DALYLABSQL           MSSQL14.DALYLABSQL             Full-Text and Semantic Extractions for Search 1033                 Enterprise Edition   14.0.1000.169   No         Yes       
  SQL Server 2017      DALYLABSQL           MSSQL14.DALYLABSQL             Data Quality Services                    1033                 Enterprise Edition   14.0.1000.169   No         Yes       
  SQL Server 2017      DALYLABSQL           MSAS14.DALYLABSQL              Analysis Services                        1033                 Enterprise Edition   14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Client Tools Connectivity                1033                                      14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Data Quality Client                      1033                 Enterprise Edition   14.0.1000.169   No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2017 
  ProductName:                   SQL Server 2017
  Type:                          RTM
  Version:                       14
  SPLevel:                       0
  Installation location:         D:\x64\setup\
  Installation edition:          Enterprise

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 NT Service\SQLAgent$DALYLABSP
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190418_141145\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    DALYLABSP
  INSTANCENAME:                  DALYLABSP
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 DALYLAB\s-sqlsrv
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DALYLAB\SQL_Admins
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$DALYLABSP
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            4
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190418_141145\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190418_141145\VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190418_141145\SystemConfigurationCheck_Report.htm