M

2 Messages

 • 

88 Points

Sat, Dec 12, 2020 6:47 PM

Lightroom Classic: version 6 crashes in the facial recognition module

Since a week my Lightroom crashes when opening the facial recognition modul. Program closes. 

I am working with Windows 10. 

I do not know. Mayby it has something to do with the latest Windows Update: 8. Dezember 2020 – KB4592438 (Betriebssystembuilds 19041.685 und 19042.685

Or it has something to do with the Installation of Photoshop Elements 2021 / Adobe Premiere Elements 2021

189 Messages

 • 

4.6K Points

10 m ago

When I purchased (bought and paid for) LR6 it was for a Perpetual version. It would be interesting to debate the definition of the word “Perpetual” against the expiration of the license of the face detection dll.

189 Messages

 • 

4.6K Points

10 m ago

Let me approach this from another perspective. When Adobe was still selling V6.x as a "Perpetual" product, they knew the face detection module already had a built-in expiration date?

If they were aware, or not, they owe us at least an updated DLL. Trivial work I would assume. Except for us having to manually install it. Although, Adobe could easily make a patchFace.exe to replace the outdated DLL. But that would require them to go the extra mile for their customers. Not generally an Adobe path.

TML59

48 Messages

 • 

548 Points

Yes, Adobe must have known that the DLL had an end date for the license. At that time they probably ignored it was 10+ years later: who would still use the old software. end 2020..? That changed of course when they stopped selling the perpetual license as that created a large user-group (us) that now had no real choice anymore other than to stay with the last version (6.14).

Yes, the least they could and should do is ensure we can still use their software. I'm not a lawyer so I don't know if they are legally required to help us. What I'm hoping is that Adobe looks at this and helps us (as -again- this might be quite easy to fix). They are big enough not to notice the change but many users would be very happy.

And as said before: if they'd bring a new LR also as perpetual I'd buy immediately. I'll never pay a yearly fee for a few pictures I process however.   

189 Messages

 • 

4.6K Points

FYI - the creation date in the properties box of the DLL is 2017.

3 Messages

 • 

80 Points

10 m ago

I just deleted the C: \ Program Files \ Adobe \ Adobe Lightroom \ CIT folder and lightroom stopped crashing. I cannot recognize new faces, but I can manage faces already recognized and can manually point and name new faces.

TML59

48 Messages

 • 

548 Points

That is not a solution as face recognition does not work anymore when you do this!

7 Messages

 • 

122 Points

Solution accepted by whom? I understand that it is a proposal from a user. Earlier they told us an unacceptable official response of "this product will receive no additional updates". Is Adobe who gives us these answers? They are very little serious.

Champion

 • 

6K Messages

 • 

103.7K Points

I don't know in this particular case, but often posts providing workarounds are marked as "accepted solution" to make sure they're at the top of the thread, rather than buried below.  This forum platform doesn't appear to have any way to pin a post to the top other than by marking it as "accepted solution" or "official answer".

In this case, it's very important for LR 6 users to know how to stop LR from crashing. Obviously, it's only a partial workaround, since it doesn't restore the use of face recognition.  

3 Messages

 • 

90 Points

10 m ago

It not only crashes when detecting faces, it crashes when I create a virtual copy. Face detection is turned off. WTF Adobe?

3 Messages

 • 

80 Points

I had the same problem. A face was probably detected in this photo. Delete detected faces (and face marks) and you will be able to create / delete a virtual copy. You can also delete the CIT folder and Lightroom should no longer crashes. You can also change the date to e.g. 12/06/2020 and that should fix it too.

5 Messages

 • 

110 Points

Ran also in the "virtual copy" issue, when the date hasn't been set back before 12/9/20. There are certainly other situations where the face detection DLL initialization issue occurs. Therefore I just renamed the CIT folder to CIT.buggy (just in case Adobe should graciously provide a fix - hope is the last to die). "Manual" face recognition still works, but the annoying LR crashes are gone...

3 Messages

 • 

90 Points

10 m ago

Rick from Adobe said "This thread is being merged into an authoritative thread for better tracking and response".

Where can we follow the outcome and the plan to resolve?

Champion

 • 

6K Messages

 • 

103.7K Points

When the conversations got merged, you were automatically added to the follow list for the merged conversation (here).  

2 Messages

 • 

70 Points

I also having issues with my Lightroom crashing with face recognition and occasionally now when deleting photos.  Running Mac with Mojave.  

Steve Coates

3 Messages

 • 

82 Points

Does the issue also exists in older version of Lightroom 6? 6.14 and 6.10 are impacted. What about the 6.0 version? Unfortunately I don't have an older version and cannot try it.

A changed system date before Dec 2020 prevents Lightroom to crash, but face recognition still doesn't work. Same happen when setup a complete new catalog.

TML59

48 Messages

 • 

548 Points

I'm sure it impacts earlier versions as well (I do recall however that Face recognition was only added later.. probably in 6.0?).

Also, if you have a v6.x, you can and should always update to the latest (6.14 I think). That is still possible.

(edited)

10 Messages

 • 

154 Points

The problem exists with 6.0 and 6.14. I have both versions installed on 2 macs. 

I hope there will be a solution soon as face recognition is oen of the features I bought LR 6 for (after having had LR 4 and LR 5). So PLEASE, Adobe: help your loyal customer base who cannot afford (or does not want tp pay) a monthly fee, especially after having paid hundreds of Euros/Dollars in the last years...

2 Messages

 • 

70 Points

10 m ago

Yesterday I discovered that by opening LR6 in win 8 compatibility mode (with full administrative grants) the face recognition function worked properly one more time. The side effect is LR6 became obviously less responsive and fast (and it wasn't so fast running on Win10). Anyway, is it confirmed that 1) the system PC date has to be changed to november (for eg), 2) open LR, 3) change the system PC date to the correct one, 4) face recognition is ok and pictures are stored with the correct information into the catalogue? Thanks

2 Messages

 • 

70 Points

10 m ago

I wrote a quick shell script that seems to work well enough for MacOS. Surely someone more into software development could improve upon this. I haven't fully tested it to see if there are weird side effects, but I can open Lightroom and switch to the People (O) module without the immediate crash that I've been experiencing.

#!/bin/bash
sudo date 1111111118
open -a "Adobe Lightroom"
sleep 30
sudo ntpdate -u time.apple.com

(edited)

4 Messages

 • 

96 Points

@MattD 

To follow up, here is a batch file I wrote for Windows 10 (untested, but should work on earlier systems).

REM LIGHTROOM LAUNCHER TO ENABLE FACIAL RECOGNITION
REM VERSION 1
REM 2020-12-28

REM UNFORTUNATELY ADMINISTRATOR ACCESS IS REQUIRED TO CHANGE THE SYSTEM TIME

ECHO OFF
ECHO THIS BATCH FILE MUST BE RUN AS ADMINISTRATOR TO WORK
ECHO RIGHT CLICK FILE AND RUN AS ADMINISTRATOR
ECHO THIS FILE SHOULD LAUNCH LIGHTROOM WITH FACIAL RECOGNITION CAPABILITIES REENABLED
ECHO YOU MUST OPEN THE FACIAL RECOGNITION TOOLBOX BEFORE THE CLOCK IS CHANGED BACK
ECHO OR LIGHTROOM WILL CRASH
ECHO ONCE THE FACIAL RECOGNITION TOOLBOX IS OPENED IT CAN BE CLOSED AND REOPENED AT WILL
ECHO IN THE CURRENT LIGHTROOM SESSION

REM THESE ARE THE COMMANDS TO CHANGE THE DATA
REM FEEL FREE TO CHANGE THESE, I JUST WANTED TO MAKE IT OBVIOUS
REM THAT THE DATE HAD CHANGED
ECHO CHANGING TIME TO 11:11:11 ON 11/01/2020 FOR COMPATABILITY
time 11:11:11
date 11/11/2011
ECHO DATE CHANGED

REM CHANGE THIS FILE PATH AS NEEDED, THE FORMATTING NEEDS TO REMAIN THE SAME
ECHO STARTING LIGHTROOM
start "" "C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe"

REM CHANGE THIS TIME TO ALLOW LIGHTROOM PLENTY OF TIME TO LOAD FOR YOU
REM AS WELL AS TIME TO OPEN THE FACIAL RECOGNITION TOOLBOX
ECHO PAUSING TO ALLOW LIGHTROOM TO PERFORM CHECKS
TIMEOUT 60

REM THIS IS THE COMMAND TO RESYNC THE CLOCK WITH INTERNET TIME
ECHO RESETTING CLOCK TO PROPER TIME
w32tm /resync
TML59

48 Messages

 • 

548 Points

Thanks, obvious and similar to an earlier post (but well documented, thanks).

I'm not sure what turning back time will do with Windows but I'm reluctant to apply this. The other option reported here is to remove the FaceRecognition folder but that will stop the recognition module from working.

Both are possible approaches but let's all agree that these are NOT solutions to the problem but -at best- workarounds. Therefore, I hope that Adobe will still take it's responsibility and fix this small problem once and for all.

(edited)

4 Messages

 • 

96 Points

I agree, I was just trying to take what we'd learned to make something that people could use to allow for maximum use of the product in the easiest way possible without having to intentionally remove functionality.  I've seen no issues with changing the time in windows, and this only changes the time for 60 seconds.  I'd recommend not copying files anywhere or making files during that minute, otherwise some of the created or modified dates could get a bit wonky.

This is definitely a workaround I wish I didn't have to use, but I'm finding more and more things starting to fail without it (not sure if it is a consistent bug, but now I'm getting lightroom crashes when trying to remove a missing photo from the catalog).

TML59

48 Messages

 • 

548 Points

OK, so the intention is just to be able to disable the FR engine? I'm sorry I didn't get that. Please realize that if one stays in LR (for hours) the FR will work as the failing DLL will sense a date before Dec 12th.

So yes, as a quick fix this is a good solution but it can be used to continue to use FR during a LR session that is always fixed in time as well (I think)

4 Messages

 • 

96 Points

Sorry, no I think I've explained poorly, this is just trying to automate the date workaround, not disable anything. (Unless I'm misunderstanding what you're saying)

I haven't tested anything with LR running for a long period of time, so I don't know if the FR DLL checks the date periodically (though, I suspect it wouldn't).  If it does, then this is not a great workaround for many people's use cases.

Anyway to make it clear, this just resets the date prior to opening, so if the FR module is opened with the old date it should work (for an unknown period of time), then it resyncs the computer's time back to present.

I really just made this for myself and decided to share in case it helps others keep this program running for them for longer.

6 Messages

 • 

120 Points

10 m ago

@everyone: It's great to find such discussions. The workaround by changing the system date works fine for me. I would never have found a workaround like this without your help!

@windows users: to make it a little bit more convenient:
I wrote a batch file to change the date, start lightroom, wait a few seconds and then resync the date. As the date commands need to be run as admin I chose a second workaround startin the batch via link.

1. create a batch file:

date 01-12-18
timeout /t 2
start "" "C:\Program Files\adobe\Adobe Lightroom\lightroom.exe"
timeout /t 30
w32tm /resync

(perhaps you have to change the path in the line start ....!)

2. create a link to this batch on your desktop

3. right click on the link, properties, advanced, tick run as admin

4. Start Lightroom by using this link!

Works fine for me. Nevertheless it isn't fully tested. Use at your own risk ;)

(edited)

6 Messages

 • 

110 Points

Thanks for the batch file, which for me (LR 6.14, Win10)

- avoids crashing but

- does not enable face recognition on actual photos

TML59

48 Messages

 • 

548 Points

That is odd... As far as some users in this group could test setting the system date to a time before December 2020 should fix the problem.

6 Messages

 • 

120 Points

Strange ... I just tested it once again ... works fine for me ...

Maybe try this one: Start Lightroom via the batch (run as admin). Switch to face recognition view (o) before the second timer expires. Then once again try to import photos with faces.

It seems to me, that the face recognition has to be activated once while the date is still changed to the past.

10 Messages

 • 

154 Points

@Smiffi 

Seems like a great workaround but I am a Mac User. Is there anybody who can provide a similar "solution" for Mac users?

Or should I manually set the date to 2019, start Lightroom, start a face recognition task in a small folder (in order to avoid a long process), rechange the system date to automatic and then proceed working in Lightroom 8as the face recognition won't check the date again when starting it for a second time within the same Lightroom session?). What do you think?

Can this create trouble with 

2 Messages

 • 

70 Points

@wildf see my post earlier in the thread for a bash script that runs on OSX

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-v610-crashes-in-the-facial-recognition-modul/5fd510567288d52d004c42d6?commentId=5fe241ad60effe0dfb54941f

(edited)

2 Messages

 • 

70 Points

10 m ago

It is official.  Adobe will not be fixing anything.  We have to live with it like it is, or upgrade to the $9.99 a month model (which I can't do because I am on widows 8 and not 10.  Only windows 10 supports the LR Classic version.  Here is the Petapixel article breaking the news.

https://petapixel.com/2020/12/24/adobe-lightroom-v6-is-falling-apart/

TML59

48 Messages

 • 

548 Points

Thanks for the update. Pity to hear that Adobe won't help us. I read the comments @ petapixel and I hope things will remain more on topic and not personal here... I also get the impression that in that other forum there are more (semi-)professionals participating (who might be able to afford this better).

That leaves us here without Adobe helping us regretfully (and I'm sad to have to admit that I'm not surprised). I see two options ahead: we get the original DLL owner company to patch their DLL or we find a software guru who can patch the existing DLL.

Wrt Win8 vs Win10 I'm different: I don't think we can ask Adobe to change LR6 itself because the world changes. There will come a time when LR6 simply won't work anymore and I can understand that at that time things will end. It's impossible for Adobe to update old code, no company does that. This discussion is about compatible code with a time-'block' in a separate 3rd-party DLL. I think that CAN be fixed.

5 Messages

 • 

110 Points

I'd be highly interested what a lawyer would say about Adobe's point of view. They sold a perpetual license to an end user (does anybody have the 6.14 license documents?), period. If their code contains either stuff like Google's Map interface which changed the charging model or a 3rd party DLL with an expiration date, that's Adobe's (design) problem (in the past), not the end user's (he has bought a perpetual license). So the core question is, what's meant w/ "perpetual" in terms of the 6.14. license agreement.

Usually (i.e. with other software vendors), when you buy a perpetual license, you are allowed to use it perpetually (as long as there exists hardware and an operating system supporting this software); you may eventually run out of support, that's fine. Hardware and operating system can be handled by the end user (as long as the hardware does not fail, spare parts are available and an OS copy exists). All that is not Adobe's business.

But any time bombed DLL or changing business modell underneath the software (Google) ist definitely Adobe's problem. I assume that all these issues were well known while LR 6 was released.

Then Adobe sales changed the business model from perpetual to subscription, forgetting the "bombs".

If the perpetual model would have "survived", these problems whould have been fixed by any LRnext release. That's Adobe's problem: not communicating what won't work in the future, update to a 6.15 release w/ changed terms/conditions or removing the features officially! What will be next?

Changing business models does not discharge a software vendor from his old both parties legally binding terms and conditions. They are currently loosing alot of reputation and confidence.

So far this is only speculation what Adobe's obligations are, therefore I'd be highly interested in LR 6(.14) license documents. That's legally binding regardless of what Adobe or anybody else is writing in an article. Unfortunately I haven't found them online yet... 

Champion

 • 

6K Messages

 • 

103.7K Points

Here's the license agreement I found in my installation of LR 6.14 / Mac OS:

https://www.dropbox.com/s/vkz7dg5nqabmn24/lightroom-6-license.html?dl=0 

The word "perpetual" doesn't appear anywhere.  Of course, it's written by lawyers to try to avoid as much legal liability as possible.  Section 6 limits the warranty to 90 days, with the exception of Germany and Austria (section 14), which is 1 or 2 years.  And of course, how it actually gets interpreted (or ignored) by courts varies greatly by country, state, and province. 

Interestingly, paragraph 14.8.1 explicitly allowed Adobe to "discontinue" the availability of Google Maps.

3 Messages

 • 

80 Points

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

Lightroom version: 6.14 [ 1149743 ]
License: Perpetual 

5 Messages

 • 

114 Points

10 m ago

Not fixing built in expiration of functionality is completely unacceptable.  From the dictionary, perpetual means "never ending or changing".  Removing capability or placing time limits is the complete opposite of perpetual.  Adobe should step up and support the many users that purchased the "perpetual" version thinking that functionality would continue to function.  If not, they will lose many, many users. 

189 Messages

 • 

4.6K Points

Only a class action lawsuit will get Adobe's attention.

3 Messages

 • 

80 Points

10 m ago

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).

22 Messages

 • 

280 Points

I would join up, perhaps on a "Go Fund Me" effort to get a legal firm to start a class action lawsuit. 

I purchased Lightroom starting with LR2 going through to v6.14.  I have invested  a lot of time and money into my catalogue including facial recognition.  I was happy with 6.14 running on Win10, and now I am pissed really Adobe!  Adobe sold us all a poisoned product knowing the DLL would stop working.    This is immoral and those sitting on the Board or Directors should be made to make amends. 

3 Messages

 • 

80 Points

10 m ago

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

3 Messages

 • 

84 Points

10 m ago

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

6 Messages

 • 

120 Points

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

3 Messages

 • 

84 Points

Yes, face recognition still works.

(edited)

TML59

48 Messages

 • 

548 Points

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 

1 Message

 • 

60 Points

@Ich Anonym I cannot found this file on mac 

3 Messages

 • 

84 Points

Sorry for the typo, the correct name of the file is of course "libfrsdk-8.6.0.dll".
Unfortunately, the FR then only works for previously imported photos.
For newly imported photos the indexing for FR does not work anymore. Unfortunately, you have to do without the FR.
But I can at least continue working without crashes with this workaround.

TML59

48 Messages

 • 

548 Points

10 m ago

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.

(edited)

TML59

48 Messages

 • 

548 Points

Also found a "libfrsdk-8.7.0.dll" somewhere on the Internet... I'll see what I can do with that file (it's a gamble, but I have to try something)

Champion

 • 

6K Messages

 • 

103.7K Points

I think you've made an arithmetic error:

2^16 mins * 1 hour / 60 mins * 1 day / 24 hours ~~ 45.5 days

TML59

48 Messages

 • 

548 Points

Yep, sorry... my bad ;-)

(it's 2^10 hours more or less but that is probably a coincidence...)

(edited)

189 Messages

 • 

4.6K Points

Maybe a dll from a Lightroom CC installation with the exact same name would work? You would likely have to unregister the old 3.x dll and then register the latest CC dll.

6 Messages

 • 

110 Points

Has someone tried this solution ?

10 Messages

 • 

150 Points

10 m ago

Try to change your system date, last year for instance. Everything works then. It's an obvious obsolescence program. They need to be prosecute for that

10 Messages

 • 

150 Points

here 's an apple script that works on big sur

on run {input, parameters}
	
	set ntpdPID to do shell script "systemsetup -getusingnetworktime; exit 0" with administrator privileges
	if ntpdPID is "Network Time: On" then
		do shell script "systemsetup -setusingnetworktime off" with administrator privileges
		do shell script "systemsetup -setdate '01:01:2020' -settime '12:00:00'" with administrator privileges
	else
		do shell script "systemsetup -setusingnetworktime on" with administrator privileges
	end if

	
	tell application "Finder"
    	activate application "Adobe Lightroom"
	end tell
	
	delay 10
	
	do shell script "systemsetup -setusingnetworktime on" with administrator privileges
	
	return input
end run

3 Messages

 • 

80 Points

Hi

My LR 6 crashes when I Delete an image; so I flag as I edit then hit delete, crash, reload, hit delete, crash, etc; after about 5 or so iterations, the delete is complete and I can carry on with the next LR cleanup.  Thinking of producing a simple index via Excel.  Then when the day some IT geek in Corporate Land decides on scrambling the code in Excel, I propose to reinvent a card index and enjoy my dotage sorting. If libraries have done it successfully for a couple of hundred years, then so can I.

Chin up in LR6 land!

TML59

48 Messages

 • 

548 Points

The crash is caused by the face recognition bug. There is hope this (the face recognition bug) will be addressed soon and that will solve the crash on delete problem.