Sometimes the path to the dll is incomplete when the information about it loading is captured. If the dll also exists on more than one logical drive (ie both C:\my_dll_path\release and D:\my_dll_path\release), the code can get confused about which one is correct. This problem should be resolved in the next release.
The work-around is to manually edit the dll's name in the profile (tbp or ebp) file.
I hope this helps.