Thx Jim for your very educational post ;)
I went through all the files you have listed and found them all in my Vista setup. In fact I found more 😃 in the directory C:WindowsSystem32drivers
Please see in the picture below (in the red rectangles). There is a lot of WSA remnant sys files. They are not all displayed. I made just an example. They are all over across the directory. Hovering over them gives WSA build number, so I noticed they indeed belong to the old WSA builds.
http://i43.tinypic.com/synyvt.jpg
I should add that I never was forced to use the randomize installation.
The clean uninstall of WSA + cleaning temps, registry etc. using CCleaner doesn't remove them. So can you provide a tool which would be capable to remove them? Something like Norton has its removal tool. If not I would have to go the file by file to check if it is really WSA remnant or not. Unfortunately as you can see the files are named very oddly so it is hard to filter/separate them.
Should I be concerned or ... ?
Thanks & regards,
pegas
Solved
Extra Webroot files in Drivers
Best answer by JimM
Hi Pegas,
I hope you don't mind, I split this topic off into its own thread since this is a separate issue.
The issue you're reporting was fixed in a recent build, but you are correct that these leftover files are not removed via a standard uninstallation. A removal tool would not remove them either. In fact, the whole point of having the files randomly named its to prevent such an automated removal script from being able to isolate and remove them.
These are renamed copies of WRKrn. The best way to deal with this would be to sort the contents of the folder by size. The ones that all share the same size as WRKrn are most likely copies of WRKrn. You still want to check. There is always the possibility of some other important file being the exact same size. Nothing is worse than wiping out some important files from the drivers directory that you still need. Your computer would not like that, and you might end up with a non-bootable situation. The best way to see what it is is to right-click the file and go to Properties. Take a look at "Digital Signatures," and you should see the file is from Webroot if it is in fact from Webroot. Make sure you don't delete WRKrn, but the duplicates are safe to delete.
If you're comfortable doing this yourself, that's ok. Alternatively, support can take care of this for you if you open a support ticket here.
Jim
Community Specialist
View originalI hope you don't mind, I split this topic off into its own thread since this is a separate issue.
The issue you're reporting was fixed in a recent build, but you are correct that these leftover files are not removed via a standard uninstallation. A removal tool would not remove them either. In fact, the whole point of having the files randomly named its to prevent such an automated removal script from being able to isolate and remove them.
These are renamed copies of WRKrn. The best way to deal with this would be to sort the contents of the folder by size. The ones that all share the same size as WRKrn are most likely copies of WRKrn. You still want to check. There is always the possibility of some other important file being the exact same size. Nothing is worse than wiping out some important files from the drivers directory that you still need. Your computer would not like that, and you might end up with a non-bootable situation. The best way to see what it is is to right-click the file and go to Properties. Take a look at "Digital Signatures," and you should see the file is from Webroot if it is in fact from Webroot. Make sure you don't delete WRKrn, but the duplicates are safe to delete.
If you're comfortable doing this yourself, that's ok. Alternatively, support can take care of this for you if you open a support ticket here.
Jim
Community Specialist
Hi Pegas,
I hope you don't mind, I split this topic off into its own thread since this is a separate issue.
The issue you're reporting was fixed in a recent build, but you are correct that these leftover files are not removed via a standard uninstallation. A removal tool would not remove them either. In fact, the whole point of having the files randomly named its to prevent such an automated removal script from being able to isolate and remove them.
These are renamed copies of WRKrn. The best way to deal with this would be to sort the contents of the folder by size. The ones that all share the same size as WRKrn are most likely copies of WRKrn. You still want to check. There is always the possibility of some other important file being the exact same size. Nothing is worse than wiping out some important files from the drivers directory that you still need. Your computer would not like that, and you might end up with a non-bootable situation. The best way to see what it is is to right-click the file and go to Properties. Take a look at "Digital Signatures," and you should see the file is from Webroot if it is in fact from Webroot. Make sure you don't delete WRKrn, but the duplicates are safe to delete.
If you're comfortable doing this yourself, that's ok. Alternatively, support can take care of this for you if you open a support ticket here.
Jim
Community Specialist
I hope you don't mind, I split this topic off into its own thread since this is a separate issue.
The issue you're reporting was fixed in a recent build, but you are correct that these leftover files are not removed via a standard uninstallation. A removal tool would not remove them either. In fact, the whole point of having the files randomly named its to prevent such an automated removal script from being able to isolate and remove them.
These are renamed copies of WRKrn. The best way to deal with this would be to sort the contents of the folder by size. The ones that all share the same size as WRKrn are most likely copies of WRKrn. You still want to check. There is always the possibility of some other important file being the exact same size. Nothing is worse than wiping out some important files from the drivers directory that you still need. Your computer would not like that, and you might end up with a non-bootable situation. The best way to see what it is is to right-click the file and go to Properties. Take a look at "Digital Signatures," and you should see the file is from Webroot if it is in fact from Webroot. Make sure you don't delete WRKrn, but the duplicates are safe to delete.
If you're comfortable doing this yourself, that's ok. Alternatively, support can take care of this for you if you open a support ticket here.
Jim
Community Specialist
Hi Jim!
Thx for explanation. I will remove them myself, no problem. To be 100% sure though, may I understand that I can delete all the leftover WSA files which are older than my actual build of WSA ( , i.e. in my case .165) and aren't named WRKrn?
pegas
Thx for explanation. I will remove them myself, no problem. To be 100% sure though, may I understand that I can delete all the leftover WSA files which are older than my actual build of WSA ( , i.e. in my case .165) and aren't named WRKrn?
pegas
From that folder, yes. If there are other files you're curious about that I'm not aware of, you'd need to point them out so I know what you're referencing. But yes, the ones we were discussing are safe to delete.
Done. Removed totally 134 files counting 13,6 MB. Just to be sure I will keep them in the recycle bin for a while ;)
Thanks & regards,
pegas
Thanks & regards,
pegas
+3Sorry to bring this up again, but it's been in the back of my mind for a while, and taking another look at this would like to ask if any feature could be implemented (e.g. into the Optimizer?) which would provide an auto-cleanup of these old renamed drivers?
I don't believe it's a solution to expect user to have the patience or expertise to locate and delete these manually...it's too tedious, and in reality they should not still be there, as they are serving no useful purpose (?)....Perhaps one for the Feature Request section?
I don't believe it's a solution to expect user to have the patience or expertise to locate and delete these manually...it's too tedious, and in reality they should not still be there, as they are serving no useful purpose (?)....Perhaps one for the Feature Request section?
Hi Dermot
Why don't you open a Feature Request and provide an expose of what you would like and where it might be put, etc?
Regards, Baldrick
Why don't you open a Feature Request and provide an expose of what you would like and where it might be put, etc?
Regards, Baldrick
? I will certainly Kudo it if you present it as a Feature Request. Given that we are also in the Beta, I have a feeling that we end up with more junk than the average user, but still it needs to be cleaned out for everyone. There is also an issue at the moment regarding language packs for the Password Manager that was discussed a few days ago.
+3Thank you ? and ? I've posted an effort here
I haven't gone into any great detail in the Feature Request, and any additional comments might help.
David, you might be right about many betas leaving more behind, and hadn't thought of that. Thanks :D
I haven't gone into any great detail in the Feature Request, and any additional comments might help.
David, you might be right about many betas leaving more behind, and hadn't thought of that. Thanks :D
LAready spotted & kudoed, mon ami. ;)
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
1 person likes this
+3Merci bien mon ami! 😃 Bon chance eh?
p.s. Don't ask for much more French....it isn't there! 😃
p.s. Don't ask for much more French....it isn't there! 😃
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.