VirusScan is always on , but I am running a manual scan now. Since the .net
problem affects every PC on this site, I suspect that there is something in
the image (like VOIP) causing the problem.
> VirusScan is always on , but I am running a manual scan now. Since the
> .net
> problem affects every PC on this site, I suspect that there is something
> in
> the image (like VOIP) causing the problem.
Is IEExec.exe the name of your application? I've never heard of "Microsoft
IE Execute shell" nor "IEExec.exe" before, and the naming sounds very
suspicious.
>> >I recently had .net version 2 installed to support a product that
>> >requires
[quoted text clipped - 13 lines]
>>
>> Run a virus scan?
Laura T. - 18 Apr 2007 09:27 GMT
IEExec.exe is standard IE helper app for zero deployment.
http://support.microsoft.com/kb/822485
Dean, could this apply?
http://blogs.msdn.com/robgruen/archive/2004/09/28/235074.aspx
>> VirusScan is always on , but I am running a manual scan now. Since the
>> .net
[quoted text clipped - 23 lines]
>>>
>>> Run a virus scan?
Dean C - 18 Apr 2007 18:36 GMT
Thanks for trying. My Tech support solved the problem. We needed to download
the SDK and run the security configuration file (mscorcfg.msc). Security
configuration was previously included with the .net Framework files and the
configuration set up using v 1.1 is not carried over to the 2.0 installation.
I hope this helps anyone else.
> IEExec.exe is standard IE helper app for zero deployment.
>
[quoted text clipped - 31 lines]
> >>>
> >>> Run a virus scan?