-
Notifications
You must be signed in to change notification settings - Fork 907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At first, a dependency failure and after working around it, apparently no installation #322
Comments
Apologies you had a bad first experience. I do want to mention that both of these appear to be package issues and not issues with core chocolatey. If you want to follow up on the win sdk on the package page, that would be great. I'm the maintainer of 7zip, so I can help you with that. |
You mean on https://chocolatey.org/packages/windows-sdk-6.1? Sure, why not. I'll post a message. |
Done. I hope I posted enough information to get the troubleshooting process started. |
Awesome. :) |
@epicbugs I've followed up with ferventcoder/chocolatey-packages#82 for 7zip |
FWIW I get this while trying to update
this in Choco 05/31, btw. |
I discovered Chocolatey today and I must say, was quite excited to try it out but when I finally ran "choco install windows-sdk-6.1" things turned ugly.
Although puzzled at first I then had an idea. I went to "Programs and Features" and uninstalled 7zip already present from previous days.
After that, "choco install windows-sdk-6.1" at least from the outside succeeded ("The install of windows-sdk-6.1 was successful.") but I have no idea where exactly was it installed.
Microsoft docs state that "To open the tools documentation, point to All Programs, point to Microsoft Windows SDK, point to Tools, and then click Tools Reference" but there isn't even a "Microsoft Windows SDK" item in the Start Menu. Nor is there currently any reference to Windows SDK or its standard tools neither in "Program Files" nor in "Program Files (x86)" of the machine where I ran the command.
Is this normal and expected behavior?
The text was updated successfully, but these errors were encountered: