One machine has only aswar0, the other has both.
XP SP3 on both.
Aswar1.dll doesn’t get a new timestamp at each boot as Aswar0.dll gets.
Aswar0.dll is newly signed, Aswar1.dll is signed a couple of weeks ago.
I know it’s used for Avast Antirootkit scanning.
Can I delete aswar1.dll?
HL
I would leave them where they are (not as if they are huge 220 and 185KB) since they are both .dll files unlike data/log files where you are unlikely to do any real harm. Why one doesn’t have aswar1.dll is beyond me as I have both and also using XP Pro SP3.
The date stamp on my aswar1.dll is 13/9/2008 so it hasn’t been modified (the date it was created) in a while. You could add the Date Accessed to the folders columns headings as that would give you a better idea of when it was last accessed/used rather than modified/created. Though this va;ue changes if you access the file in explorer.
XP Home SP3, forgot the home part.
Just doing some housekeeping with my systems, so I follow your suggestion.
None of my aswar logs show anything strange.
Both of my dll-files are 220 KB. MD5 is different.
Thanks.
aswar1.dll (or 2, 3…) might be created when the file is currently used, and a simultaneous VPS update brings a new one. I’d say it should be removed on the next reboot…
So to answer the question - if it has an older timestamp (and you’ve already rebooted), you can remove it (but you’ll have to disable the self-defence to do that). But as David said, it shouldn’t do any harm there.
Igor,
Thanks a lot. Useful info for me. 
HL