P: 6.x crashes in the facial recognition module

What did you rename? There is no file named "ibfrsdk-8.6.0.dll" only a file called "libfrsdk-8.6.0.dll"...

And what do you mean by "FR still works"? We've seen that existing FR-tags are processed fine but it's FR attempts on new faces that crash LR 

Yes, face recognition still works.

This might not be a license expiry... If I look at the file date of the DLL that seems to cause the problems ("libfrsdk-8.6.0.dll"), I see 12 Dec 2017 (which is a few days before the release date of LR 6.14 I could find BTW: 19 Dec 2017).

Now I also think that the date LR started to fail on us is 9 Dec 2020.

If I think software and programming... suppose they used an integer to somehow calculate the offset between the DLL date and now. Max integer size is 2^16 (65536), suppose these were minutes.

If I subtract that exact amount of minutes from the 'fail date' 9 Dec 2020, I get 12 Dec 2017 (the file date of the DLL). Coincidence? Or a programming error? Define the variable as LONG-type integer and our problems might disappear.

Is the face recognition still working after renaming the file? Or does it simply inactivate the functionality?

I just renamed the file -ibfrsdk-8.6.0.dll to -libfrsdk-8.6.0.dll and LR 6.14 works now without crashes.

Hey. Is there any other software I can change - without monthly fees?

Thanks!!! I had just fired up LR6.14 (on MacOS Mojave) for the first time since Dec 14 and it crashed while importing a batch of new pics. Then immediatly crashed within seconds of being opened, again and again. After trying a few things, rolling back to an older/empty catalog worked, but any attempt to import new pics got me back to square one before the import finished.

With the tip above I changed the date to Dec 1, 2020, opened the catalog with the imported pics (no crash!), updated the catalog preferences *not* to perform face detection on import, restarted, and things now look fine.

In Lightroom, go to Help, then click on System Info.  The first two lines state:

Lightroom version: 6.14 [ 1149743 ]
License: Perpetual 

@Rikk This is NOT an issue of a needed update.  This is an issue stemming from Adobe's negligence in planning and preparing for their own license problems with Google Maps and the maker of the facial recognition software.  These issues should have either been addressed by Adobe's planning for (or absorbing) the cost of those licenses/rights on the front end such that the cost was incorporated in the product cost I paid OR Adobe should have clearly provided advanced warning to their perpetual licensing customers that certain major functionalities of the software they were being would cease to work on specific dates.  I will not rent software from Adobe but I WILL pay a lawyer to research whether Adobe is liable or not for knowingly selling PERPETUAL licenses for software that will have major functionalities disabled on future dates known to the company (but not disclosed to the end user).

I concur with some of the other posts addressing the possible grounds for a class action lawsuit.  I  bought my PERPETUAL license for the same reason as many other of you did: I resent being forced to rent software.  I paid for a PERPETUAL license with the understanding that the software would perform certain functions PERPETUALLY.  Because the company sold a PERPETUAL license to me, I believe Adobe's issue with their license for the facial recognition software ending is their problem, not mine!  (They should have planned for this and incorporated whatever cost would need to address the eventuality in the product cost).  While Adobe should have addressed these issues on the front end, it is relevant to note the EULA does not indicate certain functions of the software will cease to operate as of certain dates.  To date, two major functionalities (mapping and facial recognition) no longer work... but not due to any issue on the end user's side.  Having bought a perpetual license, I expect to be able to use the full functionality of MY software for as long as it meets my needs.  Disabling an end-user's ability to utilize a functionality they paid for is criminal.  It IS the equivalent of the manufacturer of your paid-in-full car coming to your house and removing the interior seats (and doing so without your knowledge).