Unable to use nrfconnect-setup-3.11.0-ia32.exe due to TrojWare.Win32.Injector.ALGW@51nb03

VirusTotal reports nrfconnect-setup-3.11.0-ia32.exe and nrfconnect-setup-3.11.1-ia32.exe as having TrojWare.Win32.Injector.ALGW@51nb03 and our IT policy prevents us from using these files.

We're just beginning a new development with nRF5340 DK and Fanstel BT40 modules and reluctant to be using outdated versions of the SDK. Dev machines Win 10 x64.

How soon could a clean version be available?

Parents
  • VirusTotal reports no issues with nrfconnect-setup-3.10.0.exe 3.10.0 Windows 32-bit and 64-bit  so our IT team has installed that version. However version 3.10.0 of nrfconnect-setup installs Toolchain Manager v1.1.3 which complains that it only supports nRF Connect for Desktop 3.11.1 and may not work as expected.

    It then fails if I attempt to launch.

    BTW, you can easily upload files yourself to https://www.virustotal.com/gui/home/upload . 

    Updating Connect for Desktop to 3.11.1 from within 3.10.0 required admin rights for several drivers so I had to skip those. The update "seems" to have progressed OK so far despite skipping the drivers, and allowed me to install the SDK v2.0.0

Reply
  • VirusTotal reports no issues with nrfconnect-setup-3.10.0.exe 3.10.0 Windows 32-bit and 64-bit  so our IT team has installed that version. However version 3.10.0 of nrfconnect-setup installs Toolchain Manager v1.1.3 which complains that it only supports nRF Connect for Desktop 3.11.1 and may not work as expected.

    It then fails if I attempt to launch.

    BTW, you can easily upload files yourself to https://www.virustotal.com/gui/home/upload . 

    Updating Connect for Desktop to 3.11.1 from within 3.10.0 required admin rights for several drivers so I had to skip those. The update "seems" to have progressed OK so far despite skipping the drivers, and allowed me to install the SDK v2.0.0

Children
  • Hello,

    Thank you for the additional information - I have passed this on to our nRF Connect for Desktop team as well.

    AlanZ said:
    Updating Connect for Desktop to 3.11.1 from within 3.10.0 required admin rights for several drivers so I had to skip those. The update "seems" to have progressed OK so far despite skipping the drivers, and allowed me to install the SDK v2.0.0

    Are you able to build the default applications from the SDK just fine, or is there any complaint about missing dependencies?

    Best regards,
    Karl

Related