Malformed URL Exception - Username with a blank space did not create a project

Well, at first, sorry if it is an already solved problem - I searched everywhere and dindn't find anything that could solve the issue.

My username in Windows has a blank space in it (TI guys choose this way).
I was able to install Modelio without any error and everything looks like to be ok.
But when I click to "Create a New Project", I got the following error:

java.net.MalformedURLException: Illegal character in path at index 21: file:/C:/Users/Renato Branco/.modelio/3.8/.eclipse/configuration.x86_64.os/org.eclipse.osgi/286/0/.cp/
Illegal character in path at index 21: file:/C:/Users/Renato Branco/.modelio/3.8/.eclipse/configuration.x86_64.os/org.eclipse.osgi/286/0/.cp/

As you can see, the problem is related to the blank space in my username "Renato Branco".

What I have to do to solve the issue?

I'm running on Windows 7 Professional, with the updated Java JDK and It is installed the Modelio 3.8.00 (Build 201810021138).

Hello, I had the same problem as you when I tried to create a new project on modelio. The only solution that I was able to find is by downgrading to an earlier version of modelio...
If you go on the download site you should have access to version 3.7 I think. just make sure to uninstall the other verison and it should work fine

I dont know how to stop the error from hapening in version 3.8. You say the error is in the blank space on your username but I know people who have been able to run it no problem even with a space in their username.

antoineT, thanks for the answer. It worked, as you said.
About the blank space, I really don't know if it is the real issue, but the error statement that the software provided pointed to it (as you can see in the URL error statement, if you count to "index 21" in the string, you will find the blank space in the suposed URL - and URLs do not accept blank spaces).
Anyway, it worked on version 3.7.1.
Best wishes!

Could you please tell us if there is special news/solutions about this bug, excluding the downgrade workaround?
The problem is affecting several colleagues at the course and, definitely, the product is the best choice. If feasible, we’d like to go ahead using v3.8.