ImportError: A dynamic link library (DLL) initialization routine failed after building source with Visual Studio 17.10 about onnxruntime HOT 8 CLOSED

does it persist if you revert the change?

from onnxruntime.

One workaround I found is like the following: copy DLLs from C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Redist\MSVC\14.40.33807\onecore\x64\Microsoft.VC143.CRT to my conda environment C:\Users\%USERNAME%\.conda\envs\my_env to overwrite existing DLLs.

Note that installing latest VC Runtime does not work (the downloaded VC Runtime is older than the one installed with latest Visual Studio).

from onnxruntime.

does it persist if you revert the change?

Yes, I encountered the issue before the change.

from onnxruntime.

conda uses old vc runtime and it is not compatible with new visual studio compiler. You can run "conda install conda-forge::vs2015_runtime" to upgrade your vc runtime version in conda.

from onnxruntime.

One workaround I found is like the following: copy DLLs from C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Redist\MSVC\14.40.33807\onecore\x64\Microsoft.VC143.CRT to my conda environment C:\Users\%USERNAME%\.conda\envs\my_env to overwrite existing DLLs.

Note that installing latest VC Runtime does not work (the downloaded VC Runtime is older than the one installed with latest Visual Studio).

Or just delete the DLLs in conda's directories.

from onnxruntime.

Faulting module name: MSVCP140.dll, version: 14.29.30153.0, time stamp: 0x653aa208

In theory this should work ... Could it be a different issue?

from onnxruntime.

Oh, @tianleiwu, when you build the code you need to add "--use_binskim_compliant_compile_flags" to your build command, otherwise the changes in #21005 wouldn't take effect. It was because I asked the author to scope the change to a smaller scope that wouldn't effect most people.

from onnxruntime.

Adding --use_binskim_compliant_compile_flags solved the issue.

from onnxruntime.