Edit:
Original Post
Greetings. I have an issue that has been reported already, but largely disregarded as “user error”.
Basically, since upgrading to avast! v7, the program locked on to, and repeatedly, redundantly scanned a single file. This file, “RaUI.EXE”, gets scanned twice per second, pointlessly skyrocketing the “File System Shield” counter. The program itself is the Rosewill Wireless LAN Card user interface program and is perfectly safe. The program comes standard with a number of Rosewill wireless network cards and USB dongles and runs from startup to shutdown because it constantly monitors the networking hardware. (It’s actually an optional program when you get right down to brass tacks, but it has a lot of useful information about one’s wireless connection.)
The problem started in avast! v7 and was did not happen prior to this. avast! reports no problem with the file, as it shouldn’t, but keeps scanning it as if it’s opening and closing over and over again, which is isn’t. The only work-around for this problem is to track down the file and exclude its directory or the file itself (generally “C:\Program Files\Rosewill\Common*” or “C:\Program Files\Rosewill\Common\RaUI.exe” respectively) from the scan:
Temporary Workaround Instructions
[ol]- Open your avast! Antivirus user interface.
- Navigate to REAL-TIME SHIELDS → File System Shield
You should see “Last file scanned: C:\Program Files\Rosewill\Common\RaUI.exe” (or wherever the file was installed) at the bottom as well as a series of “scan spikes” in the SHIELD TRAFFIC area. - Click “Expert Settings” and navigate to “Exclusions”
- Either click the “Add” button, or click the blank spot under the last last exclusion (“allowance_response” for most users, I guess?)
- Either browse to where the file RaUI.exe is, or simply type in the full directory listed under “Last file scanned”, but with an asterisk at the end. (“C:\Program Files\Rosewill\Common*”, for example.)
Alternately, you can write the full path and filename (“C:\Program Files\Rosewill\Common\RaUI.exe”) if you simply want to exclude that one file. (avast! doesn’t seem to scan anything else in that directory either way.) - Finally, click “Ok”. avast! should no longer be scanning this file.[/ol]
It’s rather annoying that this issue popped up out of nowhere for no apparent reason and I personally would appreciate it if someone looked into the matter. As stated in the other topic, the issue persists even after a full uninstallation/reinstallation of avast! v7, so it’s not simple “user error”, here. avast! is just getting some sort of false positive it wasn’t before.
Thank you for your time.
Edit: Apparently, there’s quite a few programs out there that trigger this behavior, as documented in the posts following this one… “RaUI.exe” just happens to me the one I experienced this with.
