C++ x64 14.40.33810 is installed but after every windows update msvcp140.dll in system32 is reverted back to older version

Question

C++ x64 14.40.33810 is installed but after every windows update msvcp140.dll in system32 is reverted back to older version

Julien Maingon 20

For months now, every Windows update is reverting msvcp140.dll to an older version and breaks A LOT of our applications.

I'm getting really tired of this situation, I have better things to do than reinstalling the new C++ version on 50 computers every month.

A lot of people reported this issue since the beginning of this year and nothing is done, Microsoft seems completely blind to this issue.

Please do something about this quickly !

Damon Pieres 5 Reputation points

2025-09-23T00:07:51.81+00:00

I've been getting this issue badly over the last two cumulative updates. Its breaks multiple apps and is causing instability across our Windows environment.
Deepak Behera 0 Reputation points

2025-10-14T13:41:48.67+00:00

Hi ,

We’re encountering a recurring issue during image deployment where msvcp140.dll reverts to an older version, causing disruptions. Even after downloading an image from the Azure Marketplace, updating it with VC++ 14.44.35211.0, and deploying it to an endpoint with the required components, the DLL version unexpectedly rolled back to 14.13.26020.0 following multiple reboots.

In our testing, repairing the VC++ redistributable has helped stabilize the msvcp140.dll version. Even after several reboots, the DLL remains intact and does not revert. However, this issue is currently blocking the FSLogix service and preventing us from updating to the latest FSLogix version.

We request Microsoft’s assistance in resolving this, as it’s impacting our deployment pipeline and service reliability.
Eric L 0 Reputation points

2026-05-13T22:11:48.7766667+00:00

For anyone else looking for answers. In my case, it was a particular Canon driver: Canon iR-ADV C5500s-P1 PSV1.0US. What I found was that after every Windows update the driver would do a full reload of it's oemsetup.inf file. Inside that file I found it was calling to a DriverStore folder which contained those old versions of VC++ files. For me the folder was: C:\Windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_7dee6c3b0ef85038.

To test: I would make sure my VC++ files were the latest version by repairing from Control Panel. Then I was able to replicate the issue by first deleting the driver in Print Management. Rebooting and reapplying the .ini file in the folder above to kick off the process of overwriting the VC++ 2015–2022 files. I'd reboot and they would be the old versions again. I confirmed this by matching the time and date from the ones stored in DriverStore. The files in System32 matched exactly.

I have been trying to track this down for about 6 months now. I believe the root cause for me was a print server I used was still distributing the driver even though the printer associated with it was decommissioned and not being deployed via Group Policy. For some reason after Windows Updates, Windows would reload that .inf file. If anyone knows why let me know.

What I did to remediate was to create a PS script to look for that printer/driver, delete it and then delete the files in DriverStore\FileRepository. I then created another script to reapply the latest VC++Redist on all domain computers. I also ensured I manually removed it from any Print Server. I do not know why Windows allows a downgrade of these important files. It wreaked havoc on my environment for months!. Random app crashes, broken software (ADESK, Adobe), even presentation software.

Hope this helps.

3 answers

Your answer

Damon Pieres 5 Reputation points

2025-09-23T00:07:51.81+00:00

I've been getting this issue badly over the last two cumulative updates. Its breaks multiple apps and is causing instability across our Windows environment.
Deepak Behera 0 Reputation points

2025-10-14T13:41:48.67+00:00

Hi ,

We’re encountering a recurring issue during image deployment where msvcp140.dll reverts to an older version, causing disruptions. Even after downloading an image from the Azure Marketplace, updating it with VC++ 14.44.35211.0, and deploying it to an endpoint with the required components, the DLL version unexpectedly rolled back to 14.13.26020.0 following multiple reboots.

In our testing, repairing the VC++ redistributable has helped stabilize the msvcp140.dll version. Even after several reboots, the DLL remains intact and does not revert. However, this issue is currently blocking the FSLogix service and preventing us from updating to the latest FSLogix version.

We request Microsoft’s assistance in resolving this, as it’s impacting our deployment pipeline and service reliability.
Eric L 0 Reputation points

2026-05-13T22:11:48.7766667+00:00

For anyone else looking for answers. In my case, it was a particular Canon driver: Canon iR-ADV C5500s-P1 PSV1.0US. What I found was that after every Windows update the driver would do a full reload of it's oemsetup.inf file. Inside that file I found it was calling to a DriverStore folder which contained those old versions of VC++ files. For me the folder was: C:\Windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_7dee6c3b0ef85038.

