30 replies

I have not come across WSA as the cause of this and would suggest that you check out this thread from the MS Support Forums, on this subject to see if it is of any help.

If you have tried temprarily shutting down WSA and find that the crashes stop then you can try an uninstall/clean reinstall of WSA to see if a faulty installation my have been causing the issue. If you want to try that then please follow the steps below closely!

Make sure you have a copy of your 20 Character Alphanumeric Keycode! Example: SA69-AAAA-A783-DE78-XXXX

KEEP the computer online for Uninstall and Reinstall to make sure it works correctly

I got around this on several Windows 10 machines with Webroot installed by going into Device Manager , right-click HID Keyboard Device, select properties, then the Driver tab, then click 'Roll back driver'.

It is possible that Windows 10 will reinstall the driver due to Microsoft update policy preventing you from disabling problematic drivers, but so far it hasn't happened to me.

It will create the following registry key:
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetserviceswrkrncompat]
"Enabled"=dword:00000006

The system WILL require a reboot for the change to be applied fully. If the issue persists, please check if the registry key was successfully created, in some cases the agent may need to be shut down in order for the key to be applied. For these cases I have included the manual method below.

To apply the fix please follow the steps below:

1. Please download the following Zip file:http://download.webroot.com/CompatibilityFlag.zip
2. Locate the SecureAnywhere icon in your system tray.
3. Right-click the system tray icon and select "Shut down protection." (You may need to adjust your policy to allow Webroot to be shut down manually via the tray icon. This is under "Basic Configuration".
4. A prompt confirming whether you want to shut down appears. Click Yes.
5. Depending on your settings, you may have to complete a CAPTCHA for confirmation as well.
6. Import CompatibilityFlag.reg from the .zip by double clicking on the file.
7. Reboot the machine after confirming the import.

this is bloody annoying cos even with the registry patch workaround, somehow 5 pc's in the office (using ms keymo) were working fine then somehow a win update came around then bsoded with kbdclass.sys and corrupted the wkrnl.sys rendering the pc unable to boot.

After restoring wkrnl.sys, reboot was slow, then proceeded to bsod with kbdclass.sys again! This time i pulled out the wireless ms dongle reapplied the patch via a vnc session! but still bsoding after the reboot!

got frustrated and replaced all of the 5 ms keymouse with a logitec one and are now humming nicely!

We've been hit by this bug again thanks to the Windows 10 anniversary update. I've discovered that installing the update, the registry key for Webroot compatibility mode was removed. It was present before I updated my computer, and the policy had compatibility mode enabled. Once updated, it was no longer there.

I tried refreshing the configuration, but this did not recreate the key. I created they key manually (as detailed earlier in this thread) and rebooted, and this fixed it for me.

We have a base of around 30 machines, all using Windows 10 and Microsoft wireless keyboard and mice. I've created a GPO that ensures the compatibility registry key is present and replaces it if it gets removed for any reason - hopefully this will cover machines taking the anniversary update in the future.

"Hi Daniel,I concur with Brad, customers who can address their own wireless keyboard BSOD by applying the fix offered in the noHold article is the best first step. If customers are unable to resolve the issue on their own for whatever reason should contact support so that our trained team can assist further.Thanks,

I am getting this BSOD before I can shut down WSA protection.
I think that typing in the captcha is triggering the BSOD.
So it's kind of a catch22 situation.
what to do?
What if I use a different keyboard? Will I have to disconnect the MS keyboard wireless dongle?

So glad I checked the boards out, because this happened to me overnight. I sure hope there will be a fix soon because using the plug in kb is driving my crazy. It is so small. I did try the fix but I can not get it to work for me.

I recently started have the Driver IRQL not less than equal BSOD. I too have the MS wireless keyboard. So the fix is to remove the dongle and use a differed (wired) keyboard? What comes next? Is there some fix or patch so I can go back to my wireless keyboard?

The issue you are having with Webroot and your wireless keyboard has been reported to the Webroot Development team and they are working on a fix.

In the meantime, we do have a workaround you can utilize to modify some of Webroot's settings to switch the way we monitor keyboard activity on your device. This should prevent this issue from reoccurring until our fix is available.

To apply the workaround, please follow the steps below:

1. Please download the following .zip file: http://download.webroot.com/CompatibilityFlag.zip
2. Locate the SecureAnywhere icon in your system tray.
3. Right-click the system tray icon and select Shut down protection.
4. A prompt confirming whether you want to shut down appears. Click Yes.
5. Depending on your settings, you may have to complete a CAPTCHA for confirmation as well.
6. Import CompatibilityFlag.reg from the .zip by double clicking on the file.
7. Reboot the machine after confirming the import.

I appreciate the attempt of giving this fix bt it did not work with my Microsoft 2000 wireless keyboard/mouse. I have purchased a different AV software and the kdbclass.sys blue screen problem is gone. Faster start ups too. I was happy with Webroot for a couple of years. But W10 Anniversary did it in.

@ wrote:
I was happy with Webroot for a couple of years. But W10 Anniversary did it in. Why blame Webroot for the issues that Microsoft Caused? I'm a Microsoft Windows Insider MVP and Unbelievable how others have had issues and some even worse but Webroot is always fixing these issues.

Cookie policy

Cookie settings

We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.