[2282] Daily HIPS alerts for aswHdsKe [Fixed]

[Asyn]

Hi, usually such alerts only happen when installing Avast.
With this version (2282) they pop up daily, out of the blue.
I've attached an example. There are 5-8 more, all related to aswHdsKe.

Cheers,
Asyn

[bob3160]

Easy fix is to remove Comodo. It's not an alert I've ever seen but I don't use Comodo.
Don't get me wrong, I don't know if this is or isn't a problem.

[RejZoR]

Also, I can see from the Comodo popup that you're using a very old version of their product. Interface they used which looked like this dates at least 3 years back if not more...

[Para-Noid]

The latest version is 10.0.0.6092

[Asyn]

1. Easy fix is to remove Comodo. It's not an alert I've ever seen but I don't use Comodo.
2. Don't get me wrong, I don't know if this is or isn't a problem.

1. Removing the tool (HIPS) that reports it, isn't a fix. (Not even a dirty one. )
2. As it's related to HNS, I could just remove this component, but I posted it as info for the devs. (Can't see any reason to rewrite the same registry values over and over again.)

[RejZoR]

How about using newer version of Comodo? It has the same functionality as old one, but is updated to behave properly for certain newer situations that didn't exist back then... I suggest you update your Comodo firewall to latest one...

[Asyn]

How about using newer version of Comodo? It has the same functionality as old one, but is updated to behave properly for certain newer situations that didn't exist back then... I suggest you update your Comodo firewall to latest one...

Hi, I have my reasons why I use this version on XP, but we're getting OT here.
Anyway, this is certainly not a problem with the Comodo-HIPS (D+).
I may add that it doesn't happen with the stable build (2280) of Avast.

[RejZoR]

Yes it is. HIPS that doesn't know what actions to ignore and what to warn about is a problem. And I'm not talking about ignoring actions as such, I'm talking about things that don't actually change, but since old HIPS doesn't understand that, it's alerting you about it every 5 seconds. Try latest Comodo FW and if it behaves the same, then there might be an issue. If there wont' be any issues, the reason was present in an outdated Comodo software.

[Asyn]

Yes it is. HIPS that doesn't know what actions to ignore and what to warn about is a problem. And I'm not talking about ignoring actions as such, I'm talking about things that don't actually change, but since old HIPS doesn't understand that, it's alerting you about it every 5 seconds. Try latest Comodo FW and if it behaves the same, then there might be an issue. If there wont' be any issues, the reason was present in an outdated Comodo software.

Thanks for your suggestion, but I know exactly how my HIPS works.
And yes, it's configured that way (ask about any change) on purpose. Cheers.

[SpeedyPC]

Also, I can see from the Comodo popup that you're using a very old version of their product. Interface they used which looked like this dates at least 3 years back if not more...

@Asyn your Comodo Firewall v3.14 is nearly 7 years old back in 2nd February 2010 and you really need an up to date firewall to be able to run on your XP platform, otherwise get windows 10 and used the latest security software available and it time for you to move on because Comodo Firewall v3.14 is long gone and buried.

[NON]

@Asyn

Does adding "Avast Software s.r.o." to "Trusted vendors" do something to your issue?
I also use CIS (mine is version 8 though) and my Defense+ does not say anything about aswHdsKe, I suppose this is because "Avast Software s.r.o." is present in "Trusted vendors".

I configure D+ as Safe-Mode so this might be a reason though. I suppose you use Paranoid-Mode?

[Para-Noid]

How about using newer version of Comodo? It has the same functionality as old one, but is updated to behave properly for certain newer situations that didn't exist back then... I suggest you update your Comodo firewall to latest one...

One reason is that the newer versions don't always work on an older machine.
I preferred CFW v5.2 but that version won't work on Win10.
Most of the newer versions of CFW take way too much space and are resource hogs.
I'm like Asyn, I don't see any reason to fix what isn't broken.

[Asyn]

Most of the newer versions of CFW take way too much space and are resource hogs.

Spot-on.

@NON: Thanks, but again, I know how to shut the alerts down. The question is, why the same registry values are getting rewritten daily.

[A. User]

It was very bad situation with the AVG beta along the newest Comodo 10 firewall. Adding AVG to trusted vendors list fixed it, but before that i got something like 20 HIPS alerts. I believe the issue was on Comodo's side because of missing AVG in their trusted vendors list. But they have Avast in the list though. I also recommend updating to the newest version of Comodo, but i don't know how it will behave in XP environment, so try updating to Windows 10 as soon as you are able to. 

[bob3160]

It was very bad situation with the AVG beta along the newest Comodo 10 firewall. Adding AVG to trusted vendors list fixed it, but before that i got something like 20 HIPS alerts. I believe the issue was on Comodo's side because of missing AVG in their trusted vendors list. But they have Avast in the list though. I also recommend updating to the newest version of Comodo, but i don't know how it will behave in XP environment, so try updating to Windows 10 as soon as you are able to. 

Once you get to Windows 10, use the firewall that's part of Windows and you will not have any problems.