I have a computer that will not boot and is displaying the error "File:windowssystem32driverswrkrn.sys" on windows 10 OS. All searches point to an error with WebRoot. How do I fix this issue?
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
although it wasn't that low, the WRKrn.sys file was cleared to 0 bytes. System wouldn't boot. System repair repeatedly said that it can't find anything wrong but it couldnt fix the problem.
SourceForge boot-repair-disk "repaired" the boot sector far enough to show, on the next attempted boot, that the file WRKrn.sys was missing or corrupted.
I copied the correct file from another computer and the system booted properly.
Now it's time for Webroot to fix this problem. Please.
tnx for all advise I can get! /Anders
P.S. 0 free disk space was because of excessively large WRData folder (40GB).
When can we expect a permanent solution?
I am an IT Consultant, Microsoft Partner and an MSP utilizing Continuum as my platform. I just spent an hour and a half troubleshooting the workstations at one of my clients. To save some time (as I have a spent a lot of it on this issue already), I am going to paste in the information I sent to Continuum. This issue is causes some real problems and potential damage to workstations. Thank you.
Microsoft has found that the Webroot driver wrkrn.sys is causing reboot issues when an update is being installed during reboot on Windows 10. Clients are experiencing a black screen with spinning white dots that never resolves without a forced reboot via holding down the power button. When running a fltmc.exe command on machines experiencing the issue, we find that WRkrn appears twice:
Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
wcnfs 0 409900 1
WRkrn 329998.99 <Legacy>
MBAMProtector 3 328800 0
WRkrn 6 321611 0
Microsoft believes this driver is the issue and Webroot seems to have a knowledge base article potentially confirming this issue: https://community.webroot.com/t5/Product-Questions/windows-system32-drivers-wrkrn-sys/m-p/287006#M4830 - Microsoft points out that the altitude for the first instance of the driver should not be followed by a decimal amount.
I need a solution to this issue as the forced reboot could be causing damage to the workstations and their hard drives.
We are still experiencing the issue on a few systems here and there...
Easy enough to fix but the end user freaks out...
We're aware of this issue and have been working hard to find the cause. For background, WSA re-writes it's kernel driver every so often. We do this just in case the current driver file has been tampered with or corrupted in some way. However, there are occasions where Windows is doing something that inteferres with this process. We've got a solution but this is all kernel driver work and we're taking very cautious approach with our QA. Once it's ready for release, we'll get it out to you all.
Senior Product Manager
Why is this happening?
Is there a better way to fix this since it is happening to so many systems?
Is there a way to prevent this?
Reboot the computer.
Note: First copy the wrkrn.sys file from the working computer to the Hiren's boot usb key
Are there any other suggestions that I could try before doing these two steps?
If you're still experiencing the issue after this build update, I recommend you open a ticket so our support team can get the right information escalated up.
My process was having to boot to a recovery CD to get command line then do:
BCDBoot c:Windows (was actually K: for us, but wherever your windows install is)
After this, system tried to boot but I got the WRkrn.sys error.
Booted to CD again and deleted the file.
System is now back online.
Am currently running 22.214.171.124.
But what causes it, and what can be done to prevent it?
the alternative is to boot from a bootable win10 setup usb/cdrom.
and proceed to click on the "REPAIR" instead of setup. Then you'll be able to select an advance method to boot in safemode with command prompt using the win10 setup. You can delete the file in question or replace/copy on the command prompt.