in all fairness, there is a workaround which is downgrade to an early version MR0.
if they didnt care about it, they would have not come out clean.
It is important to give credit where is deserved and in this case it is deserved, regardless how long will it take for a fix to be deployed.
Choosing to deploy the fix in 2017 version (where Kaspersky historically releases their "next year" version sometime half way through the year) is a good move instead of a rush and not properly tested fixed for next patch instead.
There would be a different wordaround: install a beta version of Patch C which it seems is available yet in the beta/test server, and then revert to standard update servers, this could fix the problem, but these days only working with laptop (KES10) and can't confirm/test it.