Petr Kovalev

Hello James! We got this stack trace in one of our products on a call to JsonConvert.SerializeObject(). I assume the certificate is the root cause. I've added Newtonsoft.Json.dll assembly signing...

Important note, it was reproduced on Windows 11 24H2, not reproduced on Windows 10

Find out that the issue was actually caused by a call to [SetProcessMitigationPolicy](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-setprocessmitigationpolicy) with enabled flag MicrosoftSignedOnly in [PROCESS_MITIGATION_BINARY_SIGNATURE_POLICY](https://learn.microsoft.com/en-us/windows/win32/api/winnt/ns-winnt-process_mitigation_binary_signature_policy). So there is no issue with the current Newtonsoft.Json.dll signature.