The “path” that is used for command-line resolution does not affect the search path that is used for dynamic libraries in Windows.

The LoadLibrary API-call is described here:   http://msdn.microsoft.com/en-us/library/ms684175%28v=vs.85%29.aspx.

There is a “safe library search order” feature now in Windows, as described in the article Dynamic-Link Library Search Order:   http://msdn.microsoft.com/en-us/library/ms682586%28v=vs.85%29.aspx.   (Yep, Microsoft is still trying to put a (ahem...) on its fundamentally poor original design ...)

It is also remotely possible that the installed version of this DLL has been retro-graded by the recent install.   A thorough search of the C: drive for all occurrences of this filename may be required.   (The “modification date” of that file may or may not be useful.)

Perhaps one of these resources will help to resolve the problem.   Please let us know.