The error is surely wrong. It doesn’t reproduce, neither under Wine nor on Windows 11. It is quite easy to see why this could happen though. Pushed a fix and documented the behavior that using an illegal name (such as a too long name) causes this predicate to fail silently.
I don’t know whether that is good or bad. On the one hand one could argue that it is better to raise an appropriate exception for an invalid name. On the other hand, we have seen that the Windows error codes are often wrong. And, one could argue that there is indeed no file with that name because the name is invalid and (thus) that file cannot exist. This, while it could exist on another system that can represent the file name.