What happens when you double click the tray icon (when it’s crossed out, of course)? Does a windows appear? And what happens when you click “Details…>>” in this window?
When i doubble click i see the normal on-access window but then whitout the pictures of the providers (this is in details mode). When i click start nothing happends.
Check the logs - start the avast! log viewer (accessible by right-clicking the avast tray icon) and see if there’s something suspicious - especially in the Error and Warning categories…
Hmm, this seems to be a tough problem. I’ll try to think off something… Maybe I’ll send you a debug version with extended logging features so that we can see why the providers are not being loaded… :-\
(first back up the original version, to be sure). The new version should work the same, except that it will create the file c:_aswServ.log on startup. I’d need you to send me the contents of this file (after starting the new version).
Hi i got an update from avast so i must restart my computer.
The next day on-access didn’t start up correct again
I had removed the log file because then i get a clean log but now when i restart there isn’t a log file.
I think that is because the update?
What can i do ???
Must i replace the ashserve again with the ashserve that you send?
Yeah, that’s quite likely, man, it’s got to be the VPS update. That is, the VPS update verified all avast files and found version mismatch in ashServ.exe (that’s because you replaced it with the “hand-crafted” version I sent you). So it replaced it with the “right” version.
Please replace it again - and you should be all set.
A new program update will be released early next week. This new version of ashServ.exe (that appearently works even on your machine) will be included in the update.
I replaced the file and then started ashserve ande on-access didn’t work correct.
Here is the text of the log:
aswServ 000353913 ms: Starting
aswServ 000353964 ms: In INIT XXX
aswServ 000355896 ms: AavmStart ERROR 80046302
aswServ 000355898 ms: AavmStart OK
aswServ 000355899 ms: Running def res task
aswServ 000356293 ms: Task started
aswServ 000356374 ms: Chest started
aswServ 000356376 ms: Scheduler started
aswServ 000356383 ms: WD started
aswServ 000356384 ms: Integrity thread started
aswServ 000356646 ms: Init complete
Maybe this is normal because i started ashserve by myself and not on startup.