Balena-cli install ERR

I’ve been using balena CLI for a while, however yesterday it just died on me and my shell refused to recognize the command. So I thought that it would be best to reinstall everything. I’ve followed the instructions in the balena-cli github project.

I’ve installed windows-build-tools@4.0.0
I’ve tried installing balena, using npm insatll balena-cli -g --production --unsafe-perm both in an administrator shell as well as a normal user one. Each time there are several gyp build errors, however I’m not quite sure why that happens, as if I understood correctly, installing windows-build-tools would fix that.

embedder : error : Could not open file 'C:\Program Files (x86)\Windows Kits\10\redist\wdf\x64\WdfCoInstaller01011.dll'. [C:\Users\confusetador\AppData\Roaming\npm\node_modules\balena-cli\node_modules\winusb-driver-generator\build\libwdi.vcxproj]
    EMBED  C:\Program Files (x86)\Windows Kits\10\redist\wdf\x64\WdfCoInstaller01011.dll
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:189:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\confusetador\AppData\Roaming\npm\node_modules\balena-cli\node_modules\winusb-driver-generator
gyp ERR! node -v v10.15.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

I’m on a Windows 10 machine.

Hello @confusetador,

For windows we highly suggest you to run the standalone version, which you can download from here.

All you need to do is to unzip the files to your computer, for example C:\balena and fun the balena.exe from there.

Let me know if you still have issues with it.

Thanks for the response, the standalone version works nicely. I’ve actually gotten it to work through npm but then it died on me so the standalone version works just fine now.