Sometimes, you may find an issue that you suspect is caused by an application from a third party manufacturer that has loaded .DLL files into your application. This article explains how you can find out what .DLLs are loaded into your application.
Use Process Explorer, as outlined here: https://support.microsoft.com/en-us/help/970920/using-process-explorer-to-list-dlls-running-under-the-outlook-exe-proc
Use ProcessMonitor by following these instructions:
1. Gather a ProcessMonitor trace of your application using these instructions.
2. Open the Filter menu and click "Filter..."
3. Click Reset
4. Choose "Process Name" "is" and write your application (Excel.exe was used in the example below)
5. Click Add, and it will show up like this in green:
6. Click "OK". You will now see a list where only the application you specified is listed. If you see nothing, you may have misspelled the application .exe, or what you wrote was not running.
7. Scroll down a few thousand lines, as it may be that not all .DLLs are loaded immediately, and doubleclick on any entry. You will see this:
8. To the bottom right, there is a column "Company". Click on that header to get the list sorted by company that published the .DLL.
9. Most entries will probably be Microsoft, but at the bottom and top of the list you will find entries that are from other companies, or are from Microsoft or other companies but are not listed as such.
Based on what you find when performing the above steps, you may want to consider disabling or temporarily uninstalling the 3rd party components there, as they may be what's introducing the unexpected behavior you are seeing. This is not guaranteed to find all
influence that 3rd party applications can have on your application if the issues is that e.g. 2 running application are competing for the same files, but it usually is sufficient.
One thing you may want to perform is to search online for each 3rd party application that you find in this list together with the problem that you are facing, and you may find if this is a known issue.
You can also use this method to find the versions of the 3rd party applications that you are using. You may find that you are using files that are maybe written several years ago, and don't necessarily work well with the current application you are using.