3 ms·
Fyi... I just tried the offline download and after 34 minutes, it is hung and won't finish. The command line I used: vs_Enterprise.exe --layout z:\VS2017_RT
by jasode 10y ago
Fyi... I just tried the offline download and after 34 minutes, it is hung and won't finish.
The command line I used:
vs_Enterprise.exe --layout z:\VS2017_RTM --lang en-US
last lines of the console:
...
Download of 'https://go.microsoft.com/fwlink/?linkid=823168' succeeded using engine 'WebClient'
Download of 'https://go.microsoft.com/fwlink/?linkid=833503' succeeded using engine 'WebClient'
Download of 'https://go.microsoft.com/fwlink/?linkid=833501' succeeded using engine 'WebClient'
Download of 'https://download.microsoft.com/download/B/5/5/B55373E5-8948-41DF-B1D5-F60896104294/WinSdkInstall.ps1' succeeded using engine 'WebClient'
Download of 'https://go.microsoft.com/fwlink/?linkid=838828' succeeded using engine 'WebClient'
stats of the target directory so far:
2,631 Files, 1,005 Folders total 14,444,652,261 bytes
I previously got the offline download to complete with version RC1 in November 2016 but RC2 in Janurary 2017 always hung in the same spot. I didn't pursue RC2 troubleshooting since RTM would be available a month later and I hoped whatever problem with RC2 would be resolved in RTM.
Well, it still doesn't work. Please let the MS team know that there's something about the offline download ("--layout" option) that's fragile and prone to hang. I don't believe it's an issue with overloaded servers because when I tried multiple times with RC2, it always hung on the exact same file whether it was morning/night/ weekday/weekend. I suspect the current problem is similar.
I took a screenshot of the hung process for RC2 in January and it seems to hang right after downloading WinSdkInstall.ps1 which is similar to RTM behavior:
RC2 hung in January: http://imgur.com/a/uwfoj http://imgur.com/a/uwfoj
RTM hung in March (today): http://imgur.com/a/QxqC3 http://imgur.com/a/QxqC3
- timsneath 10y agoThanks the report, @jasode. I'm bringing in a few folk to take a look.
- timsneath 10y agoUnfortunately the printed logs only show what has been downloaded, not what is currently downloading. I know - that's not very helpful in this case. It would be really useful to see the more detailed logs, which are stored in the %TEMP% folder. It might be that it's not hung at all - if it's a really large file that's being downloaded. If you're willing to mail me at tims@microsoft.com, I'd be happy to work with you to grab your detailed logs and investigate further.
- jasode 10y agoThanks for your reply. It helped me get past the problem. I want to the %TEMP% folder and looked at dd_setup_2017??.log and saw that it last executed: Running: C:\Windows\SysWOW64\\WindowsPowerShell\v1.0\powershell.exe with parameters: -NoLogo -NoProfile -ExecutionPolicy Unrestricted -InputFormat None -Command ... I then went to Task Manager and noticed the powershell.exe command hanging with 0% cpu consumed. I remembered that sometimes those commands hang on network paths so I ran "vs_Enterprise.exe --layout" again to local "C:\VS2017_RTM" instead of mapped "Z:\VS2017_RTM". It then completed without hanging. The completed target folder has: 1,901 Files, 765 Folders total 22,171,951,890 bytes It seems strange that the successful completion results in less files & folders but 8 more gigabytes. I assume some intermediate scripts cleaned up some files.
- timsneath 10y agoGreat - so glad that you're up and running. Thanks for the update. We'll take this back and see if we can repro this in-house.