When running pc-nrfconnect-programmer on a fresh installation of Windows, the error "Failed to get the library versions: Error: Failed with exit code 1" is shown, and the program doesn't start. - SOLVED - posted here for information

[Marcus Clyne]

Installing the latest ms visual c++ redistributable resolves the issue.  It looks like all the dependencies aren't installed by the installer.

[Karl Ylvisaker]

Hello,

Do I understand it correctly that you had a fresh windows installation (which version?), in which you downloaded the nRF Connect for Desktop application, and then installed the Programmer application, and when you went to launch this it failed until you manually installed the ms c++ redistributable?
Did you also install the nRF Connect SDK and Visual studio code extensions before you tried to launch the programmer?

Best regards,
Karl

[Marcus Clyne]

Hi,

This was for a "programming only" system for a customer, so no SDK or VS Code Extensions:

Tried both a win11 install (fresh, cloud download from MS, win11 pro ) and also a win10 install (same, win 10 pro fresh).
Installed the OS and then allowing it to self update to a point where no further MS updates were found.
Downloaded NRF connect from Nordic
Completed the install
Chose install the programmer (noticed vc++ install during this install, segger etc)
After completion, programmer fails to start every single time - (view log results are attached)

Finally discovered that downloading the ms vc++ 15/17/19/22 update
Located here learn.microsoft.com/.../latest-supported-vc-redist
Package was aka.ms/.../vc_redist.x64.exe

That it fixed every one of the installations that had been attempted (three different computers)

[Karl Ylvisaker]

Hello,

Thank you for the update, and for the clarifications - I have created an internal report on this to our nRF Connect for Desktop developers, so that they may take a closer look.

Thank you for bringing this to our attention! :) 

Best regards,
Karl

[Karl Ylvisaker]

Hello again,

I was just informed by the developers that a fix has been created for this, and that a new release with the fix is on the way! :) 

Best regards,
Karl