C:\\WINDOWS\SYSTEM32\VCRUNTIME140.dll file corrupted daily.

[chris_1067]

Hey guys, Adobe uses Microsoft Visual Studio C++ 2015-2022, and in it there's a file called VCRUNTIME140.dll. Daily when we have users across our organization open up Adobe, we get an image that pops up that says "C:\\WINDOWS\SYSTEM32\VCRUNTIME140.dll is either not designed to run on Windows or contains an error". Error status 0xc0000020

When we repair Microsoft Visual Studio C++ 2015-2022, Adobe is able to work again for one day. We've uninstalled and reinstalled the C++ suite, all adobe apps, rand sfc /scannow repeairs, ran DISM image repairs, and still no success. Have you guys seen this ticket come up yet and do you have more solutions than what we've tried?

[Anshul_Nautiyal · Accepted solution]

Hi @chris_1067,

Thanks for reaching out. The error involving VCRUNTIME140.dll and the repeated corruption suggests a deeper system or software conflict beyond just Adobe or the Microsoft Visual Studio C++ redistributables. Here are some detailed steps to help you troubleshoot and resolve this issue:

Corrupted Visual C++ Redistributables:
Even after repair or reinstallation, a conflict or system process may corrupt the DLL again.

Completely uninstall all versions of Microsoft Visual C++ Redistributables. Ensure that you have installed both the x86 and x64 versions for 2015, 2017, 2019, and 20221. Sometimes, having all versions installed can resolve compatibility issues.

Check for Windows Updates: Make sure your Windows operating system is fully updated. Sometimes, missing updates can cause compatibility issues with system files.

Check for Third-Party Conflicts: Malware or third-party applications can interfere with critical system files. Run a full system malware scan with tools like Microsoft Defender or Malwarebytes.
Temporarily disable antivirus software to test if it’s causing conflicts.

Replace the DLL File: If the issue persists, you can try manually replacing the VCRUNTIME140.dll file. Download the correct version from a trusted source, and replace the existing file in the C:\WINDOWS\SYSTEM32 directory. 

Create a New User Profile: Sometimes, user profile corruption can cause issues with system files. Try creating a new user profile and see if the problem persists when using Adobe applications under the new profile. 

Check event logs (Event Viewer > Windows Logs > System) for recurrent errors related to the DLL or C++ redistributables.

Consider creating a clean system image for testing purposes.

Restrict Access to the DLL:
To prevent potential overwrites:

Navigate to *C:\WINDOWS\SYSTEM32* and locate VCRUNTIME140.dll.
Right-click > Properties > Security tab > Edit permissions. Remove write permissions for all non-essential users/groups.

Driver and Software Updates: Outdated drivers or software can trigger system conflicts.

Update all drivers (use tools like Driver Booster or go to your hardware manufacturer's website).
Ensure Windows and Adobe applications are fully up-to-date.

Alternative Temporary Workaround
Instead of repairing the C++ Redistributables daily, try replacing the corrupted VCRUNTIME140.dll with a known good version: check out this link. 

Copy the file from a working machine with the same version of Windows and Redistributables.
Replace the corrupted file in C:\WINDOWS\SYSTEM32 and C:\WINDOWS\SysWOW64.

Clean Uninstall and Reinstall: Perform a clean uninstall and reinstall of Microsoft Visual C++ Redistributable. Then, uninstall all Adobe apps using the CC Cleaner Tool. Reboot the system.

Log in as administrator. Reinstall the software

Can you please also let us know how many people are affected by this issue? Is it for all users in your organization, or is it specific to some users? If it is isolated to some users, the above steps should help resolve the issue.

Refer to this guide for missing DLL issues: Adobe Missing MSVCP110.dll. 

I hope this helps! If you need further assistance, feel free to ask.

Regards,
^AN

[chris_1067]

Hey Anshul, commenting for anyone researching this issue, what seemed to work for us was to change ownership of the vcruntime140.dll file to an admin account, and to take away all write permissions of the file for all other users and groups on the device. The file is no longer getting corrupted, and so it seems that the file was being written into and preventing this has resolved. 

[Anshul_Nautiyal]

Hi @chris_1067,

Glad to hear the issue is resolved! Thanks for sharing your solution and updating us—this will definitely help others facing the same problem. Appreciate your contribution!

Let us know if you have any additional queries in the future.

Regards,
^AN