Scripting WinDBG to process captured minidumps

I script windbg.exe to process minidumps captured in my QA organization,
which can amount to thousands every couple of weeks.

This is the PowerShell script I use to run my script after preparing the
input files:
============= run-triage-windbg.ps1 ==================
Param ()
Set-StrictMode -version latest # inform of uninitialized variables
$ErrorActionPreference = ‘Stop’
$VerbosePreference = ‘Continue’

$windbgexe = ‘c:\Program Files (x86)\Windows
$windbgargs = @(‘-WX’,‘-QSY’,“-logo "${Env:WINDBG_LOG}”“,”-c
"$\<${Env:TRIAGE_WINDBGCMDS_FILE}“”,“-y "${Env:_NT_SYMBOL_PATH}”“,”-z

$proc = Start-Process $windbgexe -Passthru -WindowStyle Hidden
-ArgumentList $windbgargs
Wait-Process -InputObject $proc

My problem is that even though the WinDBG main GUI window is not shown
(due to -WindowStyle Hidden), the window titled “Command - Dump … -
WinDbg: 10.0.10586.567 AMD64” still gets displayed while the script is

Is there any way to make sure that window gets created docked by default? I
currently run without any workspaces.

Appreciate your input,
Osiris Pedroso

I’m not sure I completely understand the problem, but maybe try using the
command line version (kd.exe) instead? It should take the same command line
arguments as WinDbg.