http://bugs.winehq.org/show_bug.cgi?id=58811 --- Comment #17 from Nikolay Sivov <bunglehead(a)gmail.com> --- Great, thank you. That's what I suspected, I think: --- 149493 0024:trace:dwrite:dwritefontsetbuilder2_AddFontFile 00007F15AB395220, L"\\??\\unix\\home\\maduranma\\Projects\\wine\\wine-git\\build64\\fonts\\tahomabd.ttf". ... 149500 0024:trace:dwrite:localfontfileloader_CreateStreamFromKey 00006FFFF5F82040, 00007F1586F8A1E0, 156, 00007FFFFE1FDE18. 149501 0024:trace:file:CreateFileW L"\\??\\UNIX\\HOME\\MADURANMA\\PROJECTS\\WINE\\WINE-GIT\\BUILD64\\FONTS\\TAHOMABD.TTF" GENERIC_READ FILE_SHARE_READ FILE_SHARE_WRITE creation 3 attributes 0x80 ... 149506 0024:warn:file:CreateFileW Unable to create file L"\\??\\UNIX\\HOME\\MADURANMA\\PROJECTS\\WINE\\WINE-GIT\\BUILD64\\FONTS\\TAHOMABD.TTF" (status c0000034) 149507 0024:trace:file:CreateFileW returning FFFFFFFFFFFFFFFF --- What most likely happens is that you don't have Z: drive, which is mapped by default to the system fs root /. When you don't have this mapping, font file paths in registry will use "\??\unix\" prefix to denote plain unix paths. My guess is that such paths are case-sensitive. I'll have to check, but the fix would be to disable path manipulation in case of \??\unix\ paths. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.