Wise decision. It should never have been included.
system
44
Thank you, Martin.
When and how can we remove aswRec.dll from our systems?
Can we just delete the DLL?
-Noel
igor0
45
The DLL itself doesn’t do anything, i.e. there’s no need to remove it (or care).
I don’t think you can remove it, the installer would probably put it back sooner or later.
system
46
Thank you, Igor.
But, with all due respect, how can you really know for sure? It’s a signed binary - that implies you didn’t build it from source and packaged the binary file just as given to you by OpenCandy. Therefore only they know what’s in there. Are you saying that no part of the existing installation of Avast calls into it any more?
I assume this DLL will be absent from the next update. Will the updater remove old DLLs such as this one that are no longer a part of the current package?
And by the way, it appears to be protected against direct deletion.
-Noel
Removal is easy enough and avast! seems to run just fine without it.
https://drive.google.com/file/d/0B-vSic0iJgyeRXd6WTdZZVlyV1k/edit?usp=sharing
I’ll see if it returns after a program update or a VPS update. 
system
48
Seems to me that disabling self defense would reduce security overall in other ways, but thanks.
-Noel
mchain
49
@ NoelC,
True.
Just re-tick the box for the self-defense option (re-enable it) when done with the operation. When self-defense is active is when you will get the access denied errors, otherwise you won’t when you disable it first, when one attempts to modify, move, or delete an avast! file.
The suggestion was never to disable self defense on a permanent basis. :o
As mentioned, if you need to make any changes to anything avast! related,
the self defense module will stop you and the cyber crook from doing so.
system
51
Did you miss the part where the Avast employee said the file would come back on its own?
And do we know the implications of their software trying to call a module that’s not there? We would hope the code is defensive and handles the error of a missing library okay, but we just don’t know. I’ll bet it wasn’t tested much that way.
Thanks, but I’ll just wait for it to be eliminated in due time.
-Noel
mchain
52
Maybe.
I’ve removed it and so far, it’s gone.
[EDIT:] There have been no errors or alerts or info boxes since this file was removed.
Hi,
the aswRec.dll will be fixed via micro-update during next week.
Thanks Martin,
Does that mean it will be removed ???
system
56
Sorry for replying on this old post but I wasn’t sure whether would be a good idea in duplicating topics.
Issue I have noticed today is that the file detection is triggered by Avast itself other than third party AV.
The detection is triggered while performing a Boot-time scan as per picture uploaded.
Is that normal? Anyone knows anything?
I have also another pc with avast and when I scan the file from within windows explorer with Avast or MalwareBytes there is no detection triggered.
Thanks
bob3160
57
It’s never a good idea to re-open an ancient thread. 
Many things change in this long a time frame.
Remember that there are different settings and parameters for different types of scans. Something “detected” by one need not be detected by a different type of scan.
Also note that a PUP is a possible unwanted program that’s different than an infection.
system
58
I kind of agree with that although as a forum admin perhaps the topic should be just locked out after a certain amount of inactivity.
I understand this is a PUP detection but do you know more on why this is triggered anyway as it sounds a bit strange that an AV product detects a DLL of their own?
bob3160
59
Deciding if a pup is dangerous or unwanted is a decision made by the user and depends on where it’s found.
The scan simply informs you of what it’s found. It’s up to the user or, the person instructing you to run this scan, to make the decision. It’s also one of the reasons why in most instances,
a boot scan is only run when asked and usually any changes made from detections are supervised.
A boot time scan isn’t meant to be run by a novice. 
The cause of the anomaly between the Boot Time AVAST scan report and an ordinary AVAST scan is probably simply because, by default, all AVAST’s AV scan setting options have PUP detection turned off. Unless you enable it AVAST doesn’t scan for PUPs.
However the Boot Time option scans for everything and by default PUP detection is turned on. It can be turned off in the Boot Time scan Settings.
To get rid of Open Candy I’d do a manual scan with free Malwarebytes or Spybot. When I last had Open Candy sneak onto my computer both picked it up during my regular weekly scans.
How it got on to my system when I have AVAST set to include PUPs and everything I download manually is scanned with Malwarebytes as well suggests it was integrated into some otherwise trustworthy installer or update software.