[Osgeo4w-trac] [osgeo4w] #876: saga 9.7.1-1 fails to start (MSVCP140.dll error)

[OSGeo4W]

#876: saga 9.7.1-1 fails to start (MSVCP140.dll error)
------------------------+----------------------------
Reporter:  andreaerdna  |       Owner:  osgeo4w-dev@…
    Type:  defect       |      Status:  new
Priority:  critical     |   Component:  Package
 Version:               |  Resolution:
Keywords:               |
------------------------+----------------------------
Comment (by andreaerdna):

 Why GRASS-GIS and SAGA-GIS (and other ones) executable don't use the
 msvcp140.dll shipped by OSGeo4W with the msvcrt2019 package (shouldn't it
 be named msvcrt2022)? Is there a way to enforce the use of the one shipped
 by OSGeo4W instead of the one installed in the system (apart from copying
 the msvcp*.dll in the same folder of the executable)?

 It looks like on some Windows 10 versions also pdal_wrench.exe
 https://github.com/qgis/QGIS/issues/61222 and untwine.exe
 https://github.com/qgis/QGIS/issues/61222#issuecomment-2760570138 have the
 same issue also disrupting the Point Cloud functionalities in QGIS.

 The msvcp140.dll 14.32.31332.0 in my system32 folder has the creation and
 last modified date June 10th, 2022, and it was almost certainly installed
 by the latest Microsoft Visual C++ 2015-2022 Redistributable (x64) -
 14.32.31332 installed in my system.

 If there is no way to enforce the use of the one shipped by OSGeo4W
 instead of the one installed in the system, then maybe the Setup program
 should check the msvc version installed in the system and either trigger a
 newer version installation or warn the user, or maybe a note should be put
 in the Windows download page about the minimum msvc version needed for
 Windows 10/11.
-- 
Ticket URL: <https://trac.osgeo.org/osgeo4w/ticket/876#comment:3>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.