IIS / .NET problem

Hang in there, Mark is very knowledgeable, he will get this sorted for you.

Cheers

 

Just one, quick suggestion that might work: I had a similar issue when Windows was in the grave and revived it with a refresh install. After than IMON would collide with basically everything, long loads etc. The solution was to uninstall IPv6 protocol. If you have it on the system you could give it's uninstallation a try.

 

Here's an updated...I'm no longer having the lock-up issue after installing the 2.5 beta.

 

Thanks for the update PLeX™, it is appreciated.

Cheers

 

So finally anyone find out how to overcome this problem? Please let me know if someone did because as all of you I like Nod a lot and I don't want stop using it just because it has some incompatibilty with Visual Studio .Net.

 

Hi cipsys, welcome to Wilders.

Have you tried the new Beta?

Cheers

 

Yes, I've tried it today but the problem is still there. I've installed the new 2.5 version and after, the computer just stop responding when I was trying to access aspx pages. I've unloaded the IMON but still the same problem.
So after uninstalling it, everything came to work normally. I really want to keep this antivirus but I will keep it only if it will work along with Visual Studio.
That's why I'm searching for a solution to this problem. If anyone has it please make it public .
Thanks.

 

Hello cipsys,

Have you tried a clean installation of the beta version?

Bandicoot.
Eset.

 

Hi,

Yes I've reinstalled Windows a couple of days ago and this was the first antivirus I've installed on the PC. So I believe this makes of the installation a clean one, don't you agree?

 

Hmmmm..... yep, guess so. Have you tried completely disabling AMON just to see if the problem stops?

Bandicoot.

 

No. But even if it works this way it makes no sense in using Nod because the computer is not protected without amon (I mean my files aren't protected). I'd like to use Amon and Imon imperatively because it makes no sense using the antivirus without them.

 

Eset needs to narrow down the issue to the particular module. No one has asked you to leave AMON or IMON turned off forever.

 

Hi,

I can say that with IMON completely deactivated the problem was still there.

 

I was successful in using 2.12.3 by disabling IMON and rebooting, then disable AMON while using VisualStudio. After I was done coding, I'd turn AMON back on. I had to leave IMON always off because I had to reboot for it to allow IIS to work.

The new beta seems to work so far, although I have had a few lockups that were similar to but not exactly like before. I post more info when I figure it out.

 

Can anyone say if this issue has been resolved with the latest version of NOD32?

 

Hi,
Had the same problem but seems to work fine since I installed v2.5
Brian