title: Stuck after 'sxe ld' command
body: <p>I'm trying to setup break points on modules that are not loaded yet.</p>
  
  <p>So I asked windbg to stop on module loading:</p>
  
  <p><code>sxe ld *xml*</code> (Just some random module for testing)</p>
  
  <p>Then I saw this:</p>
  
  <pre><code>0:010&gt; sxe ld *xml*
  0:010&gt; g
  ModLoad: 70d10000 70e68000   C:\Windows\System32\msxml6.dll
  eax=00000001 ebx=00000000 ecx=002a260c edx=0022017c esi=7ffd9000 edi=02259024
  eip=775070b4 esp=02258f3c ebp=02258f90 iopl=0         nv up ei pl zr na pe nc
  cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
  ntdll!KiFastSystemCallRet:
  775070b4 c3              ret
  </code></pre>
  
  <p>That output quickly showed, but windbg entered a 'BUSY' state. Why is that? </p>
  
  <p>I have turned off address resolution with <code>.symopt+ 100</code>, I don't know why it stuck now, any way to find out?</p>
  
  <p>(Running Windows 7 x86 in Virtrual Box)</p>