https://bugs.winehq.org/show_bug.cgi?id=41258 --- Comment #10 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> --- I tried it also again, as a guess it might be a consequence of EnumDisplayDevices or EnumDisplayMonitors returning wrong stuff. I tried very poor and sad hack below, and it seems to get a tiny bit further, to crash in d3d11. I cannot run any d3d11 things because of my poor GPU, so maybe someone else with better computer could try the hack to see what happens; diff --git a/dlls/user32/misc.c b/dlls/user32/misc.c index fa0502e..50644fd 100644 --- a/dlls/user32/misc.c +++ b/dlls/user32/misc.c @@ -290,7 +290,7 @@ BOOL WINAPI EnumDisplayDevicesW( LPCWSTR lpDevice, DWORD i, LPDISPLAY_DEVICEW lp { FIXME("(%s,%d,%p,0x%08x), stub!\n",debugstr_w(lpDevice),i,lpDisplayDevice,dwFlags); - if (i) + return FALSE; memcpy(lpDisplayDevice->DeviceName, primary_device_name, sizeof(primary_device_name)); -- 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.