Disclaimer: I'm clueless. They claim that there's basically no way to fix this (it's a consequence of the design of some features, Atoms). But as far as I und

Disclaimer: I'm clueless. They claim that there's basically no way to fix this (it's a consequence of the design of some features, Atoms). But as far as I understand they have to call the (undocumented, according to the blog) NtQueueApcThread function. a) What guarantees are given for undocumented API methods in Windows? I know Microsoft tries hard to make everyone happy, to be backwards compatible. But - even for stuff like this? b) For AV solutions: Wouldn't this undocumented call be a somewhat decent marker?