Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=47813 Your paranoid android. === w7u (32 bit report) === user32: win.c:966: Test failed: wrong dwStyle: 84cb0000 != 94cb0000 for 000401AE in hook HCBT_ACTIVATE === w7pro64 (32 bit report) === user32: win.c:966: Test failed: wrong dwStyle: 84cb0000 != 94cb0000 for 000201C4 in hook HCBT_MINMAX win.c:977: Test failed: wrong dwWindowStatus: 0000 != 0001 active 000201C4 fg 003901C8 in hook HCBT_MINMAX === debian9 (32 bit Chinese:China report) === user32: msg.c:8713: Test failed: WaitForSingleObject failed 102 msg.c:8719: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8719: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8719: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000 === debian9 (32 bit WoW report) === user32: menu.c:2354: Test failed: test 27 msg.c:8713: Test failed: WaitForSingleObject failed 102 msg.c:8719: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8719: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8719: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000