The issue is known and our R&D team is already working on the fix.
For now, I can suggest a workaround you can perform on your side:
Find the file called enginesettings.list
It might be located either in %programdata%\{Your_Company_Name}\ or in %appdata%\local\{Your_Company_Name}\
Or try finding it using windows search.
In that file find the line <FilterInvalidCharsOnListing>false</FilterInvalidCharsOnListing>
and change it to <FilterInvalidCharsOnListing>true</FilterInvalidCharsOnListing>