Endpoint Protection

 View Only
Expand all | Collapse all

High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

Mithun Sanghavi

Mithun SanghaviOct 12, 2009 09:14 AM

  • 1.  High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 07, 2009 02:53 PM
     Hi All,

    I just updated to MR5 and exported new single exe install packages I am still having this issue that was supposed to be fixed in MR4MP1.

    My Vista workstation is updated to MR5.  The SEPM Server where the packages is still on MR4 flat no MPs.

    High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package.
    Fix ID: 1470577
    Symptom: Explorer.exe has high CPU usage in Task Manager.
    Solution: Fixed in an update to the Auto-Protect component.

    Any Ideas?


  • 2.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 07, 2009 03:19 PM
     The issue is with the auto-protect of the client.So you need to upgrade the Client to MR4Mp1 or MR5 on the computer where you are seeing the CPU spike.So you need to upgrade the client on the server to MR5.


  • 3.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Trusted Advisor
    Posted Oct 07, 2009 03:25 PM
    The issue is resolved in MR5.

    The issue was with MR4MP1

    High Explorer.exe CPU usage when touching exported SEP client package

    This issue still occurs with an unmanaged SEP client. *Managed* clients don't
    seem to have a problem.

    I tested with XP Pro SP1 and an unmanaged SEP 11 MR4 MP1 client, updated with
    current definitions. I exported a client setup.exe from two other SEPMs (MR4 and
    MR4 MP1). In the XP client, right-clicking these packages and choosing
    properties results in a delayed response. Explorer.exe doesn't max out, but CPU
    usage stays around 30%.

    When I convert the XP client to managed (by SEPM MR4 MP1), the issue does not
    re-occur -- the properties dialog for both packages appears immediatly. The XP
    client didn't receive any updated content from the SEPM -- it already had latest
    updates, so I'm puzzled by the difference in behavior.




  • 4.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 08, 2009 11:41 AM
    My CPU spikes are on my Vista workstation thats running MP5 (managed).  The SEPM server where the packages are is running MP4 flat. So perhaps there is some issue there.

    Ah crap! the SEPM Server is running MR2 flat not MR4..... I will update the SEPM server to MR5 and retest.


  • 5.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 08, 2009 11:47 AM
     Yup...since its Client side issue to make sure all the clients are upgraded to MR5..so why even leave SEPM..


  • 6.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 09, 2009 01:32 PM
    Everything is upgraded now and its still doing it.  I tried moving the installing over to my file server from the SEPM machine and its still doing it.

    I've also tried touching the file from an XP Pro machine and the problem remains.

    Ideas?


  • 7.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 09, 2009 01:38 PM
    Just to make sure it is due to Auto-Protect.
    Disable File System AutoProtect on the SEP client then try to move the Package and check is it doing the same thing ?

    Can you delete that package and export a new one.


  • 8.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 09, 2009 03:17 PM

    Yeah well you can never really turn off sep.  Even if you right click the shield and "Disable it" go try the eicar test virus with SEP "disabled" and it will still catch it.
    Problem remains with SEP "disabled"

    However if you touch the file from a PC with no SEP it works just fine.  So it's defiantly an auto protect issue still.




  • 9.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 09, 2009 03:23 PM
     Have you tried exporting new packages..does it do the same thing..


  • 10.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 09, 2009 03:47 PM
    I can certainly try exporting new packages, however the packages I am having trouble with were freshly exported after I updated to MR5.  They are MR5 packages.


  • 11.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 09, 2009 05:58 PM
    Well I exported the MR5 package again, this time from my remote SEPM console on my Vista workstation and the problem is gone.

    Freaky.

    Thanks for your time Vikram and Mithun



  • 12.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Trusted Advisor
    Posted Oct 12, 2009 09:14 AM
    Hello,

    Thanks for updating Symantec EP to MR5.


  • 13.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 12, 2009 12:18 PM
    Hate to say it but the problem still remains.

    It was fixed for the first time I touched the file.  However it is happening again on both my XP and Vista workstations.


  • 14.  RE: High Explorer.exe CPU usage when touching exported Symantec Endpoint Protection client package. Fix ID: 1470577

    Posted Oct 16, 2009 01:39 PM
    Yes, the problem is still there.  I posted a message about the problem here not knowing it was something that was supposed to have been fixed. Happening on updated, and new installs of MR5:
    https://www-secure.symantec.com/connect/forums/explorer-locks-when-accessing-setupexe-install-packages-network-share#comment-3121781


    XP and 2003 machines it seems fixed, but if you are still running Vista, Server 2008 or Win 7 the problem  is still there.