I've been facing a persistent issue with several applications failing to launch due to an MVC140.dll error following routine Windows updates. This happens with programs like CAD, C3D, Adobe InDesign, and Chaos Enscape. Initially, we tried repairing the Microsoft Visual Redistributable 2015-2022 on users' machines, but it feels like we're doing this way too often. To make things easier, we set up a script to reinstall the necessary x64 C++ versions automatically.
However, I'm looking for a more permanent solution to this problem, rather than just relying on automated scripts after each patch. Additionally, with Microsoft transitioning towards Rust, I'm curious about how this will impact software like CAD, Adobe products, and various rendering applications. Has anyone else experienced this issue, and found any better solutions than periodic script runs?
2 Answers
I totally get where you're coming from. We've been dealing with similar MVC140.dll errors too, and it seems like a never-ending cycle of fixes. Our software provider is supposedly 'looking into it,' but so far, nothing permanent. I created a script to keep the x64 and x86 versions updated, but it’s a hassle since I have to update the download URL every time a new version is released. We've considered scheduling this script to run after the patching process, but with over 400 workstations, it feels risky! What if a new version causes more issues? It just feels like we're stuck in a loop of updates and repairs.
I hear you loud and clear! This has been a problem since last October, and the Adobe community is in an uproar over it. Admins have to keep repairing those distributables every time Microsoft or Adobe rolls out an update. It's definitely frustrating, especially in larger departments that rely heavily on Adobe and CAD software.
Exactly! We've been doing the same thing—reinstalling the Visual Redistributables every time there's an update is such a pain. It gets old fast. I wish there was a more stable fix.