Problem with COMODO fw and starting ashMai Sv.exe

Avast Free Antivirus / Premium Security
1

Hi forum members,

When I started up my comp today, it greeted me with a pop-up that ashMai Sv.exe service could not be started, this could be because of firewall settings. I got an error 10049 message.
In the Avast console it said the service waited for a sub system.
I allowed ashMai Sv.exe now as a trusted application in Comodo FW.
What happened here, the second time around I did not get an error message and 5 of my 7 Avast services are operational.

polonus

2

Well have you updated avast, 4.7.1074 is now the latest ?
If so that may have been what kicked it off by comodo blocking ashMaiSv.exe.

Comodo can block any outbound connection whilst it is starting so it may also be what happened.

  • Comodo config options. Advanced Attack Detection and Prevention. - To get there, open program, click Security", “advanced attack detection and prevention”, and click “configure,” Block all outgoing connections while booting.

Also I have had this, where my firewall blocked an application that was permitted and is common in Zone Alarm. The firewall seems to get amnesia regarding permission settings even though it is permitted. The only thing that seemed to work was deletion of the entry in comodo and have it ask permission when you next check your email.

3

Hi DavidR,

I just restarted, might have done it myself (inactivity?). All 6 services are back up and running because I saw in my personal monitor program all the connections from 127.0.0.1 on port 12080 inbound and out (very reassuring sight). Says in the console all services fully operational. Just have to check the update service, maybe have to put that in the trusted applications. Weird firewall anamnesia. Maybe have to uninstall- reinstall firewall to hit its brains…
Well just had to restart the computer to install this latest, and the virus version 071028…
So everything OK…

polonus

4

Well firewall amnesia would seem strange but that is what it seems to be suffering, forgetting its permission settings, usually just deleting the entry is enough to effectively reset any ‘forgotten’ settings. I doubt you would need to go as far as a reinstall.

5

Hi DavidR,

While I had the right pop-ups from the firewall asking to allow, and the latest Avast program and AVS versions installed, I think everything is back to normal… Thanks again for you explaining,

polonus

6

Your welcome.

7

I don’t think so… I bet on the avast program update.

8

I think not, why no challenge, see quote below.
First there is an error message, but no challenge by comodo to a changed application.
Even with ashMaiSv.exe as a trusted application, it is still blocked and still no challenge if it were a changed application.

Now if a trusted application can’t connect, yet isn’t challenged as a changed application, tell me what ‘you’ think that is.

Now tell me that is normal for comodo and I will tell you it is flawed. After a program update when ashMaiSv.exe (or any changed avast element) is started or tries to connect it should be challenged by the firewall mine does (outpost pro).

When I started up my comp today, it greeted me with a pop-up that ashMai Sv.exe service could not be started, this could be because of firewall settings. I got an error 10049 message.

In the Avast console it said the service waited for a sub system.

I allowed ashMai Sv.exe now as a trusted application in Comodo FW.

What happened here, the second time around I did not get an error message and 5 of my 7 Avast services are operational.

Me I call it a firewall that has amnesia (permissions corruption/failure/memory loss/amnesia) blocking an application that has permission, e.g. it has screwed up its permissions. Amnesia is just a light hearted description of what is has happened.

9

Hi All

I got exactly the same problem after downloading a program update. Current version 4.7.1074 build Sep 2007

I use Win XP SP2, Comodo Firewall.

After reboot got the following error message

"Avast mail scanner warning

Avast will not be able to protect incoming mail (pop3 protocol)

Error 10049

Check if the mail scanner (ashmaisv.exe) is not blocked by your personal firewall"

In Comodo, ashmaisv.exe is allowed for both TCP/UDP in and TCP/UDP out

I get this error message every time I boot up

Is there a clear solution to this problem?

Thank you

Terry

10

Hi All

Tried blocking all outgoing connections at bootup. Did not work

Tried adding ashmaisv.exe as trusted then rebooted and up came an allow box to allow ashmaisv.exe. Clicked allow then rebooted. No problem.

Just to be sure change the settings back from trusted to allow tcp/udp in and tcp/udp out then rebooted. Everything appears to be ok.

So it it seems that Comodo needed to allow the ashmaisv.exe again

Thanks

Terry

11

Avast mail scanner warning

Avast will not be able to protect incoming mail (pop3 protocol)

Error 10049

I got the same warning … after a reboot it asked me to allow the Avast mail scanner, I did so and It worked. I still think this is a possible bug in the new version 1074 …

12

It has absolutely nothing to do with the latest update, a competent firewall that has outbound protection should notice the program changes (hardly surprising after a program update) and first it will block access. At the same time it should pop-up a dialogue window to challenge if it is valid, the user says Yes and that should be the end of the issue, exactly the experience you had.

The avast error is reporting that because something is blocking ashMaiSv.exe it can’t provide email protection until the problem is resolved.

What happened to you is what should happen challenge, acceptance, end of problem.

Some of the others in this topic aren’t getting the challenge and when they check ashMaiSv.exe has permission but can’t connect, this is what I mean by amnesia. Deletion of the entry forces comodo to ask (challenge) again and once accepted, the problem miraculously goes away.

13

It’s not a bug on avast.
This is a firewall issue like David said.