hello i recently installed spysweeper as i had a keylogger installed on my pc. I managed to get rid of the keylogger then i deleted the spysweeper program and rebooted.
Now when i restarted my pc my avast will not start on acess protection it is saying its on but nothing is running. When i try to start avast it is saying error " the process cannot acess the file because the program cannot set property into main storage" i clicked on the read more about this error but it doesnt apply to my version of Avast which is 4.7 Home Version.
Spysweeper deleted the avast startup item.
Use the restore/recover or whatever it may be called to restore the deleted registry entry and update your definitions file for spysweeper. It reports incorrectly (false positive) the avast ashDisp.exe which is the icon you see on your system tray.
Other programs that can block are the startup monitors: PrevX, ProcessGuard, WinPatrol, TeaTimer, Ad-watch, etc.
Or you can check the option in the Appearance tab of settings of avast
the error susanM (and many others in other threads (cf. http://forum.avast.com/index.php?topic=21429.0) reports also showed up in my avast version 4.7.844 (Windows Me) in the following situation:
I had started the built-in update function of Copernic Desktop Search and was referred to MS Internet Explorer, which I did not want. So I interrupted the activity. I then got one or two dialog boxes which I answered with the objective of terminating the update process (I did not take notes of the text and look of the dialog boxes because I did not expect something exceptional to happen) and detected a few moments later the avast error in question when I started an on demand scan.
It seems that interrupted installation processes for large software systems could cause the avast error in question. I hope that the avast team will soon be able to present a solution to this problem. In my case it cannot be the Jet drivers (MDAC package) as was proposed to leomalav in the above thread because avast 4.6 and 4.7 have worked flawlessly so far on my system up to this interrupted software update.
Until there is a solution available could you provide an easy and practicable way to perform a memory scan? (In my case it does not start as it should after closing the error splash screen).
MDAC and Jet drivers aren’t due to problems anymore. Since version 4.7.807 a new data storage called SQLT is used by avast! Which version are you using?
Sure.
Run “C:\Program Files\Alwil Software\Avast4\ashQuick.exe” “*STRT-MEM-SHORT”
Which should be equivalent to the initial memory scan.
Do you mean version of MDAC or avast? (I mentioned already in my post above that I am using avast version 4.7.844)
As concerns ODBC / XML vs. SQLT my avast4.ini file contains the line:
Database=SQLT
This still works in two other, similar partitions of my computer whereas it has stopped working in the partition my post refers to (since the time I had interrupted the program update for Copernic Desktop Search.)
The intermediate solution for the memory test alone works. Thank you for this. But I still hope that you come up with a solution for the error described by the message “Program cannot set property into main storage”. The repair function in the Control Panel does not succeed to eliminate it.
On this version, ODBC / XML methods are not used anymore. So, MDAC is not a problem anymore as avast uses the SQLT storage method. That was what I meant.
About the other problem, well, ask to Alwil team as it is further my knowledge
