Enabling "DOS names" seems to have fixed this error for me.

Just wanted you to know so that you might fix it properly in next versions.

With regards, Alex