Hello anonymous user-5396
That is a likely explanation, I have experienced same Exception codes when running some specific security softwares, in my case from FSecure, but since the DLL is from Microsoft the statement in your reference link makes complete sense:
"This is done intentionally to prevent DLL injection by malware. I don't think there's a reasonable workaround though. To work your injected DLL must be a part of the UWP package. And if so, the app may not be approved for inclusion into the Windows Store. The last one is just a guess. I'm not a Microsoft employee. Additionally I don't know if it would work cross-UWP-apps either."
I would try to sandbox into a clean and isolated VM (just in case) with all security disabled to see if it can make any change.
Hope this helps with your query,
--If the reply is helpful, please Upvote and Accept as answer--