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.
I want to the %TEMP% folder and looked at dd_setup_2017??.log and saw that it last executed:
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:
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.