Deadlock in Schannel on ARM64 Windows during DecryptMessage

Question

We have this bug-report:

https://bugreports.qt.io/browse/QTBUG-98106

Whose stack trace indicates that calling DecryptMessage may deadlock in Schannel on ARM64 Windows 11 installs.

I'd like to know if it's a known problem or if the stack trace would indicate a problem in our code.

The bug report is a little light on info, but it's also all I have to go on for now.

Thanks for any answers,

Mårten

Answer 1

I advise you either contact the Microsoft support or open start and search for feedback and open the Feedback Hub app and report this issue.

Answer 2

Hi there,

The Deadlock Detection option of Driver Verifier, along with the !deadlock kernel debugger extension, is an effective tool for making sure your code avoids poor use of these resources. Deadlock Detection is supported only in Windows XP and later versions of Windows.

A deadlock is caused when two or more threads come into conflict over some resource, in such a way that no execution is possible.

You can use the below link to get detailed steps and try them
https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/deadlock-detection
https://learn.microsoft.com/en-us/windows/win32/secauthn/decryptmessage--schannel

---------------------------------------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer--