I realized what you had asked now. The \u issue normally only happens in Windows, where it is very easy to accidentally name a file starting with ‘u’, and the \ comes from the Windows path. I am sure that is still a problem.
On Mac you can make the same error happen by starting the file name with ‘\u’, which it seems is a legal filename, that happens to trigger the same Unicode related problem.
So, no, it isn’t fixed.