In spite of the complaint it won within the United States and within the United Kingdom, Kaspersky is still one of the crucial main safety distributors for Home windows customers internationally, with its tool protective thousands and thousands of programs powered by way of Microsoft’s OS.
But it surely seems that a few of the ones whose computer systems have been working the Home windows 10 Fall Creators Replace and Kaspersky Web Safety 2018 had been hit by way of a trojan horse inflicting a Blue Display screen of Loss of life (BSOD) since previous this month.
BornCity finds that the problem first gave the impression previous this month when some customers complained of a BSOD on Home windows 10 construct 16299.98, which signifies that those programs have been working the newest model of the OS with cumulative replace KB4051963.
Cumulative replace now not at fault this time
Whilst in lots of instances cumulative updates are accountable for mistakes like this, it doesn’t seem to be the problem right here, as some mentioned identical downside is skilled on Home windows 7 SP1.
After additional investigation, it seems like the BSOD is brought about by way of classpnp.sys and klbackupdisk.sys (Kaspersky Labs quantity clear out driving force), with the mistake extra steadily prompted when working browsers like Mozilla Firefox and Google Chrome. There’s no trend right here to breed the trojan horse, and the BSOD presentations up at random instances for no transparent explanation why.
Whilst neither Microsoft nor Kaspersky launched a remark at the trojan horse to recognize it, a beta patch already appears to be to be had, regardless that it calls for to be manually put in by way of those that need to give it a check out. This isn’t clearly probably the most handy way to repair a crucial workaround, however having a beta patch is a sign that Kaspersky is having a look into solving this downside within the close to long term.
Despite the fact that there’s no phrase on when the patch may well be launched, it seems like the model you must be in search of is 18.zero.zero.405(e), because it’ll be the primary one to incorporate the patch and connect the BSOD factor.