title: Is it possible to fix a full memory dump so that running .imgscan /l will no longer be required?
body: <p>For some reason I have started receiving dumps from production that require running <code>.imgscan /l</code> first.</p>
  
  <p>Now I tend to run small queries against the dump using CDB invoked from a powershell script. However, running <code>.imgscan /l</code> every time takes considerable amount of time.</p>
  
  <p>Is it possible to fix the dump in a way that renders <code>.imgscan /l</code> unnecessary?</p>
  
  <p>P.S.</p>
  
  <p>I think there is another problem with the need to run <code>.imgscan /l</code> - DebugDiag does not seem to understand such dumps.</p>