To test: I would make sure my VC++ files were the latest version by repairing from Control Panel. Then I was able to replicate the issue by first deleting the driver in Print Management. Rebooting and reapplying the .ini file in the folder above to kick off the process of overwriting the VC++ 2015–2022 files. I'd reboot and they would be the old versions again. I confirmed this by matching the time and date from the ones stored in DriverStore. The files in System32 matched exactly.

I have been trying to track this down for about 6 months now. I believe the root cause for me was a print server I used was still distributing the driver even though the printer associated with it was decommissioned and not being deployed via Group Policy. For some reason after Windows Updates, Windows would reload that .inf file. If anyone knows why let me know.

What I did to remediate was to create a PS script to look for that printer/driver, delete it and then delete the files in DriverStore\FileRepository. I then created another script to reapply the latest VC++Redist on all domain computers. I also ensured I manually removed it from any Print Server. I do not know why Windows allows a downgrade of these important files. It wreaked havoc on my environment for months!. Random app crashes, broken software (ADESK, Adobe), even presentation software.

Hope this helps.

Answer 1

tpark630 5

This issue is not caused by Microsoft or Windows, it is caused by a third-party Fiery printer driver that is out of date. You notice it when Windows does a big cumulative update, because when Windows does a big cumulative update, it also reapplies your printer drivers. The Fiery printer driver relies on msvcp140.dll as a dependency, and so it makes sure that it has the dependency by installing it in the System32 folder. Unfortunately, it does this even if you already have the dependency, and it overwrites the version that's already there. And since the printer driver is out of date, it overwrites the dll with a version of the dll that's also out of date.

Search for Fiery printer driver overwrites System32 dll files to find discussions on this issue. Fiery has acknowledged it and released a fix.

The fix is to remove the old version of the Fiery driver, install version 7.3 or later, and then repair the Microsoft Visual C++ Redistributable installations.

Eric L 0 Reputation points

2026-05-13T22:22:59.2166667+00:00

Thanks for this! See above for what I discovered. But you are correct. For me it was an outdated print driver. A Canon driver. What is interesting though is the printer wasn't in use anymore. However the driver was still installed on workstations on my network.

What you wrote lead me down the path of searching for MSVCP140.dll everywhere on the C: drive. I figured it had to be coming from somewhere. I found it in the driver repository. In my case, that Canon printer driver. I found an exact match to what was being overwritten in System32. FWIW though, that particular printer/driver (Canon iR-ADV C5500s-P1 PSV1.0US) was used with a Canon printer using a Fiery we had long ago.

Answer 2

Hello,

I can confirm this issue is still occurring as of 12/21/2025. For now, our workaround has been to repair the C++ 2015-2022 x64 installation and then reboot the PC.

Is Microsoft aware of this and working toward a permanent fix? This has been ongoing for about 3–4 months, so it would be great to see an official patch soon. Considering upgrading to Win 11 25h2 to see if this issue is limited to 24h2. Keeps breaking after each windows update patch cycle, so looking forward to getting this resolved soon.

https://forums.autodesk.com/t5/revit-architecture-forum/revit-2026-install-corrupts-windows-11-explorer-crash-caused-by/td-p/13820617/page/2

https://community.adobe.com/t5/indesign-discussions/adobe-indesign-2026-won-t-start-on-windows/td-p/15591465

https://www.reddit.com/r/sysadmin/s/L3ITEozJCy

Answer 3

Quinnie Quoc 11,060 Independent Advisor

Hi,

We understand the frustration caused by repeated Windows updates reverting msvcp140.dll to an older version, resulting in application failures across multiple systems. This behavior has been reported by other users and is currently under review by our engineering teams.

The issue appears to be linked to how certain updates interact with the Visual C++ Redistributable libraries, particularly version 14.40.33810. As a temporary workaround, we recommend deploying the correct version of the redistributable via a centralized script or endpoint management tool to reduce manual effort across your 50 devices.

We also encourage you to submit detailed feedback through the Feedback Hub, which helps prioritize fixes based on impact and user reports. Your input is critical to driving improvements, and we appreciate your continued engagement.

If my answer is useful for you, please give it a vote.

Best regards,

Quinnie Quoc.

tpark630 5 Reputation points

2026-04-13T16:49:06.9033333+00:00

Your profile says that you are an independent advisor. Who is "our engineering teams"? You don't appear to be someone who can speak on behalf of Microsoft.

Share via

C++ x64 14.40.33810 is installed but after every windows update msvcp140.dll in system32 is reverted back to older version

3 answers

Your answer