Visual Studio 2017 installer does not start after extraction

Question

visual studio 2017 community.exe will not start after extraction to the pace.

OS: windows 10 x64bit

Customization: Community Version

The temp boot tray log says:

The beginning of the magazine. Start time: 03/26/2012 1:14:54 AM VisualStudio Bootstrapper: 3/26/2017 1:14:54 AM: Optin current root path does not exist
VisualStudio Bootstrapper: 3/26/2017 1:14:55 AM: command line arguments =

and dd_vs_community_decompression_log says
[3/26/2017, 11:17:47] === Logging started: 2017/03/26 11:17:47 ===
[3/26/2017, 11:17:47] Executable file: C: \ Users \ Sameera \ Downloads \ Programs \ vs_community.exe v15.0.26228.0
[3/26/2017, 11:17:47] --- logging level: standard ---
[3/26/2017, 11:17:47] The directory for 'file:' C: \ Users \ Sameera \ AppData \ Local \ Temp \ 4ceac4b7b9cd9fdf2489526c66 \ 'was selected to extract the files
[3/26/2017, 11:17:48] Extracting files to: C: \ Users \ Sameera \ AppData \ Local \ Temp \ 4ceac4b7b9cd9fdf2489526c66 \
[3/26/2017, 11:17:48] Mining took 360 milliseconds
[3/26/2017, 11:17:48] Executing the extracted package: 'vs_bootstrapper_d15 \ vs_setup_bootstrapper.exe' with the command line ''
[3/26/2017, 11:18:10] Full execution of the Box with the result code: 0x0
[3/26/2017, 11:18:10] An extracted application was launched with the result code: 0xc000000d
[3/26/2017, 11:18:10] === Registration is stopped: 2017/03/26 11:18:10 ===

cannot find the right solution.

Answer 1

I was able to solve my problem after 4 days of troubleshooting with 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 start. Then, making sure we saved the OS restore point, we issued the / resetRepository command. After that, the VS 2017 Pro installer was able to run without errors.

EDIT: adding the exact steps and code examples below:

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: from a command prompt with administrator privileges or elevated privileges, run the following command: winmgmt / resetRepository

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

Step 7: restart the computer.

Hope this helps anyone who has a problem installing Visual Studio 2017.

Answer 2

I also had this problem. Answer SHClark did not work for me. I found out what caused the problem on my computer: Mirekusoft Install Monitor. I disabled both services and solved this problem. (I suppose this is not a very likely program for someone to work, but could this be a problem for installing monitors in general?)

I also heard from someone on the Visual Studio community forum that RivaTunerStatistics (used for games) can also cause this problem.

Answer 3

One of my colleagues ran into 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 figure it out. The problem is somehow explained there and is related to the NODE_OPTIONS variable . If you have this variable, delete it, and then restart the computer. This solved his problem.

Configuration: Widows 10, Visual Studio 2017 Enterprise.

I hope this helps you

Answer 4

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

Answer 5

I had the same (or similar) problem. I could not update VS2017, either from within the program, or tried to run the installer. At https://docs.microsoft.com/en-us/visualstudio/install/troubleshooting-installation-issues, there were instructions that resolved the issue. For me, removing the "Installer" directory and trying to install again resolved the issue.

Answer 6

Try deleting this folder C:\Program Files (x86)\Microsoft Visual Studio\ . Restart the installation.

Answer 7

This is the same answer as in visual studio 2017 install break question : it does not start unless you notice another question.

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 8

I had this problem all day and MS support did not help. To solve my problem, I updated the video driver to the latest version (I intentionally used the old driver, since the new versions do not support my monitor resolution). The visual studio installer must use GUI technology not supported by my old card, and simply fails before loading the installer GUI. The same problem arose for older, standalone installers for older versions like VS2013.

Answer 9

I had the same problem (with the Dell lab desktop) and SHClark did not work for me. Here is what I did:

I used the command line to create a local cache of files needed for an offline installation

[ctrl] [shift] [enter] to run the cmd command as administrator

1) scored

 d:\vs_community.exe --layout h:\vs2017layout --add Microsoft.VisualStudio.Workload.NativeDesktop --includeRecommended --lang en-US 

after the download is complete in h:\vs2017layout ,

2) opened h:\vs2017layout\vs_setup.exe finally, opening it after unpacking, but ran into this error:

 The name of the file cannot be resolved by the system 

so I created a link to the c:\ProgramData\Microsoft\Visual Studio folder using the following command on a Windows command prompt:

 mklink /D "C:\ProgramData\Microsoft\VisualStudio" "g:\ProgramData\Microsoft\VisualStudio" 

It worked after that. Not sure if the second error was related to the first. Hope this helps.

Answer 10

I had the same problem, correction: go to reigonal settings from the control panel, then select (or select reselect) the current language for programs that do not support Unicode on the administrative tab. than try again.

Answer 11

I have the same problem. Here is my solution:

1. right-click in relation to the installer, unzip it using WinRAR.
2. Go to the extracted folder.
3. run: vs_setup_bootstrapper.exe

It worked for me :)

Answer 12

I had the same problem, and the problem was that my username contained both a space and a non-ascii character (Olkay Ertash). I moved the installer to my root folder and it worked. This is probably the reason why @ oğuzhan-türk's solution also works.

Answer 13

If you have Win8, you need to update the system to version 8.1. and restart your computer.

Answer 14

I had this problem. It turned out that the disk had an old failed installation. I had to go to Control Panel-> Add or Remove Programs and remove the Visual Studio Install Tool. After that, the installer worked fine.

Answer 15

Faced the same issue with Visual Studio 2019, but I think the version here doesn't matter. This topic helped me: https://developercommunity.visualstudio.com/content/problem/326811/vs-community-installer-not-running-working.html . The reason was in corrupted .NET files.

Applied Actions:

• uninstalled all applications with the name "Microsoft.NET" using https://support.microsoft.com/en-us/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed
• downloaded and installed the latest version of the .NET Framework Runtime (not the .NET Core Runtime) from https://dotnet.microsoft.com/download , in my case it was version 4.8
• restarted the computer

It helps me.

Answer 16

I didn’t succeed here, however, I was able to detect that an error occurred in the main.js file due to which he could not find the temporary folder. so I looked at the environment variables and indeed for my current user TEMP was not set accordingly. empty. I copied the temporary default value (% SystemRoot% \ TEMP) for all users to the TEMP variable of the current user, after which everything worked