Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Resolve issue with DISM "missing" or with the 32-bit DISM being called on a 64-bit system #393
Recently while creating a chocolatey package, I ran into an issue where trying to install a windows feature would fail on my 64-bit windows operating system with a message saying that I could not use the 32-bit version of DISM to manage features. The reason this was happening was because of the 32-bit redirection that occurs on a 64-bit operating system. I also found an issue (#378) that seems to be related because either the DISM was not in the path or more likely it was due to the lack of a new line between the closing curly brace and the "cmd" and resulted in "none" of the code being executed in the elevated shell.
After reading the "contributing" document, I implemented the fix in a branch and sent a new pull request.
Awesome! Thank you for doing that. This looks pretty clean and easy to pull
On Thursday, December 19, 2013, Julian Easterling wrote:
referenced this pull request
Dec 19, 2013
Hi, first just to say thanks for finding this: I was trying to get 'windowsfeatures' to work properly with puppet, and it turns out I was running into this exact issue.
Anyway, this is just a note that 'dism' is also called from Chocolatey.List if the source is 'windowsfeatures', so the same fix needs to be applied there.
The "sysnative" special alias is not a feature of "32-bit shells" (or cmd.exe in particular), rather it is provided by the WOW64 layer and available to all 32-bit applications running on 64-bit Windows, PowerShell included.