Windows-build-tools: Not recognizing VS Build Tools 2017 and hanging on "still waiting on installer log file"

Created on 5 May 2021  路  6Comments  路  Source: felixrieseberg/windows-build-tools

windows-build-tool does not seem to be properly recognizing VS Build Tools 2017 whether I manually install it or let the tool do its thing. I believe this is because of the log file name change. I think this could be resolved with the current PR #248. When looking at my %temp% directory, I also see files such as dd_installer_20210504174139.log or dd_installer_elevated_20210504171150.logbut notdd_client`.

OS: Windows 10 Pro - Version 20H2 Build 19042.964
Node: v16.1.0
windows-build-tools: v5.2.2 (latest according to npm)
Command: npm install -g windows-build-tools

Most helpful comment

windows-build-tool does not seem to be properly recognizing VS Build Tools 2017 whether I manually install it or let the tool do its thing. I believe this is because of the log file name change. I think this could be resolved with the current PR #248. When looking at my %temp% directory, I also see files such as dd_installer_20210504174139.log or dd_installer_elevated_20210504171150.logbut notdd_client`.

OS: Windows 10 Pro - Version 20H2 Build 19042.964
Node: v16.1.0
windows-build-tools: v5.2.2 (latest according to npm)
Command: npm install -g windows-build-tools

i use npm install --global --production windows-build-tools --vs2015 success
OS: windows 20H2
Node: v12.14.1

All 6 comments

Perhaps if anything there should be a fallback check to the previous dd_client_#####.log file just in case. I've seen other issues opened up regarding this same issue. Personally, I attempted the listed solutions to no avail. I would try this PR but I can't get it to install locally.

I have the same problems.
node version = 14.16.1

image

I have the same problem too,
node version:12.0.0
image

I do too with node v12.19.0 and also with node v14.16.1

windows-build-tool does not seem to be properly recognizing VS Build Tools 2017 whether I manually install it or let the tool do its thing. I believe this is because of the log file name change. I think this could be resolved with the current PR #248. When looking at my %temp% directory, I also see files such as dd_installer_20210504174139.log or dd_installer_elevated_20210504171150.logbut notdd_client`.

OS: Windows 10 Pro - Version 20H2 Build 19042.964
Node: v16.1.0
windows-build-tools: v5.2.2 (latest according to npm)
Command: npm install -g windows-build-tools

i use npm install --global --production windows-build-tools --vs2015 success
OS: windows 20H2
Node: v12.14.1

i use npm install --global --production windows-build-tools --vs2015 success
OS: windows 20H2
Node: v12.14.1

it worked!!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kimbaudi picture kimbaudi  路  3Comments

bwhybrow23 picture bwhybrow23  路  3Comments

kittaakos picture kittaakos  路  8Comments

Archer456 picture Archer456  路  5Comments

anaisbetts picture anaisbetts  路  4Comments