Continuing ash Serve Shut Down error. Vlk please Help

Vlk,
Apparently the ashServ shutdown problem first experienced during the beta testing
is still with us.
I’m still getting them on a sporadic basis. Once every few days and for no apparent reason.
I’ve attached the latest unp file for your scrutiny.

One other annoying problem has to do with ashQuick and Zip files.
My default compression program is Power Archiver and when I download a zip file, the context
function always shows avast! as the first program in the list that pops up and selecting avast to do the scan,
does absolutely nothing.
I have to open the zip file which then brings up Power Archiver and select Scan.
At that point, the file is extracted into a temp folder and then scanned by avast!.
Please note that for any other file types, the context menu always shows avast!
in the 6th or 7th position of the context menu list.
For a downloaded zip file, it’s always in the first position.?

Thanks for your help.

Regarding the scanning of ZIP files - do you have any suspicious records in avast! log?

Hi igor
What do you mean by “suspicious”?
Nothinbg that I can see in either the files or the logs.

Well, I meant if avast! log viewer shows some errors maybe.
I suppose that if you run ashQuick on the downloaded .zip file manually (= from command-line), it works OK, right?

What do you have in the context menu for the .zip file?

I usually run it directly from inside PowerArchiver because I have
ashQuick setup as the default AV program.

So, where does the problem really appear? In Explorer context menu, or in PowerArchiver context menu (if it has any)?

The problem is in the context menu
ashQuick will not scan the zip file.
If however I open the file and then thru Powerarchiver select scan which invokes ashQuick,
it scans just fine.

Strange… could you post a screenshot of the Explorer context menu for a ZIP file, and for some other file (where scanning works OK)?

igor
I’ll take shots as soon as I have another situation where it comes up and will post it in here.

Maybe this will help.

http://img.photobucket.com/albums/v190/bob3160/Avast%20Forum/ContextScan.jpg

This is what happens when I do a right click on the zip file.
Please note that avast always appears as the 1st item in the context menu and when I select
avast!
nothing happens.

http://img.photobucket.com/albums/v190/bob3160/Avast%20Forum/ContextScan1.jpg

If I open the zip file in PowerArchiver and then select scan, the file is scanned by ashQuick.

The last sreen shot shows the normal position of ashQuick when a file is selected thru a right click.

http://img.photobucket.com/albums/v190/bob3160/Avast%20Forum/ContextScan2.jpg

Well, let’s forget (for a while) about the fact that it works in PowerArchiver - it is are not so important ;), and also about the fact that avast! is the first item in the menu.
(More interesting question would be: are the usual items moved down in the context menu, or are they simply missing?)

Does the problem affects .zip files only - or would it occur e.g. with some other archives (.rar, .cab, …) as well?

Check the default value of
HKEY_CLASSES_ROOT.zip
in your registry; it has some name (maybe CompressedFolder, maybe ZipFile, don’t know).
Now, navigate to the key called exactly the same under HKEY_CLASSES_ROOT
(e.g. HKEY_CLASSES_ROOT\CompressedFolder).
What’s the content of the “ShellEx” subkey (especially ContextMenuHandlers key)?

igor
Sorry for the delay. Things have been a little hectic in my house.
Hopefully the following jpg helps.

Well, I meant it a little different.
First, click on the .zip key and check the (Default) value in the right pane. It will probably say “CompressedFolder”.
So, navigate to
HKEY_CLASSES_ROOT\CompressedFolder\ShellEx\ContextMenuHandlers

Hope this helps
Zip default is PAZIP and that default is PowerArchiver.

Does it help if you (temporarily) change the default value from PAZIP to CompressedFolder ?

Will try it right now and let you know.

As you can see from the picture the only change is that ashQuick is now in the second position
but it still doesn’t work.
If it helps, ClamWin which I use as a back up context menue scan, is also effected and also
doesn’t work.

I would say that something (maybe PowerArchiver?) is somehow interferring with the context menu… but I really don’t know how to prove it (or fix it) :frowning:

igor
When and/or if you do, please let me know.
Till them i’ll just continue to scan the file from within the PowerArchiver program.
That works like a charm.