I ran into this problem only yesterday and did not find the exact solution, but there were some workarounds that did this work. I encountered problems installing the following components using vs_community.exe: - - SqlDom_amd64 - TSqlLanguageService - CT / AzureMobileServicesSdkV2.0
- Win10_UniversalCRTSDK - Library Headers and Sources - WcfDataServices - Win81_SDK - SQLSysClrTypes - SQLSysClrTypes_amd64 - SharedManagementObjects_x86 - SharedManagementObjects_amd64
TRICK:
- Since the choice of the place where this package did not help, I pressed the SKIP PACKAGE button for all the packages listed above. - And then manually run setup / msi-installers for the packages listed above. - Some of them were successfully installed as "SqlDom_amd64" and several others - But, to my bad luck, for some it was somehow a failure during extraction, so I thought that msi-installer could really be damaged for some. - So, for the left, I have to select "Repair" -option of "vs_community.exe" and select "Download packages from the Internet." - Finally, the setup was successful, and everything works fine.
I understand its workaround, not the solution, but it serves the purpose of limiting that some packages require an Internet connection.
source share