Lightroom Classic: Bad Image error (McAfee antivirus)

  • 2
  • Problem
  • Updated 10 months ago
  • (Edited)
Lightroom Classic on Windows 10  version 1709
Yesterday LR Classic worked perfectly. Today it would not open and gave Bad Image error which said "C:\Program Files\Adobe\Adobe Lightroom Classic CC\CRClient.dll is either not designed to run on Windows or it contains an error.

I uninstalled Lightroom - restarted the PC and re-installed it and got the same error. On checking the offending file in Windows Explorer - CRClient.dll it was shown as containing 0 bytes.
I renamed it to CRCLient.old and copied the CRClient.dll from Photoshop CC2018. Lightroom then launched OK.
So two questions :
1. Why is an empty file being installed?
2. Will running the Photoshop version cause any other issues and if so - how do I install the correct version of this dll file

Dave
Photo of David Richardson

David Richardson

  • 87 Posts
  • 29 Reply Likes

Posted 11 months ago

  • 2
Photo of Bob Dunkley

Bob Dunkley

  • 8 Posts
  • 2 Reply Likes
The mystery of CRClient widens. This has been an issue with others, myself included. One “solution “ centres around Macaffee antivirus program.- apparently if you use MaCafee, then by disabling it before installing Lightroom and then enabling it afterwards and listing the CRClient in the file list of MaCaffee to ignore, then Lightroom works.
Photo of David Richardson

David Richardson

  • 87 Posts
  • 29 Reply Likes

Now that is interesting. I do have Macafee installed. It did not flag any errors during installation or on running - but I'll give what you say a try later today.
Strange thing is that CRClient.dll appears in several Adobe Cloud apps - albeit with different versions and te others are OK.  I'd be interested to know what version should be in the Lightroom folder (I copied v 1.6.1.0 from Photoshop to get it going)


Dave

Photo of David Richardson

David Richardson

  • 87 Posts
  • 29 Reply Likes

Plot thickens:

Later that evening I had another "bad.image" failure with Lightroom Classic. This time a different   .dll set to zero bytes.

I ran another full virus scan - with McAfee and with Malwarebytes. No issues were found.

So I wondered whether I was having SSD issues - although it would be unusual for that to affect the same application in the same way after two installations which would write to a different part of the SSD. Also no other applications have shown issues. Samsung S.M.A.R.T. showed no issues, an error check on the disk also showed no issues.

 

So I reinstalled, this time from the direct download link (previous two installs were from the CC desktop app). So far today I have seen no issues.

 

Dave

Photo of Pete Green

Pete Green, Customer Advocate

  • 710 Posts
  • 134 Reply Likes
How's it still going for you David? No issues after the uninstall/reinstall?
When you did the uninstall/reinstall, did you disable McAfee or Malwarebytes?

Regards
Pete
Photo of David Richardson

David Richardson

  • 87 Posts
  • 29 Reply Likes
Hi Pete - it is still working.
The first uninstall / re-install via the CCdesktop app failed.

The second I uninstalled via the desktop app but re-installed via the link in "My Account".. Whether that makes any difference in terms of the image or the process, I don't know. What I do know is that it is still working .
I did not disable the virus checkers during the installation, that would have been my next step.

One other bit of info which may help - the .dlls that went to 0 bytes also had a time shown on them matching the crash time - not the installation time or the original creation time. Almost as if something broke those files on Lightroom startup.

Someone else just replied to the post on the user forum - with the same issue - so I may not be alone in this.

Dave
Photo of Pete Green

Pete Green, Customer Advocate

  • 710 Posts
  • 134 Reply Likes
Thanks for the added detail David. Glad to hear you're up and running successfully currently. 

Do let us know if you have further questions or trouble.
Regards
Pete
Photo of David Richardson

David Richardson

  • 87 Posts
  • 29 Reply Likes

I have come back to update this as I believe I finally isolated the problem.

 

A few days after having the Lightroom issues I had a similar problem with Techsmith's SnagIt. Dll files were being set to zero bytes.

I ran various virus scans, McAfee, Malwarebytes and HitManPro which showed nothing. Finally, I uninstalled my normal antivirus software ( Mcafee ). All the problems stopped.  After a few days I re-installed Mcafee and the problems started again.

 

So now I have replaced my McAfee antivirus with BitDefender and have experienced no issues since.

 

I hope that may be useful to anyone else who experiences similar issues.

 

Dave

Photo of Bob Dunkley

Bob Dunkley

  • 8 Posts
  • 2 Reply Likes
I have finally had enough!! Now my Lightroom 2015 is affected by the "Bad Image" API. Thus I uninstalled my McAfee A/V and installed Kaspersky instead and so far no problems. There seems to be a bad mis-match between McAfee and Lightroom judging from the replies to this thread. I'm waiting and hanging on to my Lightroom 2015 before I upgrade, in the hope that Adobe may address the bugs that are currently plaguing their product.
Bob
Photo of David Richardson

David Richardson

  • 87 Posts
  • 29 Reply Likes

Hi Bob

I think the issue is with McAfee not Adobe. In my case the "Bad Image" problems were first seen on Lightroom but I then got the same issues on Techsmith's SnagIt.  Replacing Mcafee with Bitdefender resolved both.

Dave