5 ms·
Unfortunately 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
by timsneath 10y ago
Unfortunately 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.