Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: dja2k on February 21, 2005, 02:00:39 AM
-
When I start certain programs, there is an entry point not found error and reads
" The procedure entry point dep_fssetfileattributes could not be located in the dynamic link library ASWCMNOS.DLL" which I think is a file from AVAST Antivirus. Why is it giving me those errors and can I fix it or not?
dja2k
-
What exact version of Avast do you have?
Have you already tried a repair?
-
I have version 4.6 and it only does it in msn messenger and yahoo for now, haven't found any other. It gives the error, you press okay , then the program works.
dja2k
-
Any error in Avast's log file?
What about the repair? Did you tried it?
What OS?
The version of Avast is in the form of 4.6.xxx
What do the xxx say?
(right click the blue ball and choose about)
-
Did try the repair but nothing, same thing when I reinstall. It is version 4.6.603. I have windows xp sp2.
dja2k
-
hmmm, let's wait and see what the people from Alwil have to say about this.
-
Okay after the third time of trying to uninstall and then install again, it seems the problem is gone for now. Thanks for the help and if the problem comes back, I will post again.
dja2k
-
I have the same program in yahoo with that The procedure entry point dep_fsSetFileAttributes could not be located in the dynamic link library aswCmnOS.dll but its in yahoo.
Does anyone know how to fix this cause i noticed the .dll file is my avast folder and in my systems 32 folder.
So if anyone knows how to fix it let me know cause ive done a yahoo unistall and reinstall and it didnt work.
-
Haha freestylegreek, ever been running an avast Professional Edition keygen? Beucase these are known to hose up avast installations in this way. ;)
The solution is to delete the aswCmn*.dll files from the system32 folder. There should be only 1 copy of those, in the avast folder.
Thanks
Vlk
-
So delete that in the systems 32 folder and one in the avast folder?
Are you talking about deleting the aswCmnOS.dll file in the system 32 folder and in the avast folder? Will deleting this damage my pc and avast? If this is the .dll file you mean will the avast still be able to run and detect virus's?
-
Delete the file in \Windows\system32 folder and leave avast folder alone, reboot afterwards.
Perhaps it's time to choose some better warez tool ::)
-
If you are so sure that the user is using a cracked version of avast (Vlk and Lukas), why should we continue helping him/her? ::) ???
-
If you are so sure that the user is using a cracked version of avast (Vlk and Lukas), why should we continue helping him/her? ::) ???
;) Well starting the keygen program does not actually mean someone is trying to use unathorized licence key .... I have already run that program too ... ;D
BTW: Is it still you, Technical? You seem to be rather shortened.
-
;) Well starting the keygen program does not actually mean someone is trying to use unathorized licence key .... I have already run that program too ... ;D
You're right... I've run it too ;D
BTW: Is it still you, Technical? You seem to be rather shortened.
I'll come back to the long Technical :-[
I thought the users would like the shorter but, as I can see by your words and others, I can't change my name that easily... it seems to be written in the deep soul of the forum :-\ :-[
-
Tech(nical) is having troubles with his weight ;D ;D ;D
He loose some than he gain some ;D ;D ;D
-
Haha freestylegreek, ever been running an avast Professional Edition keygen? Beucase these are known to hose up avast installations in this way. ;)
The solution is to delete the aswCmn*.dll files from the system32 folder. There should be only 1 copy of those, in the avast folder.
Thanks
Vlk
Hihihi... this is unbelievable how easy is to track some things... and best of all, people from Alwil are still helping... even if it comes to cracked (or better say "keygen-ed") version of avast! Pro... ;D
Cheers !
-
Haha freestylegreek, ever been running an avast Professional Edition keygen? Beucase these are known to hose up avast installations in this way. ;)
The solution is to delete the aswCmn*.dll files from the system32 folder. There should be only 1 copy of those, in the avast folder.
Hey Vlk, wow you guys even help people using illegal versions...
But what I wanted to ask, I'm interessted how come the keygen causes such problem, I thought they just make a key and you enter that?
anyway, just interest, I'm the happy owner of a 3 year license :D :D :D
-
But what I wanted to ask, I'm interessted how come the keygen causes such problem, I thought they just make a key and you enter that?
Let's just say that the keygen authors are rather "lame" (to use the field terminology ;D) - and also use tools that are (suprisingly) bad.
-
But what I wanted to ask, I'm interessted how come the keygen causes such problem, I thought they just make a key and you enter that?
Let's just say that the keygen authors are rather "lame" (to use the field terminology ;D) - and also use tools that are (suprisingly) bad.
aha we talk about ACME then? :P
I'm interested, gonna try to unpack that thing to look what it does...