Skip to main content
Semer CHERNI
ST Employee
July 16, 2025
Solved

[Resolved] STM32CubeIDE project creation issue

  • July 16, 2025
  • 15 replies
  • 9455 views

Updated post to reflect permanent fix

Dear STM32CubeIDE user,

Further to the recent STM32CubeIDE project creation issue, we would like to inform you that a solution is now available for you.

This permanent fix applies to all STM32CubeIDE versions.

  1. Issue description

When creating a new STM32 project in STM32CubeIDE, the “STM32Cube” radio button may have become unresponsive, blocking the “Next” button after the product selection screen. This prevented the project creation from being completed.

  1. Permanent fix

You can apply this resolution to any STM32CubeIDE version, even if you applied the temporary workaround that we recently shared with you.

  1. Open STM32CubeIDE.
  2. Refresh the database.
    Go to Help > STM32Cube updater > Select “Check the Target selector Device Database Updates”
  3. Restart STM32CubeIDE
  4. If you deactivated the auto refresh function previously, you may wish to reactivate it for all your STM32Cube tools. Here is how to proceed:
  • STM32CubeIDE:
    Go to Window > Preferences > STM32Cube > Firmware Updater.
    Select your preferred auto-refresh option.
  • STM32CubeMX:
    Go to Help > Connection & Updates > Updater Settings.
    Select your preferred auto-refresh option.
  • STMCUFinder:
    Click on the Settings icon > Settings > Updater Settings.
    In the "Database Auto-Refresh" section, select your auto-refresh option.

We apologize for any inconvenience caused by this temporary issue.

If you require further information or assistance, please contact our customer support.

Best regards,

STMicroelectronics

Best answer by Amel NASRI

We understand your concerns and are fully committed to helping you overcome the recent issues with STM32CubeIDE to ensure continuous operation. We sincerely apologize for any inconvenience caused.  

We value your feedback and would like to provide clarification on the points you have raised.

  • We have identified the root cause behind this issue, and we are currently resolving resolved it.

The problem is due to a change in our database, which impacts current versions already deployed.

Edit: Permanent fix is available. Please refer to the updated original post or to the notification mail that you should have received.

  • Developers are never forced to update the versions of their tools.

As part of our software management lifecycle process, ST releases regular updates for multiple software packages to add new features or to fix issues on specific versions.

We are maintaining public access to all the versions of our tools and we have no intention of forcing developers to update them. The permanent fix shared for all previous STM32CubeIDE versions is proof of our commitment.

  • Rest assured that using STM32Cube tools is safe. Furthermore, the handling of your personal data is fully compliant with GDPR rules.

ST takes user privacy and data protection very seriously. Our STM32 tools are fully compliant with our corporate privacy statement.

Our tools collect anonymous data to improve future versions but we never use or copy developer code. The collection of analytics can be disabled in the tool settings.

  • We are removing the login from our tools and replacing it with a notification service.

Login information is used to communicate updates and fixes to developers. We are replacing this approach with a notification service. Users will be offered the choice to subscribe to notifications.

For more details on upcoming changes and improvements, you can refer to the post STM32CubeIDE 2.0 Release - Early Heads-Up, which outlines our plans to enhance your experience.

Your feedback is valuable, and we aim to ensure STM32CubeIDE meets your expectations. Please feel free to share any additional insights or suggestions.

15 replies

Associate
July 23, 2025

Reinstall the latest version 18.1 from the web portal.
Follow the instructions in 2. Permanent Solution and it's fixed. Thank you.

Associate
July 23, 2025

Thanks for the solution. With Best Regards...

 

Associate III
July 24, 2025

Refreshing the database in the STM32CubeIDE 1.19.0, and in STM32CubeMX 6.15.0 on Windows 11 I get an error popup about failing to download api_config.json. I never applied the temporary workaround. I guess this is not expected?

See attached picture.

 

 

Semer CHERNI
ST Employee
July 28, 2025

Hello,

Could you send me the STM32CubeMX.log file found under C:\Users\userID\.stm32cubemx.

KR,
Semer.

Associate III
July 29, 2025

Thanks for coming back to me.
In the meantime I could resolve it by applying the stated temporary fix(delete .stm32cubefinder) folder.
And I have also opened a ticket where I have uploaded that folder in the state that cause the problem.
Maybe that helps if you are still doing any further analysis. The ST case number is 00239810.

Visitor II
October 8, 2025

It would be awesome if you would put instructions that matched the ui. Specifically version 1.18 and 1.19 that do not have many of the fields that you have clearly specified for an older version. I am still trying to find where these fields are hidden in the UI. Instrcutions for faulrs should be clear

 

SMusc.1
Associate III
December 21, 2025

Hi, all of this os absurde but any way I cant see hoe to fix from the point n2 since there is no this menu on the release 2.0 as attached the picture. Now I have to spend time and time, day and day to let work the cube ide? It's all really absurd: lookat the picture attache and plese give me a solution.

Andrew Neil
Super User
December 22, 2025

This thread is over 5 months old; it's from long before v2.0.0 - so not relevant to v2.0.0.

 

Note that v2.0.0 no longer integrates CubeMX at all:

STM32CubeIDE 2.0.0 released - 18 November 2025

STM32CubeIDE 2.0.0 new workflow tutorial

For an explanation & discussion of this change, see: IDE Version 2.0.0 - why remove MX ?

 

If you still have a specific problem with v2.0.0, please start a new thread and give a full description of your issue:

How to write your question to maximize your chances to find a solution

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Associate III
December 24, 2025

Ah yes, the traditional ST approach to customer service:

- Ignore the problem

- Do something else, like add telemetry or an online account requirement

- Release a new version that eliminates the feature that doesn't work properly

- Tell everyone the problem is no longer relevant.

This is called the Soviet approach: "tell the government what you need, they'll tell you how to live without it."

FIY some people use older versions of tools for process and regulatory reasons. And also because the newer tools are not always an improvement on the older ones.

People forget: "evolution" does not imply "improvement". An evolution is only a change. It can be for the worst. ST proves it frequently.