New Post: could I debug kernel outside of Windbg?

Not sure if I am doing something wrong or not so I thought that I would just ask:

I am using version 0.3.0.30 of PyKd (along with python 2.7.10) and am trying to issue a command to the debug engine. However, when I display the results of the command I only receive the string None rather than what was expected (this happens for any command that I try to pass through to the debugger).

For clarity, here is a screen capture of what I am doing and what I am seeing:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\System32>cd \

C:\>python
Python 2.7.10 (default, May 23 2015, 09:40:32) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import pykd
>>> pykd.attachKernel(r"com:pipe,resets=0,reconnect,port=\\.\pipe\com_1")
>>> ext = pykd.loadExt(r"C:\WinDDK\7600.16385.1\Debuggers\winext\kext.dll")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
pykd.DbgException: failed to load extension with error 193
>>> ext = pykd.loadExt(r"C:\WinDDK\7600.16385.1\Debuggers\winext\kext.dll")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
pykd.DbgException: failed to load extension with error 193
>>> pykd.isKernelDebugging()
True
>>> print pykd.dbgCommand("!process 0 0 explorer.exe")
None
>>>

Since the target state is sitting at the desktop I would have expected the return value to contain the explorer process information.

Am I not doing something correctly or misunderstanding the use of PyKd from outside Windbg?

Thanks.

-- Michael --