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.
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,
Best answer by JimM
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.