Is anyone else seeing recurring endpoint problems where a Windows update causes the Microsoft Visual C++ v14 x64 Redistributable to stop working or revert to an older DLL version? Afterward, applications such as Power PDF fail to launch or crash, and repairing the latest redistributable immediately fixes them. What could be causing the regression, and how are you tracking it down?
4 Answers
It may be worth checking update and installer logs to determine whether the redistributable is actually being removed, damaged, or simply overwritten. Also verify which update ran immediately before the failure; a consistent pattern can narrow down the culprit. Keeping Windows feature versions controlled may reduce unexpected changes, but it won’t fix a third-party driver that reinstalls old DLLs.
Check the version of MSVCP140.dll before and after the failure, then search the usual program folders and the Windows driver store for older copies. For example, PowerShell can search for the DLL and display its file version. Comparing the versions often reveals that a printer or other hardware driver is supplying the outdated runtime.
In our environment, the redistributable itself wasn’t the real problem. An older EFI Fiery printer driver was being reapplied after updates and was replacing newer Microsoft Visual C++ runtime DLLs with older copies. That broke LibreOffice, Adobe applications, and other programs. Updating the printer driver and removing the obsolete package from the DriverStore stopped the recurring repairs.
We had the same issue with EFI drivers, especially affecting Autodesk and Adobe software. Updating the driver fixed it.
Some EFI packages bundle an old VC runtime, and updates can trigger printer-driver reinstalls. The driver can cause the regression even when the printer queue isn’t actively being used.
I’ve seen this repeatedly with Adobe InDesign users. Repairing the newest Visual C++ redistributable restores the application, but it’s better treated as a temporary fix while you identify which update, driver, or management policy is putting the old runtime back.
Some newer Windows releases are enablement packages rather than full reinstallations, so version pinning alone may not explain every case.