cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CUBEIDE install error

최민혁.1
Associate II

It doesn't install as the phrase pops up. "can't initialize plugins directory. please try again later​"

I've tried everything. Please help me.

window10 64bit

intel core i7-6700 3.4GHz

0693W000004Ik7yQAC.png

1 ACCEPTED SOLUTION

Accepted Solutions
Markus GIRDLAND
ST Employee

I've also searched around and come to the same conclusion as @KnarfB​ in that it appears to be a common windows issue.

The three solutions I've seen throughout these searches that has worked for some of the users are:

  1. Create a new user without any spaces or non-ASCII characters. This seems to only be relevant if your current user profile uses non-ASCII or spaces!
  2. Clean boot as described on Windows support page here.
  3. %TEMP% folder access rights, which has already been mentioned and tried.

Besides those three I haven't seen any other solutions where users reported that it worked except one where it just suddenly started working again but the user didn't mention any changes made, so not much to be learned from that case.

View solution in original post

5 REPLIES 5
KnarfB
Principal III

No specific tip, on many machines it works.

Take care that the install path is short and ASCII alphanumeric characters only, e.g. C:\ST\STM32CubeIDE.

Also: search the internet for the error message. Looks like a common windows issue.

I also searched. But I do not know the cause.

Sometimes, issues with the access rights of the Windows %TEMP% folder were reported.

I've already tried that method. Still not installed

Markus GIRDLAND
ST Employee

I've also searched around and come to the same conclusion as @KnarfB​ in that it appears to be a common windows issue.

The three solutions I've seen throughout these searches that has worked for some of the users are:

  1. Create a new user without any spaces or non-ASCII characters. This seems to only be relevant if your current user profile uses non-ASCII or spaces!
  2. Clean boot as described on Windows support page here.
  3. %TEMP% folder access rights, which has already been mentioned and tried.

Besides those three I haven't seen any other solutions where users reported that it worked except one where it just suddenly started working again but the user didn't mention any changes made, so not much to be learned from that case.