I do have the snoop sourcecode and have looked through it, but unfortunately it is a bit too complex for me to understand in its entirety.

Yes, the initial element would be the main window, but obtaining that element as an object that can be used is the issue that I'm having

Thank you. I did read that the controls in a WPF application do not have handles and therefore must be traversed through with a TreeHelper/Walker, but I cannot figure out how to get the initial element to start the process. I have the names of the controls I need to find by using Inspect and Snoop, but finding the controls by name seems to require an initial element.

I am assuming this is relatively simple, but I have not been able to figure this out as of yet. I have an external WPF application that I cannot modify, but I would like to retrieve the data from a control in the application. I have the code to retrieve the application top window from the windows API and the code needed to traverse the visual tree to find child items. The problem lies in getting the window (which is contained in the HwndWrapper) into an object in my program that I can use to send to my code to find the controls I need. I have tried searching and have come up with the following: Using HwndSource.FromHwnd() - Returns Nothing Casting a custom window class to Window - Will not convert Inheriting from Window in custom window class - none of the attributes I need get populated this way. I know that this can be done, as the opensource project, snoop, is able to get the data. Unfortunately it is written in C# with a C++ ManagedInjector and I am not as proficient in these languages as I am in VB, so while I can read and understand some of it, the rest is lost on me. I truly hope that someone will be able to help me with this project, as I am ready to tear my hair out. Thanks in advance.