{"action":"created","issue":{"url":"https://api.github.com/repos/lukesampson/scoop/issues/774","repository_url":"https://api.github.com/repos/lukesampson/scoop","labels_url":"https://api.github.com/repos/lukesampson/scoop/issues/774/labels{/name}","comments_url":"https://api.github.com/repos/lukesampson/scoop/issues/774/comments","events_url":"https://api.github.com/repos/lukesampson/scoop/issues/774/events","html_url":"https://github.com/lukesampson/scoop/issues/774","id":145754252,"number":774,"title":"Scoop skipping steps, not raising an error","user":{"login":"damnhandy","id":415094,"avatar_url":"https://avatars.githubusercontent.com/u/415094?v=3","gravatar_id":"","url":"https://api.github.com/users/damnhandy","html_url":"https://github.com/damnhandy","followers_url":"https://api.github.com/users/damnhandy/followers","following_url":"https://api.github.com/users/damnhandy/following{/other_user}","gists_url":"https://api.github.com/users/damnhandy/gists{/gist_id}","starred_url":"https://api.github.com/users/damnhandy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/damnhandy/subscriptions","organizations_url":"https://api.github.com/users/damnhandy/orgs","repos_url":"https://api.github.com/users/damnhandy/repos","events_url":"https://api.github.com/users/damnhandy/events{/privacy}","received_events_url":"https://api.github.com/users/damnhandy/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-04-04T17:45:06Z","updated_at":"2016-04-05T22:47:32Z","closed_at":"2016-04-05T22:47:32Z","body":"We have a version of Scoop running internally for a small work group. The only modifications we've made are changing the install script and modifying the manifests to point to files hosted in our environment. Other than that, it is stock Scoop code. \r\n\r\nFor the most part, everything works. However, for a small percentage of users, some manifests are not working and it appears scoop is skipping steps but continuing as it the step was successful. For example, here is what it the output looks like when someone is installing git:\r\n\r\n    PS C:\\> scoop install git\r\n    installing git (2.7.4.windows.1)\r\n    creating shim for git\r\n    can't shim cmd\\git.exe: file doesn't exist\r\n\r\nIn a successful scenario, you see the URL being downloaded, checking the hash, and extracting the archive. In the case of git, it's also skipping the 7zip download as well. I should also note that this is a clean install of scoop and nothing is cached here. The execution policy appears to be working as the installation of scoop works without issue. In my case, the Git manifest also has a dependency on some internal certificates, and those download and install without issue. \r\n\r\nAs far as software and OS: we're running Windows 7 Enterprise and PowerShell 4.0. Any insights would be appreciated. "},"comment":{"url":"https://api.github.com/repos/lukesampson/scoop/issues/comments/206023085","html_url":"https://github.com/lukesampson/scoop/issues/774#issuecomment-206023085","issue_url":"https://api.github.com/repos/lukesampson/scoop/issues/774","id":206023085,"user":{"login":"damnhandy","id":415094,"avatar_url":"https://avatars.githubusercontent.com/u/415094?v=3","gravatar_id":"","url":"https://api.github.com/users/damnhandy","html_url":"https://github.com/damnhandy","followers_url":"https://api.github.com/users/damnhandy/followers","following_url":"https://api.github.com/users/damnhandy/following{/other_user}","gists_url":"https://api.github.com/users/damnhandy/gists{/gist_id}","starred_url":"https://api.github.com/users/damnhandy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/damnhandy/subscriptions","organizations_url":"https://api.github.com/users/damnhandy/orgs","repos_url":"https://api.github.com/users/damnhandy/repos","events_url":"https://api.github.com/users/damnhandy/events{/privacy}","received_events_url":"https://api.github.com/users/damnhandy/received_events","type":"User","site_admin":false},"created_at":"2016-04-05T22:47:32Z","updated_at":"2016-04-05T22:47:32Z","body":"Yep, we just figured this out while watching one the developers consciously select the 32-bit PowerShell (x86) console. All our machines are 64-bit, so we didn't think to bother to 32-bit. I didn't even consider that folks could select a 32-bit console. Now I know!\r\n\r\nI'll take your advice and remove the architecture options. Thanks again! I'll close this out then."}}