lukesampson
commented
10 years ago Sorry to hear that. Are you sure powershell froze? Go is a big zip file with lots of small files inside so it takes a long time to extract—it takes about 54 seconds to extract on my machine with Scoop, and about 52 seconds to extract through Windows Explorer (Scoop is doing some extra work though).
After you've kill powershell or otherwise aborted the installation, if you run scoop status it should show that installation failed for Go. But before you can try installing it again, you need to clear up the files from the failed install with scoop uninstall go.
If at this point you get the message "couldn't remove ~\appdata\local\scoop\apps\go\1.1.2: it may be in use", you can run rm ~\appdata\local\scoop\apps\go\1.1.2 manually to try to see what's wrong. If something has a lock on a file (possible if you've killed a process) you can use unlocker (available in the extras bucket if you run scoop bucket add extras; scoop install unlocker). Or, just restart—depending on whether or not you can be bothered working out the unlocker command :)
Now that Go's uninstalled, and assuming you'd like to try installing it again, you should be able to run scoop install go again. You won't need to re-download—Scoop will have cached the download.
If it's still not working, please let me know. Hopefully we can get this working for you.
danishabdullah
Whuichenggong
when I issue "scoop install go" It goes to googlecode, downloads the zip but crashes while extracting it. The powershell becomes unresponsive and has to be manually closed through the tast manager. When I open another powershell, "Go" isn't installed on the system, however scoop thinks that it has already been installed.