[SirFisher]

Hello, I have been searching around forums for the past few hours and have not found a solution to my problem so I figured I would post this here. I recently purchased a new laptop and after freshly installing Esys v 3.27.1 with the free token master v 2.82.162 free installer, when launching I am met with the error; "Loading: E-Sys Launcher PSdZ API Module Failed! Error C:\ProgramData\TokenMaster\E-Sys Launcher Pro\bin\PSdzAPI.dll: Can't find dependent libraries."

Is there a newer way to provide the est token to E-sys, I have this exact software setup on a different laptop where it runs without this error. I have checked through my entire c: drive and have now found the PSdzAPI.dll file anywhere. Is this something I need to download from somewhere or have I set my E-sys up incorrectly...

Older posts say to upgrade the pro launcher version, but as far as I know this is the newest reliable method. I looked into purchasing the premium as donation ware but I do not know when I would receive this product.

I followed the E-sys installation instructions provided by shawnsheridan to the best of my ability and have done a clean install of windows on my laptop as well as copied all of the files I used to install from my other laptop and that has not helped.

Any and all input is greatly appreciated, I just retrofitted NBT EVO id6, the 6wb cluster and rear parking sensors to my vehicle and I am in desperate need of coding it.

Thank you so much

[torobravo33]

Sounds like you need to download the PSdZ data and add it to C:/data/PSdZdata.

[SirFisher]

I will double check that I installed the PSdZdata in the correct location. I downloaded the latest Lite folder and installed it per the ESYS install instructions under C:/data/PSdZdata.


I tried redownloading the data but I got the same weird error saying its missing a file in the ProgramData folder, which is odd because the Pro Launcher is 32bit meaning that the tokenmaster folder is in ProgramData(x86)

[SirFisher]

I wanted to mention as well that I installed Esys on a separate windows surface in the exact method I did for the other laptop which has the response listed above. Interestingly the surface so far has not had any issues nor does it run into this error. I just would like to try and figure out what I did wrong on my own laptop because I am unable to borrow the other surface laptop that often.

[Fettler]

Hi, I have the same problem as SiriFisher above:
New install of E-Sys v3.27.1 build 44813 with TokenMaster's free E-Sys Launcher Pro v2.82.162. When I run the launcher I get error message: "Loading: E-Sys Launcher PSdZ API Module Failed! Error C:\ProgramData\TokenMaster\E-Sys Launcher Pro\bin\PSdzAPI.dll: Can't find dependent libraries." I'm using Windows10 Home laptop.

When I start E-Sys without using the launcher, it runs and connects to my vehicle. I have downloaded PSdZ data and put it in C:/data/PSdZdata

Did you solve this problem? Any help would be much appreciated, thanks

[joshaguirre]

Same issue here...

[RuleNormaliai]

The best working settings for me are:

Download E-Sys 3.27.1
Download ESysLauncherPROSetup_2.8.1_Build_155
Download TokenBuster_1.0

Install Esys
Install Launcher
Run TokenBuster
Follow the instructions and you're done!

Enjoy your fully working E-Sys (offcourse you will need PSdZData of version that you want)

If you want more info you can PM me i will be glad to help you out.

[pete in fate]

Originally Posted by RuleNormaliai

The best working settings for me are:

Download E-Sys 3.27.1
Download ESysLauncherPROSetup_2.8.1_Build_155
Download TokenBuster_1.0

Install Esys
Install Launcher
Run TokenBuster
Follow the instructions and you're done!

Enjoy your fully working E-Sys (offcourse you will need PSdZData of version that you want)

If you want more info you can PM me i will be glad to help you out.

Having issue with v3.33.0 Do you have links to the downloads that I need? You are very helpful, really appreciate it! Thanks!!

[FIREXTREMESLAYER]

has this issue been resolved? i'm still being affected by it...

[SirFisher]

I'll be totally honest, I do not know why the issue was resolved. I took a break for two weeks and it was working by the end of it. Now I am having issues with ISTA+, so I do not know if the problems are related...

[nstone97]

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

[spyro512]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

Came here to say thanks. Worked for me.

I cant really explain why because the .dll that is meant to be found in that Launcher folder is NOT in the folder after installing these both updates you mentioned, but it worked.

[thedi4bl0]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

Solved! Thanks!!

[stanospeed]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

You are the best ! works for me !

[9mmkungfu]

Thanks for posting this. My .dll error went away with this as well.

[vickersss]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

Thanks for this! This also fixed the exact same issue for me when setting up a new laptop with ESYS.

[Larrylotus]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

Oh thanks ! It worked for me as well, for a fresh E-Sys installation on Windows 10.

[AndriusL]

Thanks a lot.

[bicoven]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

Thanks for sharing that

[hotnikks]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

This was an amazing find. Thanks!

[ramziadi]

Originally Posted by nstone97

To revive an old thread, in hopes of helping others who may be having a similar issue.

I was able to solve my missing dependent library issue by looking in the Windows Event Viewer to see an error related to Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86".

Installing both the x32 and x64 versions of the 2013 redistributable from this link solved my issues.

Thank You so much, it worked for me

[aidbar2]

Thanks!