No, Unicode pathnames are a horror and you're done if you don't have an appropriate language support installed on your box. You won't be able to either access, or rename, or delete the offending file. But then, upper-/lower-casing isn't going to work for you either.
The same goes about Linux chars not allowed in the Windows pathnames created or copied to the Windows hosts from under their Linux VM's.
Avoid localized path/file names under Windows at all times and use ANSI whenever possible because there may be potential users whose environments are not equipped with the corresponding locale.
Not that it matters much to Anglo-Saxon users though whose locale support is built into the MS Windows installations natively.