Hi Sunil, Microsoft Windows will map many extra DLL's into your process space which do not appear in a PE image dependency walker. These extra libraries which are mapped into your process can be completely different on each users machine. Some examples of extra dynamic link libraries which could be mapped into your process: 1.) AppInit_DLLs[^] 2.) Window Hooks[^] 3.) Application Compatibility Layer[^] (Much of the AppCompat/Shim Engine is NDA undocumented) 4.) Device Drivers may map extra DLL's into a process. If you want to visually inspect which libraries are loaded in each situation then I would recommend downloading Process Explorer by Mark Russinovich[^]. You can export your process information to a text file and differentiate them. Best Wishes, -David Delaune