@thor I spent some time on the build issue. Disclaimer: I am not an expert on 'choco' and it's package management. I see the build breaking when there is an existing VS instal and that probably happens because of the side-by-side installation of Windows 10 SDK (that OSQuery script does) along with whatever was already on the system. This causes the SDK paths etc to get messed up as it adds a version number
Those paths then have to be manually fixed.
The current bat file installs all the dependent packages using choco. So if there was an out-of-band (i.e. not using choco) installation of SDK, the script won't catch it and end up doing a side-by-side install and we land in mess. One option is to make the script smart enough to detect the existing SDK installer, not only in the choco pakage list, but also from the local system. I realize its not so easy as to just comment/add a few lines and get done with it. Anyways, will continue spending some more time on it. Thought I will share whatever I found so far.
09/25/2017, 8:17 PM
I also faced similar issue while doing provisioning...since i already had vs2015 installed. i got around it by commenting out the code for installing vs2015community thereafter. It would definitely be cleaner to avoid such issues.