![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Performance and Maintainance of Windows Vista A forum for performance and maintenance tasks in Windows Vista. (microsoft.public.windows.vista.performance_maintainance) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
When i load up my MS OS i get the follwoing error message:
the procedure entry point get processimage file name could not be located in the dynamiclnk library psapi.dll. Can someone help me find out what this is and how to rectify the problem. |
|
|||
|
HERE IS THE SOLUTION TO YOUR PROBLEM: Apparently this is a DLL belongs to Process Status Helper (I think from Microsoft) and it has the procedure entry point GetProcessImageFileNameW that is incompatible. According to Microsoft, there is only one PSAPI.DLL file in your PC and it is under the Windows\System 32 folder. Additional PSAPI.DLL file may be installed by third party programs such as SmartBridge, often the older version. If you have other versions of the PSAPI.DLL file in the system, it can cause your IE 7 or other windows programs that interact with IE7 to crash when you start it up. Beside, you may have annoying error message like above too. *To solve the PSAPI.DLL incompatibility issue* and overcome this problem, search your PC or check the program folder of the application that crashes for a PSAPI.DLL file: 1. Open up Search from Start Menu. 2. Find all instances PSAPI.DLL on your PC. 3. Rename all extra copies of PSAPI.DLL files found EXCEPT the one located in \Windows\System32\ folder to some other names like PSAPIOLD.DLL (never delete or do anything with the PSAPI.DLL file in your Windows or Windows/System 32 folder). 4. Reboot the system. After reboot, there will not be anymore conflict and Windows will automatically look for valid PSAPI file in the Windows system folder. solution from 'my digital life' (http://www.mydigitallife.info/2007/0...-library-file/) Hope this helps! -- 0vermind |