Skip to main content
davis65553906
Participating Frequently
November 20, 2015
Answered

Win32 API error 193. Could not call C function: private_load_AgCoreTest

  • November 20, 2015
  • 4 replies
  • 22914 views

Hi guys,

When I try to run Lightroom, I get the following error messages:

  • Win 32 API Error 193 ("(unknown error)") when calling ::Load library from getCFunction
  • Could not call C function: private_load_AgCoreTest

Then I can't have access to my library or to make a new library by importing files.

I'm running it on a notebook with Windows 10 64-bit, Nvidia GeForce 850m GTX and an Intel Core i7 processor, with 12 Gb of RAM and a 500 Gb SSD (Samsung 840 EVO). Everything with the latests drivers.

I've already tried to unninstall and reinstall the program, all my Visual C++ packages and dll's. I've also already checked my permissions to the catalog folder and granted full access. I've also tried to run Lightroom as administrator.

None of these fixed the problem.

What should I do?

This topic has been closed for replies.
Correct answer Brett N

Hi Brett,
I`ve already done all these things... I've manually deleted all Lightroom and Adobe folders. In fact, I've done it a million times, and always reebooting my computer after each step to make sure that Windows notice that the files are really gone.

But I still have all these errors... None of the solutions that were given to me worked, including here at the forum or when using adobe phone/chat support service.

I'm mad due the fact that I'm paying for a software that don't work and don't have enought support!!!

I've read this thread abou another customer with the exact same problem as mine (Help WINAPI error 193 when calling Load Library) and she only got it working when the guys at the support center remotelly fixed her problem. I've asked for remote support, but the people at adobe chat are just refusing to do so... So what should I do?


According to the notes, they followed the directions here to resolve the issue: Error: "Unable to start correctly (0Xc000007b)"

4 replies

Participant
October 14, 2019

I am facing the same problem

 

Participant
January 15, 2018

现在我也出现同样的错误,请求帮助,谢谢!

Participant
November 20, 2015

Try creating a new user with administrator rights and then try

davis65553906
Participating Frequently
November 21, 2015

I've tried creating a new user with Administrator rights, but it also didn't work... I have absolutely no idea about what to do to fix this thing!!!

davis65553906
Participating Frequently
November 21, 2015

Well, I'm going to recap all that I've tried to do until now:

  • Tried to uninstall (sometimes using the creative cloud cleaning tool) an reinstall several times;
  • Tried to paste the recomended lightroom 64-bit dll files into the programs folder;
  • Tried to install and run under a new administrator user account;
  • Tried to uninstall and reinstall all my Visual C++ redistributable packages;
  • Checked that all users have full control over all folders needed for Lightroom to work.
  • Updated my GPUs drivers (Nvidia GTX 850m and Intel HD4600 integraded card);
  • i've also tried to disable the GPU on the Performance tab, in Preferences.
  • Updated my Java versions, both 32-bit and 64-bit;

Despite of all these, I still can't use the program.

Also, I've notice a different error message when I try to go to the Slide Presentation Module:

  • ?:0: attempt to index field 'videoController' (a nill value)

Please guys, help me!!!

Community Manager
November 20, 2015

Hi davis65553906

Check the Post-processing section of your Export dialog.

In the dropdown of "After Export", choose "do nothing"

davis65553906
Participating Frequently
November 20, 2015

Hi Chetna,

I think you didn't understand my problem. I get these errors immediately after openning the program, so the Library, the Book and the Slide Presentation Modules don't work.

I can't get to the Export dialog because I can't even ad a file to my catalog. My library is completely empty, there's nothing to export.

Community Manager
November 20, 2015

Thanks for the update.

I am sorry I missed the part that you were getting the error as soon as you launch and believed that you were getting it while working.

Here are the steps that you need to follow :