Visual Studio 2017 set the gap: it does not start

Question

• I am using administrator permission to install vs_enterprise.exe. But the installation package does not work at all.

• OS: win10 professional

• The installation log in appdata / local / temp / is as follows:

dd_bootstrapper_20170313103210:

The beginning of the magazine. Start time: 03/13/2017 10:32:10
VisualStudio Bootstrapper: 03/13/2017 10:32:10: Current Optin root path does not exist
VisualStudio Bootstrapper: 03/13/2017 10:32:11: Commandline arguments =

dd_vs_enterprise_decompression_log.txt

[3/13/2017, 10: 32: 4] === Logging started: 2017/03/13 10:32:04 ===
[3/13/2017, 10:32: 4] Executable file: D: \ vs2017 \ vs_enterprise.exe v15.0.26206.0
[3/13/2017, 10: 32: 4] --- logging level: standard ---
[3/13/2017, 10: 32: 4] The directory 'C: \ Users \ gary \ AppData \ Local \ Temp \ b012f31d56525c685e \' was selected to extract the files
[3/13/2017, 10: 32: 4] Extracting files to: C: \ Users \ gary \ AppData \ Local \ Temp \ b012f31d56525c685e \
[3/13/2017, 10: 32: 5] Mining amounted to 484 milliseconds
[3/13/2017, 10: 32: 5] Executing the extracted package: 'vs_bootstrapper_d15 \ vs_setup_bootstrapper.exe' with the command line ''
[3/13/2017, 10:32:11] Full execution of the box with the result code: 0x0
[3/13/2017, 10:32:11] The extracted application was launched output with the result code: 0xc000000d
[3/13/2017, 10:32:11] === Registration is stopped: 2017/03/13 10:32:11 ===

Thanks ~

Answer 1

I had this exact problem, thought it was a service. The installer will start working if I run it as soon as Windows boots up; if I was waiting, it is not.

It turns out that this is the RivaTunerStatistics server, which was launched for my game overlays. He closed it, and voila took up again. Tested several times to confirm.

Answer 2

I had a similar problem, my Visual Studio Professional 2017 installer closed before the installation began. I solve the problem by following these steps:

1 - Open an invitation (CMD) with administrator privileges

2. Check if there is a file "InstallCleanup.exe" inside the folder "% programfiles (x86)% \ Microsoft Visual Studio \ Installer \ resources \ app \ layout \". If the file exists, go to step 7.

3 - Manually delete the folder "% programfiles (x86)% \ Microsoft Visual Studio \ Installer"

4 - Restart the recently loaded visual studio installer

5 - enable the first step of installing the installer

6 - After the installer appears and you see the options for the workload (desktop, etc.), close it

7 - inside the CMD, navigate to the folder "% programfiles (x86)% \ Microsoft Visual Studio \ Installer \ resources \ app \ layout \"

3 - run this command: "InstallCleanup.exe -full"

4 - what is he. Just run the installer again.

It worked for me.

Answer 3

I had the same problem on two different PCs (both win10), and the only thing that worked for me was reinstalling Windows and reinstalling the visual studio installer. I know this is not a good, quick or easy solution, but it works.

Answer 4

I had a similar problem with the VS 2017 installer (similar error message) and I was finally able to solve my problem after 4 days of troubleshooting using Microsoft Support. I am developing on a Dell laptop, and a technician believes that one of the Dell services is causing problems with the winmgmt service.

The following is a command that did not run during troubleshooting. After making sure that we saved the OS restore point, we issued the winmgmt / resetRepository command. After that, the VS 2017 Pro installer was able to run without errors.

Here are the exact steps taken by Microsoft Support:

Step 1. Create a Windows system restore point.

Step 2. At the command prompt with administrator rights or elevated privileges, run the following command: net stop winmgmt

Step 3. Open Windows Explorer and find the path to the folder C: \ windows \ system32 \ WBEM \ and rename the repository folder to another location, for example, to RepositoryOLD (right-click and select "Rename folder").

Step 4: restart the computer.

Step 5: from a command prompt with administrator privileges or elevated privileges, run the following command: net stop winmgmt

C:\>net stop winmgmt The Windows Management Instrumentation service is stopping. The Windows Management Instrumentation service could not be stopped. 

Step 6: At a command prompt with administrator rights or elevated privileges, complete the following steps and complete the following steps: winmgmt / resetRepository

 C:\>winmgmt /resetRepository WMI repository has been reset 

Step 7: restart the computer.

Hope this helps someone else.

Answer 5

Having tried all the suggested answers here (using VS 2017), I followed the instructions from the official Microsoft documents that worked for me. In short:

• Close the Visual Studio installer.
• Delete the Visual Studio installer directory. Typically, the directory is C:\Program Files (x86)\Microsoft Visual Studio\Installer .
• Launch the Visual Studio Installer bootloader. You can find the bootloader in the “Download” folder with the file name that follows the vs_[Visual Studio edition]__*.exe template. If you do not find this application, you can download the bootloader by going to the Visual Studio download page and clicking Download for your Visual Studio edition. Run the executable in the reset metadata of the installation.
• Try installing or updating Visual Studio again. If the installer continues to fail, continue to the next step.

Answer 6

I had the same problem, but it was resolved using @Ben Logan's answer (Closing RivaTunerStatistics).

Answer 7

Copy vs_enterprise.exe to USB and run. This will work.

Answer 8

try running this file using the console example: c: /vs_community__556869458.1519050247.exe

Answer 9

For those who still have this problem:

One of my employees faced the same problem. We spent 4 hours searching for solutions, removing VS and other software, which, in our opinion, could be the culprit.

In the end, THIS LINK helped us understand this. The problem is somehow explained there and is related to the NODE_OPTIONS variable . If this variable is set, delete it and restart the computer. This solved his problem.

Configuration: Widows 10, Visual Studio 2017 Enterprise.

I hope this helps you