Windows 10: Bad Image Error on CONCRT140.dll

Discus and support Bad Image Error on CONCRT140.dll in Windows 10 BSOD Crashes and Debugging to solve the problem; I've been trying to open some of my Adobe Creative Cloud Apps Photoshop, Illustrator, After Effects but I keep getting a Bad Image Error whenever I do.... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Jo Litzenberger, Aug 24, 2020.

  1. Bad Image Error on CONCRT140.dll


    I've been trying to open some of my Adobe Creative Cloud Apps Photoshop, Illustrator, After Effects but I keep getting a Bad Image Error whenever I do. The error itself however says that it is CONCRT140.dll that's acting up. After looking for answers online, I tried reinstalling the programs, doing an sfc scan, a malware scan, and a system restore though it only gave me the option to go back to the last major update, but to no avail.


    Bad Image Error on CONCRT140.dll 9c1ba4fa-689f-4b1c-b805-b25013c175b5?upload=true.jpg

    :)
     
    Jo Litzenberger, Aug 24, 2020
    #1

  2. CONCRT140.DLL

    how do i repair c:\windows\system32\CONCRT140.DLL file?
     
    AprilThe Queen, Aug 24, 2020
    #2
  3. CONCRT140.DLL

    Hello AprilThe,

    First of all, thank you for posting your question with us. I am an Independent Advisor, and I am happy to assist you.

    Please, follow this Microsoft Support link to help you to repair c:\windows\system32\CONCRT140.DLL file.

    https://answers.microsoft.com/en-us/windows/for...

    Thank you very much.

    Best regards,

    Vladimir
     
    Vladimir Palacios, Aug 24, 2020
    #3
  4. Camera Win User

    Bad Image Error on CONCRT140.dll

    Bad Image Errors - dll files changing to 0 bytes

    Hi
    Have an unusual problem (to me anyway)

    Last week I got "Bad Image" errors with Adobe Lightroom (the program had worked OK previously). Two .dll files were listed as corrupt and in Explorer both were shown has having 0 bytes size. Re-installation resolved the problem.
    Today I have had the same "bad image" error with another program. Techsmith SnagIt. Once again it was .dll files and they show in explorer as 0 bytes. The timestamp on the 0 byte dlls is the time of the error i.e. today (not when the files were installed).

    What I've done so far :
    Ran McAfee viruscan across all disks - no problems reported.
    Ran Malwarebytes - no problems reported

    Went to the properties for the disk drive and under "Tools" ran error check - nothing found
    The disk is an SSD so I went to Samsung Magician which shows drive condition as good and S.M.A.R.T. shows wear levelling count at Current Value 99. I do not use Rapid Mode.

    The problems are happening on a Samsung 850 Evo 500GB

    Any suggestions welcome

    Dave
     
    Camera, Aug 24, 2020
    #4
Thema:

Bad Image Error on CONCRT140.dll

Loading...
  1. Bad Image Error on CONCRT140.dll - Similar Threads - Bad Image Error

  2. vccorlib140.dll Bad Image Error

    in Windows 10 Gaming
    vccorlib140.dll Bad Image Error: I keep getting this error, it's really annoying. I've been trying to fix it by uninstalling Visual Studio 2015 and 2017, then reinstalling them, as I've seen in other answers, but every time I install Visual Studio 2017x86 the 2015 ones disappear from Control Panel. The other...
  3. vccorlib140.dll Bad Image Error

    in Windows 10 Software and Apps
    vccorlib140.dll Bad Image Error: I keep getting this error, it's really annoying. I've been trying to fix it by uninstalling Visual Studio 2015 and 2017, then reinstalling them, as I've seen in other answers, but every time I install Visual Studio 2017x86 the 2015 ones disappear from Control Panel. The other...
  4. Bad Image MSVCP140.dll and VCRUNTIME140.dll

    in Windows 10 Installation and Upgrade
    Bad Image MSVCP140.dll and VCRUNTIME140.dll: Hi, For the past week I have gotten a lot of bad image messages. At first it was with my adobe programmes, and it seemed to be every single dll wasn't working. I have my adobe programmes on another laptop so I deleted them all from this laptop and didn't have any other...
  5. Missing concrt140.dll, can't use Plex

    in Windows 10 Network and Sharing
    Missing concrt140.dll, can't use Plex: Hello, I've had an issue with a dll missing that was causing issues with Origin and my Logitech software, after uninstalling visual c++ 2019 and 2017 from my computerafter lots of trial and error and having to use this install/uninstall program, I went ahead and got it...
  6. CONCRT140.DLL

    in Windows 10 Network and Sharing
    CONCRT140.DLL: how do i repair c:\windows\system32\CONCRT140.DLL file? https://answers.microsoft.com/en-us/windows/forum/all/concrt140dll/9590dc9f-0129-4a57-9adc-1f7ea69e1893"
  7. Bad Image MSVCP120.dll and MSVCP140.dll with ERROR 0xc000012f

    in Windows 10 BSOD Crashes and Debugging
    Bad Image MSVCP120.dll and MSVCP140.dll with ERROR 0xc000012f: Bad Image MSVCP120.dll and MSVCP140.dll with ERROR 0xc000012f with several .exe files - acrobat, HRBlock, icloudservices, etc. This is a Windows 7 machine that was updated to Windows 10....
  8. Bad Image – MSVCP140.dll error

    in Windows 10 BSOD Crashes and Debugging
    Bad Image – MSVCP140.dll error: I recently updated to the latest version - windows 10 1809 - and now this is the message I get when I try to open the third party softwares I had(about 10 of 'em) ; Windows Warning: Bad Image – MSVCP140.dll not designed to run on Windows. ... C:\WINDOWS\SYSTEM32\MSVCP140.dll...
  9. Bad image and .dll errors

    in Windows 10 BSOD Crashes and Debugging
    Bad image and .dll errors: I keep getting bad image, dll errors, and I'm unable to download anything. Originally I thought this was because of an update so I used the fresh start ability to restart everything and I still get the same errors. Could anybody help diagnose my problem?...
  10. Bad Image Errors - dll files changing to 0 bytes

    in Windows 10 Support
    Bad Image Errors - dll files changing to 0 bytes: Hi Have an unusual problem (to me anyway) Last week I got "Bad Image" errors with Adobe Lightroom (the program had worked OK previously). Two .dll files were listed as corrupt and in Explorer both were shown has having 0 bytes size. Re-installation resolved the problem....