- Home /
- Visual Studio /
Get help from our community supported forum
Report an issue from
within Visual Studio*
This allows diagnostic information to be included in your report
1
Open Visual Studio
2
Select Report a Problem
3
Type and Submit
*Available only on Visual Studio 2017 Preview 3 and newer releases
Components fail to install because of spaces in user names
Some payloads fail to install because of white-space in user name (namely at least GitV2 and .NET Core SDK). EXE file is properly enclosed in double-quotes, while file path to log is not (\log C:\Users\John Doe\AppData\Local\Temp...)
Thank you for submitting feedback. In order to efficiently investigate and reproduce this issue, could you please give us a setup log file so that we can conduct further research?
You are able to get the files with the following steps:
1) Download collect.exe from the link http://aka.ms/vscollect .
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.zip.
4) Upload your vslogs.zip by choosing insert file tag on add comment field then submit after signing in.
You can get more details about how to get the log files here: http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx
We look forward to hearing from you with this information.
This was previously reported during Preview and RC. How is this not fixed by RTM? See https://developercommunity.visualstudio.com/content/problem/6667/vs2017rc-installation-failed-because-of-vcredist-x.html and https://developercommunity.visualstudio.com/content/problem/6808/visual-studio-2017-rc-community-professional-fails.html
133 People are following this
