Forum Discussion
Microsoft Visual C++ Redistributable rolling back or getting corrupted after every Windows Update.
Hello! So I'm having an issue where multiple users would create a ticket stating they can't access AutoCAD, InDesign, and even sometimes even File Explorer. Now this part is an easy fix, just uninstall/reinstall or repair the Microsoft Visual C++ Redistributable and the issue is fixed. The problem I'm having is that a few days later, the same users would create another ticket with the same issue. I've been going back and forth uninstalling/reinstalling, when a user (that was having this issue before, and I had fixed) brought up that they were able to access AutoCAD fine, until they did a Windows Update and rebooted. Sure enough, I remoted into their PC and their Microsoft Visual C++ Redistributable wasn't updated to the v14. I first contacted AutoCAD and they did some digging and stated the same thing, that the Visual C++ was being rollback. Then I contacted Microsoft and they had me go to Windows support which then they guided me here. So I'm presenting my question here now, anyone else had this issue, and is there a solution to this fix? Thanks!
13 Replies
We finally figured out a fix for our environment. And thanks to "@ahmed_masoud97" for the reminder to post back here. Hope it helps.
We run Xerox EX-i C9065-70 printers with EFI Fiery Controllers. For some reason, Fiery added code in earlier versions of their print driver that overwrites MSVCP140.dll with an older version that they use in their software. I think in our case, Fiery reverts it to like 14.13.something.
There is a very informative thread over at EFI's forums discussing this: https://communities.fiery.com/s/question/0D5QU00000jFvpW0AS/some-applications-failed-after-windows-updates-dlls-for-msvcp140dll-and-related-became-corrupt-caused-by-fiery-printer-driver-does-someone-recognize-this Highly recommend reading through it.
For us, we have to remove the printers from the end users computers, manually clean out the old driver packages, and then reinstall the printer using the latest build of the print driver. Removing the print drivers can be challenging, but installing the new version is handled by Windows Server print services. (nice and easy).
We are currently using Fiery Driver Version 7.03.001.0
Fiery Server version 1.0_SP2
The reason we were looking at Windows Updates is probably the same reason as everyone else on here. This only happens around Patch Tuesday. Windows updates MSVCP140.dll to version 14.51.36231.0 then Fiery would promptly revert it.
You can also verify in Control Panel -> add remove programs. The version number is listed next to the C++ Redistributable line item.
I am seeing the same issues with Hp Smartstream and Adobe Indesign, has there been any update to this. We have to fix visual C++ every month
Good day
our oganization is also having the same issueWe checked the event logs and error comes up is AP/exception/code: 0xC0000005
AP/exception/text: ACCESS_VIOLATION
AP/exception/module_name: MSVCP140.dll each week a repair or reinstall of C++ V14 64bithas there been any solution to this
Error I get is AP/exception/code: 0xC0000005
AP/exception/text: ACCESS_VIOLATION
AP/exception/module_name: MSVCP140.dllBefore repairing any package, enable Windows Installer verbose logging for one affected test machine and reproduce the next update/reboot cycle. The log and MsiInstaller events will identify the exact product code and action that removes or supersedes the runtime. With that evidence, you can target the responsible deployment/update configuration instead of repeatedly repairing every Visual C++ package after Patch Tuesday.
This is very disruptive to productivity across our office, and is still happening several months since.
This has been happening in our organization for months now. It's so bad that after Patch Tuesday, we just assume that any issue we hear about is caused by this and this is our first troubleshooting step. Would be nice if this gets addressed somewhere.
This may not be Windows Update directly corrupting the Visual C++ Redistributable. Similar cases have traced the problem to outdated printer or application drivers that are reapplied after Windows Update and overwrite msvcp140.dll with an older version.
Check the affected DLL’s version and timestamp before and after patching, then search the DriverStore for an identical copy. Pay particular attention to older Fiery, Canon, or Ricoh printer drivers. Updating or removing the responsible driver, followed by repairing the latest x86 and x64 Visual C++ Redistributables, has resolved this pattern in reported cases.
Did you ever get an answer? My vc_runtimeMinimumx86.msi cannot be found and I'm sick of seeing the error.
All - the same thing is happening to us - would love if there are any solutions out there.
Windows Update might be rolling back or removing certain Visual C++ Redistributable versions to maintain system stability or due to conflicts.
