Fix #8251 No artifacts produced from windows builds since VS 2022 was upgraded to v17.10

Author: reevespaul

builds/win32/setenvvar.bat

@@ -108,11 +108,22 @@ for %%v in ( %* )  do (
 :: suggest them.
 :: This has been tested on VS 2017, 2019 and 2022
 :: Note that VCToolsVersion is only defined after vcvarsall.bat been run.
+
 @if defined VCToolsVersion (
   set MSVC_RUNTIME_MAJOR_VERSION=%VCToolsVersion:~0,2%
+  set MSVC_RUNTIME_FILE_VERSION=%MSVC_RUNTIME_MAJOR_VERSION%0
+rem NOTE 1 Since the upgrade to VS 17.10.5 this attempt to set the runtime minor
+rem version is broken as it now returns '4'. Note also that vcvars.bat has v143
+rem hard-coded. It does not seem to be possible to dynamically derived the minor
+rem version using the available env vars so we test to see if the runtime dir
+rem exists and if not we fall back to 3.
+rem NOTE 2 This code is likely to break again in the future !!!!
   set MSVC_RUNTIME_MINOR_VERSION=%VCToolsVersion:~3,1%
+  if not exist %VCToolsRedistDir%%VSCMD_ARG_TGT_ARCH%\Microsoft.VC%MSVC_RUNTIME_MAJOR_VERSION%%MSVC_RUNTIME_MINOR_VERSION%.CRT (
+    set MSVC_RUNTIME_MINOR_VERSION=3
+  )
   set MSVC_RUNTIME_LIBRARY_VERSION=%MSVC_RUNTIME_MAJOR_VERSION%%MSVC_RUNTIME_MINOR_VERSION%
-  set MSVC_RUNTIME_FILE_VERSION=%MSVC_RUNTIME_MAJOR_VERSION%0
+
 )
 @echo.