2005 release of VC runtimes incorrectly detected as outdated revision of current

[Fragbert]

The visual c++ runtimes from MS are distinct releases grouped by year as separate and different programs. Many are required for older programs and games and do not run using current year versions (aka "2015-2022" v14.x).

After MS released to the general public the latest v14 version of the runtimes v14.44.35.211 under the "2015-2022" moniker - PatchMyPc incorrectly detects the latest 2005 v8.x version as an outdated "2015-2022" build. Again, many users maintain an up to date library of 2005, 2008, 2012, 2013, *and* 2015-2022 runtimes where each of these versions have separately maintained revision forks.

[Omar (Patch My PC)]

Can you test now please?
Also, is this an ARM machine?

[Fragbert]

Can you test now please?
Also, is this an ARM machine?

Still there, this is a traditional x64 system, not an ARM machine.

[Omar (Patch My PC)]

Sorry for the late reply!
How about now?

[Fragbert]

Fixed, thank you sir!

[jvidal]

Unfortunately it's not fixed, today PMPc is detecting VC++ 2013 v12.0.40664 as an "outdated" version of VC++ 2015-2022 (which currently is 14.50.35710, but PMPC thinks it's 14.44.35211.0).

[jvidal]

well?

[Omar (Patch My PC)]

How about now? It should be fixed.

[jvidal]

seems to be fixed, but microsoft visual C++ 14 / 2015-2022 just doesn't appear at all in the list.

[Omar (Patch My PC)]

seems to be fixed, but microsoft visual C++ 14 / 2015-2022 just doesn't appear at all in the list.

Well, that just means it is not installed

[jvidal]

wrong, they are installed. I don't know if you now, but they changed the name from "Microsoft visual C++ 2015-2022" to "microsoft Visual C++ V14" from version 14.50.35710 on

[Omar (Patch My PC)]

This is the latest stable version from their official download links.