Windows 10 Fall Creators Update causes Could not call C function: private_load_AGCoretech

[chrisp74722975]

So the Microsoft update killed my lightroom today, very disappointing and typical Microsoft.

I am clearly not the only person with this issue where lightroom gets stuck as the "Could not call C function: private_load_AGCoretech" message - I simply cannot proceed further.

I have updated to the latest version (difficult to tell which when I cannot start the product successfully) and that makes no difference.

I am quite concerned because I've found updates for some products eg Power buddy but none to address this specific issue from Adobe yet.

Need help please! Not great news at Xmas!

[Just Shoot Me]

This is more than likely some type of permissions problem as MS has gone the way of Apple and it seems that with every new update they change drive, folder and file permissions.

Not sure where to start.

[chrisp74722975]

Slightly amusingly it also affects the Classic CC trial product but worse because task manager is unable to kill it, come on Adobe!

[Just Shoot Me]

Look here.

How to fix Lightroom launch error 'Could not call C function: private_load_AgCoreTech'.

[chrisp74722975]

Tried that too, been rummaging for the last couple of hours - the only things definitely dead at the moment are Genie timeline and Lightroom.

[chrisp74722975]

Just had a call with Microsoft support and the problem is entirely with Adobe according to them.

If only someone from Adobe monitored their official support forum, the forum that is the only way to raise a support request for the product.

Really rather disappointing. Perhaps if I keep raising the same call I will get a response.

[Just Shoot Me · Accepted solution]

It's not Adobe LR.

Look at this thread.

Error after Update 6.12: could not call c function private_load_AgCoreTech

Really if it was something LR did you would expect to see Hundreds of Thousands post about it. A Google search turns up not many report of this error.

It is some type of configuration error with your particular computer setup. I personally have never seen this error in the 15 years I've been using PS and the 11 years I've use LR.

[chrisp74722975]

I fully expect Microsoft have screwed up again, I've tried various of the redistributables - the link you send is certainly given as a common answer but is now out of date and cannot be updated.

I have also tried the Adobe 13p a minute help line - cost be better part of £1 before they got as far as a human being who did quickly agree to call me back in 30 minutes rather than me running up a bill - that was a couple of hours ago now.

However, thank you - you twigged a thought, while I have repaired both the x64 and x86 versions of the product and reinstalled the later versions (I can see 7 subsequent versions listed) I hadn't uninstalled, rebooted and reinstalled visal C++ 2010 redistributable x86 and x64 (just to be clear which this time) and indeed it works.

Who knew it could be so painful. SQL Server VSS Writer died during the original steps and was fixed by reinstall of 2012 redist, now to see if Genie timeline will play ball again.

Happy now - thanks for the pointers!

[chrisp74722975]

nope, enough presses on kill task on task manager batters it's way through eventually, seemingly like another nail in Adobe's coffin.

I have put all of the exclusions in place on the Exploit Protection to no odds.