Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VShieldUpdate using all of my CPU power

I recently downloaded the mac antivirus, running on a macbookpro with osX 10.7.2, and now a process called VShieldUpdate is gobbling up about 100% of my processor power all of the time.... Any thoughts on why this is and how to get rid of it?

:1004281


This thread was automatically locked due to age.
  • VShieldUpdate is a component of VMWare Fusion, part of the VShield security solution.  If you search Google for vShieldUpdate, you'll discover that this isn't a Sophos issue, it's a VMWare/OS X issue.  Of course, since VShield is a security product, it is definitely possible that it isn't playing nicely with SAV.

    :1004287
  • i am having a similar problem too. Everytime i try to do a scan it will run for about 5 minutes, then crawl to a stand-still and use up approx 6.5GB or ram leaving my mac mini unuseable. Any help or advice is appreciated............Thanks

    :1004295

  • neildunne wrote:

    i am having a similar problem too. Everytime i try to do a scan it will run for about 5 minutes, then crawl to a stand-still and use up approx 6.5GB or ram leaving my mac mini unuseable. Any help or advice is appreciated............Thanks


    This is a completely different problem... turn off archive scanning and check the other threads on here for further solutions.

    :1004297
  • Andrew- thank you for your reply- and it would make sense except for the fact that I have never installed VMWare Fusion, and never seen it in my activity monitor until after installing SAV. Unless I've already got something nasty on my computer that is masquerading as VShieldUpdate... 


    Agile wrote:

    VShieldUpdate is a component of VMWare Fusion, part of the VShield security solution.  If you search Google for vShieldUpdate, you'll discover that this isn't a Sophos issue, it's a VMWare/OS X issue.  Of course, since VShield is a security product, it is definitely possible that it isn't playing nicely with SAV.


    :1004355
  • Try checking in /Library/LaunchAgents, /Library/LaunchDaemons, and the /Users/<user>/Library equivalents and see if you've got anything in there that shouldn't be there.

    Try going to the terminal and entering the following command:

    sudo grep VShieldUpdate -R /Library/LaunchAgents /Library/LaunchDaemons ~/Library/LaunchAgents

    If anything comes up, the plist file it lists is what you have to disable.

    :1004357