Yeah, its wkix32.exe. I tried it and got a different but similiar result if that makes sense. I can probably control the output/read the output of that window too if I put my mind to it. Maybe even detect the wkix32 and not even open up my own debug window but I don't think many people would use it as they would just use the kix32.exe when using my program. Not sure though, if people would want the ability to track errors generated by wkix32.exe I can probably do it, need to see if thats the case.
