WRkrn.sys Blue Screen: How to Fix This System Error

A Webroot app update is efficient for many users

Reading time icon 3 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Key notes

  • WRkrn.sys is a driver used by Webroot SecureAnywhere and manages the software’s kernel-mode components.
  • If the driver triggers a BSoD, you may reset your computer as a last resort.

The WRkrn.sys driver is a kernel-mode driver used by Webroot SecureAnywhere, and it may sometimes trigger a Blue Screen of Death (BSoD) error.

However, the fixes are not always complicated. So, in this guide, we have put together some easy-to-follow steps to rid your computer of the blue screen error.

What causes the WRkrn.sys BSoD?

  • Corrupted or outdated WRkrn.sys – Outdated drivers are the main culprits for BSoD errors like the one caused by WRkrn.sys.
  • Conflict with another driver – There are chances that the WRkrn.sys driver is conflicting with other drivers on your computer.
  • Hardware problem – If your computer’s hardware is not working properly, it can cause the driver to fail and trigger the stop code.
  • An outdated antivirus – If you use an outdated version of the Webroot antivirus, chances are that associated drivers are outdated and will trigger this issue.

How do I fix a wrkrn.sys BSoD?

Before exploring any complex fixes, we recommend you run a virus scan to ascertain the BSoD is not triggered by malware, restart your computer, and uninstall conflicting apps, which will most likely be other third-party antivirus programs.

1. Reinstall the Webroot antivirus

Note icon NOTE
This solution applies only if you installed the Webroot antivirus.
  1. Press Windows + R to open the Run dialog.
  2. Type apwiz.cpl and hit Enter.
    wrkrn.sys
  3. Click on the Webroot antivirus from the app list and select the Uninstall button.
    wrkrn.sys
  4. Follow the wizard to complete the process, navigate to the official website to get a new copy, and install it.

Our readers reported that reinstalling their Webtroot antivirus fixed the issue, so if you’re in the same situation, use the solution above.

Note that on rare occasions, you may need to boot into Safe Mode to execute the uninstallation.

2. Rename the WRkrn.sys file

  1. Press the Power button to start the computer, and once you see the Windows logo, press and hold the Power button to shut down. Repeat this step a few times till you are redirected to the Automatic Repair screen.
  2. There, you have to click on the Advanced options.
    wrkrn.sys
  3. Choose Troubleshoot, then click on the Advanced options.
  4. Click on Startup Settings.
    wrkrn.sys
  5. Click on the Restart button.
    wrkrn.sys
  6. Press the F4 key to get into the Safe Mode.
  7. Navigate to the path below:
    C:\Windows\System32\drivers
    wrkrn.sys
  8. Search for WRkrn.sys and rename it to WRkrn.sys.old.
  9. Finally, reinstall the app like in Solution 1.

3. Reset the PC

Note icon NOTE
This step will mean you lose most of your data and should be done only as a last resort.
  1. Boot into Safe Mode using steps 1 to 6 of Solution 2.
  2. Press Window + I to open the Settings app.
  3. On the right pane, click on Recovery.
  4. Click the Reset this PC option.
    wrkrn.sys
  5. Select Keep my files to save as much as possible from the old installation (If the problem persists after a reset, you may redo the process but select Remove everything rather).
    wrkrn.sys
  6. Follow the onscreen prompts to complete the process.

If you have tried the above steps and are still getting the WRkrn.sys blue screen error, you may need to contact Webroot support for assistance.

That is all we will cover in our guide. While we have not written these solutions in any particular order, we recommend trying a reset as a last resort since you may lose all your data.

We also have a guide that focuses on solving aswhdske.sys Blue Screen problems, so be sure to visit it.

Please reach out to us using the comments section below and let us know what worked for you.

More about the topics: BSoD errors