On Thursday, December 8, 2016, Alexandre Julliard &lt;<a href="mailto:julliard@winehq.org">julliard@winehq.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Lauri Kenttä &lt;<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;lauri.kentta@gmail.com&#39;)">lauri.kentta@gmail.com</a>&gt; writes:<br>
<br>
&gt; On 2016-12-08 17:58, Alexandre Julliard wrote:<br>
&gt;&gt; Lauri Kenttä &lt;<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;lauri.kentta@gmail.com&#39;)">lauri.kentta@gmail.com</a>&gt; writes:<br>
&gt;&gt;<br>
&gt;&gt;&gt; v2: Win8 and Win10 give different results (sometimes even<br>
&gt;&gt;&gt; different different results), so mark some cases as broken.<br>
&gt;&gt;&gt; Also simplify the patch overall.<br>
&gt;&gt;<br>
&gt;&gt; I don&#39;t think that painting on the desktop window is a very useful<br>
&gt;&gt; test,<br>
&gt;&gt; and it can fail for various reasons. If the goal is to test<br>
&gt;&gt; LockWindowUpdate, you should do that with top-level windows instead.<br>
&gt;<br>
&gt; If painting to desktop is not interesting, then bug 52 (the oldest<br>
&gt; open bug) should probably be closed.<br>
<br>
As I mentioned in a comment there, that&#39;s mostly a WONTFIX. There may be<br>
a use for LockWindowUpdate in other cases, but scribbling over the<br>
desktop is not a particularly interesting case.<br>
<br></blockquote><div><br></div><div>A program use case: IDA 5 Free relies on this while doing heavy loading, to reproduce just try to open any exe file and notice the LockWindowUpdate calls.</div>