Our code in setenvvar.bat tries to dynamically determine the correct MSVC runtime libraries to include in the packages.
This code has worked fine for several years and several versions of Visual Studio (2017, 2019 and 2022 for nine minor releases). Unfortunately it was based on an assumption that is no longer true with the release of VS2022 v17.10.
There does not appear to be a 'correct' way to determine the library version to use and the value is hard-coded in vcvars.bat.
It would seem that the best temporary solution is to also hard-code this until a newer release of VS2022 breaks the code again.
Our code in setenvvar.bat tries to dynamically determine the correct MSVC runtime libraries to include in the packages. This code has worked fine for several years and several versions of Visual Studio (2017, 2019 and 2022 for nine minor releases). Unfortunately it was based on an assumption that is no longer true with the release of VS2022 v17.10.
There does not appear to be a 'correct' way to determine the library version to use and the value is hard-coded in vcvars.bat.
It would seem that the best temporary solution is to also hard-code this until a newer release of VS2022 breaks the code again.