Hi, we have a desktop application developed in PowerBuilder 2017 R2. This application does not use any external functions or DLL calls. But when it is launched, it has been observed that the application is internally searching for some Windows DLLs on entire Windows installation drive i.e. without qualifying the complete path. May be this is an existing behavior of PowerBuilder, but it is making the application as vulnerable to attack as one can easily develop a malicious DLL with any Windows DLL name the application looks for. Basically it is making dynamic search for dependent DLLs. So Is there any way that will force the PowerBuilder application to search for the required DLLs qualified by the complete path?