MSDK2021R1.exe crashes with 0xC0000374 (STATUS_HEAP_CORRUPTION)

[Jeremy-Tess]

Looks like there's some problem with the installer, which means it won't install once VS2022 is installed. I can reproduce this problem in a container too:

https://docs.microsoft.com/en-us/visualstudio/install/build-tools-container?view=vs-2022

COPY MSDK2021R1.exe "C:\MSDK.exe"
---> Using cache
---> 35fc6060f3db
Step 35/37 : RUN "C:\MSDK.exe" install --output=msdk.log --eula=accept
---> Running in 65a8961b0e53
The command 'cmd /S /C "C:\MSDK.exe" install --output=msdk.log --eula=accept' returned a non-zero code: 3221226356 

Even working around this, it doesn't seem easy to consume in a C++/CLI project with other third party dependencies since libmfx_vs2015.lib is only supplied as a static library built with /MT. This makes it conflict with other dependencies:

error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MD_DynamicRelease'

While it's possible to work-around this too, is there any chance Intel would consider making the Media SDK available via vcpkg? It would be way easier and much more flexible for Windows devs to consume than via the current pre-builds.

[Gopika_Intel]

Hi,

Thank you for posting in Intel Communities.

Q: Looks like there's some problem with the installer, which means it won't install once VS2022 is installed.

A: Please try downgrading the Microsoft Visual studio to 2017 to make use the features of Intel Media SDK. We were able to install Media SDK while the Visual studio 2017 is already installed.

You can download the older versions of Microsoft Visual studio from here: https://visualstudio.microsoft.com/vs/older-downloads/

Please let us know whether you’re able to install media SDK with Visual Studio 2017.

Q: While it's possible to work-around this too, is there any chance Intel would consider making the Media SDK available via vcpkg? It would be way easier and much more flexible for Windows devs to consume than via the current pre-builds.

A: We are checking this with the internal team, we will get back to you as soon as we get an update from them.

Regards

Gopika

[Jeremy-Tess]

Hi Gopika,

Thanks for your reply!

I'm afraid I'm unable to use an older version of Visual Studio due to dependencies on other frameworks. Similarly, I'm not sure that using a 5 year old IDE would be a reasonable workaround for a lot of users.

Thanks for forwarding to the internal team about vcpkg. There's a few other Intel libraries supplied that way, so fingers crossed. It would really make a lot of problems go away just ditching the prebuild installer entirely and just supporting vcpkg.

Kind regards,

Jeremy

[Kevin_O_Intel1]

Hi Jeremy,

Support for the latest frameworks is being developed for our newer products. We recommend that you try OneVPL. 

Let us know if you have any questions!

Kevin

[Pamela_H_Intel · Accepted solution]

Hello,

Please transition to the oneAPI Video Processing Library (oneVPL). Our developers are focused on increasing the functionality for oneVPL, the successor to Media SDK. oneVPL enables the best features of both integrated and discrete GPUs for encoding, decoding and processing frames.

If you need help transitioning please ask.

Pamela