Incident Response & Digital Forensics Debugging Extension
C++ C
Latest commit 207ca90 Feb 1, 2017 Andrey Bazhan Merge branch 'dev'


SwishDbgExt is a Microsoft WinDbg debugging extension that expands the set of available commands by Microsoft WinDbg, but also fixes and improves existing commands. This extension has been developed by Matt Suiche (@msuiche) – feel free to reach out on ask for more features, offer to contribute and/or report bugs.

SwishDbgExt aims at making life easier for kernel developers, troubleshooters and security experts with a series of debugging, incident response and memory forensics commands. Because SwishDbgExt is a WinDbg debugging extension, it means it can be used on local or remote kernel debugging session, live sessions generated by Microsoft LiveKd, but also on Microsoft crash dumps generated to a Blue Screen of Death or hybrid utilities such as Comae DumpIt.

2016 Contest

More information on


You can either copy the WinDbg extension in the corresponding (x86 or x64) WinDbg folder or load it manually using the !load command such as below. Please note you can’t have spaces or quotes in the full path to the target dll to be loaded. !load X:\FullPath\SwishDbgExt.dll


kd> !load E:\projects\labs\SwishDbgExt\bin\x64\SwishDbgExt.dll;
       SwishDbgExt v0.7.0 (Nov  2 2016) - Incident Response & Digital Forensics Debugging Extension
       SwishDbgExt Copyright (C) 2016 Comae Technologies FZE -
       SwishDbgExt Copyright (C) 2014-2016 Matthieu Suiche (@msuiche)

       This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
       This is free software, and you are welcome to redistribute it
       under certain conditions; type `show c' for details.

If you wish to update your WinDbg template with a more DML-friendly template, you can directly import windbg_template.reg file joined to the package.


  • Define structures
  • Define Commands
  • Announce feature contest.



Displays information on available extension commands.

This command will give you the list of all commands if you specify no argument, will give you the list of parameters for an existing command if specified as an argument.


Display callback functions


Look for used code cave


Display console command's history


Display user's credentials (based on gentilwiki's mimikatz)


Display list of drivers. !ms_drivers will go ahead and display a list of drivers that are currently loaded. In this example, here’s a few of the drivers loaded at the time of the crash in this kernel-dump: With this command, we can also view in-depth IRP information regarding a driver: In the above image we can see the driver-specific I/O stack location within e1cexpress.sys’ IRP. Here we can see function codes such as IRP_MJ_CREATE which opens the target device object, indicating that it is present and available for I/O operations.


Dump memory space on disk


Display Ex queued workers.

!exqueue doesn’t work properly on Windows 8, so a working version needed to be implemented. Just like the original command this one dispaly the working threads queue.


Reset segmentation in WinDbg (Fix "16.kd>")


Display GDT.

!ms_gdt displays the Global Descriptor Table. Note on x64 that every selector is flat (0x0000000000000000 to 0xFFFFFFFFFFFFFFFF). This command can be extra helpful to check for any suspected hooking of the GDT, as attempting to do so on x64 will call a bug check. This is because x64 forbids hooking of the GDT.


Display list of registry hives.

ms_hivelist displays a list of registry hives. We can look directly into a hive (\Registry\Machine\Software for example) to see its subkeys, values, etc:

Alt text


Display IDT.

!ms_idt displays the Interrupt descriptor table. Very much like the GDT, if the IDT is hooked on an x64 system, it will call a bug check. This is due to the fact that Microsoft implemented (programmatically) a prevention of hooking the IDT with a kernel-mode driver that would normally intercept calls to the IDT and then add in its own processing. This is why in the above image, there is ‘No’ as far as the eye can see.


Analyze a memory space and returns a Malware Score Index (MSI) - (based on Frank Boldewin's work)


Scan Master Boot Record (MBR)


Display network information (sockets, connections, ...)


Display list of object


Display list of processes. !ms_process is an improved version of !process and !dml_proc.. One of the nice thing as you can notice below is the usage of DML (Debugger Markup Language) with the commands. All the underline commands are in fact links to commands. As an example below, you can see the output of /vads /scan, to scan VAD (Virtual Address Descriptors). You can notice that one column gives the “Malware Score Index” which can be useful to detect shellcodes or heap-spray. In the screenshot below, you can see an abnormally high score in several VADs – due to usage of heap spray. Just by clicking on the score it will run the scanning algorithm. The scanning algorithm is based on Frank Boldewin’s OfficeMalScanner utility. And returns you information about where the shellcode is: /scan option can also be used on exported functions to know if the EAT (Export Address Table) has been patched or if the prolog of the function modified.

Similar tests are available for the SSDT (!ms_ssdt).


Read key control block


Read key node. !reg WinDbg command has been a frustration for a long time, due to some bugs. This is why SwishDbgExt, has its own registry explorer functions to try to make access to registry data as simple as possible.


Read key value


Scan and display suspicious NDIS hooks


Display list of services


Display service descriptor table (SDT) functions. !ms_ssdt displays the System Service Dispatch Table. This command is extremely helpful in the investigation of suspected rootkit hooks through what is known as Direct Kernel Object Manipulation (DKOM). If you see a low level routine here that is hooked (such as nt!NtEnumerateKey), this can aid you in your analysis regarding a possible rootkit infection.


Display information related to the Store Manager (ReadyBoost).

The present command allows to list the current ReadyBoost (requires USB 3.0) cache used by the Operating System, but also to display the logs of the memory pages managed by the store manager. Parameter: /cache


Display list of KTIMER.

!ms_timers displays the KTIMER structure, which is an opaque structure that represents and contains various timer objects. This command can be helpful to figure out what drivers created what timer objects, what drivers called what routines, etc.


Display list of cached VACBs


Turn verbose mode on/off


The following is based on the research published by Alex Ionescu and available here:

This feature is available on Windows 10+ O.S. as an optional feature installable via the following PowerShell command:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

You can read more about the Windows Subsystem for Linux at the following links:

    Windows Subsystem for Linux Overview.
    Instance 0xFFFFE704EEB8F010
    GUID: {E29032FD-35D3-4C53-AB68-6BCEBDA7176F}
    State:            (1) [STARTED]
    Creation Flags:   00000001
    GlobalData:       0xFFFFF802ED4138A0
    Root Handle:      80000834
    Temp Handle:      80000838
    Job Handle:       8000083c
    Token:            80000818
    Event Handle:     800008bc

    Map Paths (0):    0xFFFFE704EF437920
    VFS Context:      0xFFFFE704EEFC4710
    Memory Flags:     0x2

    Last PID:         35
    Thread Groups:    3
        Session 0xFFFFE704EDB79EC0
        Instance:         0xFFFFE704EEB8F010
        Console inode:    0x0
        Foreground PID:   -1
            Process Group 0xFFFFE704EDB79AE0
            Instance:      0xFFFFE704EEB8F010
            Session:       0xFFFFE704EDB79EC0
                Thread Group 0xFFFFE704EF4F8000
                Binary Path:           /init
                Thread(s):             1
                Owner Process Group:   0xFFFFE704EDB79AE0
                Flags:                 0x00000000
                Main Thread:           0xFFFFE704EF5CC010
                Arguments (006 bytes): 0x00007FFFC081D6E0
                    Process 0xFFFFE704EF2F1D70
                    Instance:            0xFFFFE704EEB8F010
                    NT Process Object:   0xFFFFAE05E84EF800
                    NT Process Handle:   0xFFFFFFFF80000F58
                    VDSO Address:        0x00007FFFC0849000
                    Stack Address:       0x00007FFFC001E000
        Session 0xFFFFE704EF5DB830
        Instance:         0xFFFFE704EEB8F010
        Console inode:    0xFFFFE704EF32D7A0
        Foreground PID:   2
            Process Group 0xFFFFE704EF5EF970
            Instance:      0xFFFFE704EEB8F010
            Session:       0xFFFFE704EF5DB830
                Thread Group 0xFFFFE704EF5EE000
                Binary Path:           /bin/bash
                Thread(s):             1
                Owner Process Group:   0xFFFFE704EF5EF970
                Flags:                 0x0000000C
                Main Thread:           0xFFFFE704EF5F8010
                Arguments (010 bytes): 0x00007FFFDF34E418
                    Process 0xFFFFE704EDEF6EC0
                    Instance:            0xFFFFE704EEB8F010
                    NT Process Object:   0xFFFFAE05E84E6800
                    NT Process Handle:   0xFFFFFFFF80000D9C
                    VDSO Address:        0x00007FFFDF883000
                    Stack Address:       0x00007FFFDEB4F000
        Session 0xFFFFE704EF0A8ED0
        Instance:         0xFFFFE704EEB8F010
        Console inode:    0xFFFFE704EF06B9C0
        Foreground PID:   19
            Process Group 0xFFFFE704F059CBC0
            Instance:      0xFFFFE704EEB8F010
            Session:       0xFFFFE704EF0A8ED0
                Thread Group 0xFFFFE704EDE51000
                Binary Path:           /bin/bash
                Thread(s):             1
                Owner Process Group:   0xFFFFE704F059CBC0
                Flags:                 0x0000000C
                Main Thread:           0xFFFFE704EDC78090
                Arguments (010 bytes): 0x00007FFFF78CFB78
                    Process 0xFFFFE704F06389B0
                    Instance:            0xFFFFE704EEB8F010
                    NT Process Object:   0xFFFFAE05E618D800
                    NT Process Handle:   0xFFFFFFFF80001650
                    VDSO Address:        0x00007FFFF7C99000
                    Stack Address:       0x00007FFFF70D0000



MsPEImageFile contains the basic common information used by Windows binaries (PE) and has been derivated into three different classes:

  • MsProcessObject
  • MsDllObject
  • MsDriverObject