Skip to main content
SQuin.2
Associate
April 14, 2020
Solved

Avast virus checker tells me that the newly installed STM32CubeIDE is infected (see attached). What should I do?

  • April 14, 2020
  • 1 reply
  • 1524 views

..

This topic has been closed for replies.
Best answer by Markus GIRDLAND

I’ve sent the request to the developers to also sign the windows binaries for future releases which they say won’t be a problem for future releases because now the ST-LINK GDB server is built separately from the CubeIDE build, which wasn’t the case previously.

We didn’t sign the windows binaries before because they were just a step in the build process and the signing process needs to be done manually.

For now, I would create an exception to allow the file.

So to summarize: It will be fixed in future releases of CubeIDE.

1 reply

Markus GIRDLAND
Markus GIRDLANDBest answer
ST Employee
April 15, 2020

I’ve sent the request to the developers to also sign the windows binaries for future releases which they say won’t be a problem for future releases because now the ST-LINK GDB server is built separately from the CubeIDE build, which wasn’t the case previously.

We didn’t sign the windows binaries before because they were just a step in the build process and the signing process needs to be done manually.

For now, I would create an exception to allow the file.

So to summarize: It will be fixed in future releases of CubeIDE.

SQuin.2
SQuin.2Author
Associate
April 15, 2020
Thank you for a most comprehensive answer Markus.