node-pre-gyp install fallback-to-build

npm install command for certain packages (like fabric-client) is giving me the following error:

npm install --global --production fabric-client

npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN lifecycle The node binary used for scripts is C:\Program Files\nodejs\node.exe but npm is using C:\Users\838082\AppData\Roaming\npm\node_modules\node\bin\node.exe itself. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with.

grpc@1.17.0 install C:\Users\838082\AppData\Roaming\npm\node_modules\fabric-client\node_modules\grpc
node-pre-gyp install --fallback-to-build --library=static_library

node-pre-gyp WARN Using request for node-pre-gyp https download

[grpc] Success: "C:\Users\838082\AppData\Roaming\npm\node_modules\fabric-client\node_modules\grpc\src\node\extension_binary\node-v57-win32-x64-unknown\grpc_node.node" is installed via remote

pkcs11js@1.0.18 install C:\Users\838082\AppData\Roaming\npm\node_modules\fabric-client\node_modules\pkcs11js
node-gyp rebuild

C:\Users\838082\AppData\Roaming\npm\node_modules\fabric-client\node_modules\pkcs11js>if not defined npm_config_node_gyp (node "C:\Users\838082\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Users\838082\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Users\838082\AppData\Roaming\npm\node_modules\fabric-client\node_modules\pkcs11js\build\pkcs11.vcxproj(21,3): error MSB4019: The imported project "C:\Microsoft.Cpp.
Default.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
gyp ERR! build error
gyp ERR! stack Error: msbuild failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Users\838082\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\Users\838082\AppData\Roaming\npm\node_modules\node\bin\node.exe" "C:\Users\838082\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\838082\AppData\Roaming\npm\node_modules\fabric-client\node_modules\pkcs11js
gyp ERR! node -v v8.11.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! pkcs11js@1.0.18 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the pkcs11js@1.0.18 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\838082\AppData\Roaming\npm-cache_logs\2019-06-13T12_27_19_206Z-debug.log

However, when I run node-pre-gyp configure, I am getting the following output:

C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp>node-pre-gyp configure
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using node-pre-gyp@0.13.0
node-pre-gyp info using node@8.11.0 | win32 | x64
node-pre-gyp ERR! UNCAUGHT EXCEPTION
node-pre-gyp ERR! stack Error: node-pre-gyp package.json is not node-pre-gyp ready:
node-pre-gyp ERR! stack package.json must declare these properties:
node-pre-gyp ERR! stack binary.module_name
node-pre-gyp ERR! stack binary.module_path
node-pre-gyp ERR! stack binary.host
node-pre-gyp ERR! stack at validate_config (C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\lib\util\versioning.js:220:15)
node-pre-gyp ERR! stack at Object.module.exports.evaluate (C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\lib\util\versioning.js:279:5)
node-pre-gyp ERR! stack at handle_gyp_opts (C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\lib\util\handle_gyp_opts.js:60:27)
node-pre-gyp ERR! stack at configure (C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\lib\configure.js:12:5)
node-pre-gyp ERR! stack at Object.self.commands.(anonymous function) [as configure] (C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\lib\node-pre-gyp.js:52:37)
node-pre-gyp ERR! stack at run (C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\bin\node-pre-gyp:82:30)
node-pre-gyp ERR! stack at Object. (C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\bin\node-pre-gyp:134:1)
node-pre-gyp ERR! stack at Module._compile (module.js:652:30)
node-pre-gyp ERR! stack at Object.Module._extensions..js (module.js:663:10)
node-pre-gyp ERR! stack at Module.load (module.js:565:32)
node-pre-gyp ERR! System Windows_NT 10.0.14393
node-pre-gyp ERR! command "C:\Users\838082\AppData\Roaming\npm\node_modules\node\bin\node.exe" "C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp\bin\node-pre-gyp" "configure"
node-pre-gyp ERR! cwd C:\Users\838082\AppData\Roaming\npm\node_modules\node-pre-gyp
node-pre-gyp ERR! node -v v8.11.0
node-pre-gyp ERR! node-pre-gyp -v v0.13.0
node-pre-gyp ERR! This is a bug in node-pre-gyp.
node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
node-pre-gyp ERR! https://github.com/mapbox/node-pre-gyp/issues

I have installed the latest versions of windows-build-tools and node-pre-gyp.
Output of npm list -g --depth 0

+-- grpc@1.19.0
+-- list@2.0.18
+-- node@8.11.0
+-- node-gyp@4.0.0
+-- node-pre-gyp@0.13.0
+-- npm@5.6.0
+-- socket.io@2.2.0
+-- typescript@3.3.4000
`-- windows-build-tools@5.1.0

Is anyone else experiencing anything like this? I am using Windows Server 2016 on a VM.

Start by reproducing the Windows install and standalone node-pre-gyp configure commands from the report. Read lib/util/versioning.js, lib/util/handle_gyp_opts.js, and lib/configure.js at the stack-trace locations, then determine the intended behavior for the missing binary fields and the node-gyp fallback. Done requires a confirmed diagnosis and a verified resolution for the reported install path.