cancel
Showing results for 
Search instead for 
Did you mean: 

Re: McScript_InUse.exe High CPU Performance

Update hogs CPU for 30 mins, 50-80% of which seems to be Backup of SCAN., NAMES. and CLEAN.DAT files.

I tried to gain some control by scheduling updates for 'When Idle for 60 minutes'...I can then launch a manual update when I can afford to lose use of the system for 30+ minutes.

But DESPITE setting updates for 'When Idle for 60 minutes',  VirusScan occasionally starts while I'm busy using the system - hardly Idle !

Why is update 'When Idle for 60 minutes' ignored? 

Can SCAN., NAMES. and CLEAN.DAT files be pruned to reduce backup+copy durations?

Please keep me posted.

I'm running VirusScan 7.1.0  scan engine 5.4.00 under Windows XP Home.

Thanks,

Richard

Reliable Contributor rmetzger
Reliable Contributor
Report Inappropriate Content
Message 22 of 29

Re: McScript_InUse.exe High CPU Performance

rstrange wrote:

Update hogs CPU for 30 mins, 50-80% of which seems to be Backup of SCAN., NAMES. and CLEAN.DAT files.

I tried to gain some control by scheduling updates for 'When Idle for 60 minutes'...I can then launch a manual update when I can afford to lose use of the system for 30+ minutes.

But DESPITE setting updates for 'When Idle for 60 minutes',  VirusScan occasionally starts while I'm busy using the system - hardly Idle !

Why is update 'When Idle for 60 minutes' ignored? 

Can SCAN., NAMES. and CLEAN.DAT files be pruned to reduce backup+copy durations?

Please keep me posted.

I'm running VirusScan 7.1.0  scan engine 5.4.00 under Windows XP Home.

Thanks,

Richard

Richard,

VSE v7.1.0 has not been in support for quite some time now. Just about anything said in these forums is not likely to help since many of the solutions require an upgrade to a new version. I was not even aware that the 5400 engine could even be applied to v7.1. Further, the rest of VirusScan Enterprise has been changed drastically to handle threats that v7.1 cannot possible deal with. As such you are not protected against todays emerging threats.

Please update your protection, as I suspect that the problems listed are not likely to still be problems in the newer versions. Use your grant code to download v8.7i with Patch 2 or at least v8.5i with Patch 8.

I hope this is helpful,

Ron Metzger

Message was edited by: rmetzger (grammar) on 12/9/09 1:17:49 PM GMT-05:00
Thanks,
Ron Metzger

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
sgrimmel
Level 11
Report Inappropriate Content
Message 23 of 29

Re: McScript_InUse.exe High CPU Performance

For downloading products, Service Packs, Patches, hotfixes or documentation:

Visit the http://www.mcafee.com. For instructions, see KnowledgeBase document KB54808.


For downloading Patches only:

Visit the https://mysupport.mcafee.com. For instructions, see KnowledgeBase document KB56057.

HTH

mBlaus
Level 7
Report Inappropriate Content
Message 24 of 29

Re: McScript_InUse.exe High CPU Performance

We have same problem with you. My computer is hung when updating process.

Reliable Contributor rmetzger
Reliable Contributor
Report Inappropriate Content
Message 25 of 29

Re: McScript_InUse.exe High CPU Performance

Based on your description, you may be experiencing 2 different   problems: 1) mcscript_inuse.exe CPU issue, 2) McShield CPU issues and   crash.

1)  Try: https://kc.mcafee.com/corporate/index?page=content&id=kb53690

Lowering the working thread priority helps relinquish CPU   cycles to other processes during updates.

2) Try: https://kc.mcafee.com/corporate/index?page=content&id=KB60651&pmv=print

By   turning off Scan Processes On Enable, you may help with the seemingly   random McShield CPU spikes. Based on McAfee statements, "This setting  is  intended for environments where security is more important than   performance." As long as you have installed Patch 1 (VSE v8.7i) or   later, this setting is suppose to be off by default, but may still be   On.

Here  is a .reg file documenting the possible changes:

REGEDIT4

;; Starting with VSE v8.5i, self-protection features are enabled.

;; By default, VSE blocks registry changes to itself.

;;

;; You will need to temporarily disable some of the McAfee

;; self-protection features.

;;

;; From the VirusScan Console

;;    Access Protection > Properties

;;        Uncheck 'Prevent McAfee services from being stopped'

;;        Common Standard Protection

;;            Uncheck (unBlock) 'Prevent modification of

;;                McAfee files and settings'

;;            Uncheck (unBlock) 'Prevent modification of

;;                McAfee Common Management Agent'

;;

;; Now try to import this registry file or make needed changes.

;;

;; Then re-enable the McAfee self-protection features.

;;

;; From the VirusScan Console

;;    Access Protection > Properties

;;        Check 'Prevent McAfee services from being stopped'

;;        Common Standard Protection

;;            Check (Block) 'Prevent modification of

;;                McAfee files and settings'

;;            Check (Block) 'Prevent modification of

;;                McAfee Common Management Agent'

;;

;; Now, restart the system.

;; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  - -

;; REGEDIT4

;;

;; LowerWorkingThreadPriority

;; SetProcessPriority

;; NoUpdaterUI

;;

;; see http://forums.mcafeehelp.com/showthread.php?t=221578

;;  'McScript.exe eating CPU cycles for several mins'

;;  1. Restart the system to activate.

;; Solution 1 - Create a registry key LowerWorkingThreadPriority as a

;; DWORD and set the value to 1.

;;  'CPU usage spikes during policy enforcement and a DAT update'

;; Solution:

;;   A noticeable performance improvement is found when using McAfee  Agent 4.0

;;   and ePolicy Orchestrator 4.0 server because ePO 4.0 compiles the  policy

;;   before sending it to the agent.

;;

;; Workaround:

;; Solution 1 - "LowerWorkingThreadPriority"

;; 1. Click Start, Run, type regedit, then click OK.

;; 2. Navigate to and select the following registry key:

;;    [HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared  Components\Framework]

;; 3. In the right-hand pane, right-click a blank space and select  New, DWORD

;;    Value.

;; 4. For the name, type LowerWorkingThreadPriority and press ENTER.

;; 5. Right-click LowerWorkingThreadPriority and and select Modify.

;; 6. In the Value data field type 1, then click OK.

;; 7. Click Registry, Exit.

;; 8. Restart the McAfee Framework Service.

;;

;;  Only implement Solution 2 if the previous solution is not  sufficient to

;;  reduce the CPU usage sufficiently during a policy enforcement and  update.

;;  Solution 2 - Disable the NoUpdateUI via the registry to reduce  the CPU

;;  usage:

;; 1. Click Start, Run, type regedit, then click OK.

;; 2. Navigate to the following registry location:

;;    [HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy  Orchestrator]

;; 3. Right-click on NoUpdaterUI and select Modify.

;; 4. In the Value Data field change the value to 1, then click OK.

;; 5. Click Registry, Exit.

;; 6. Restart your computer.

;;

;; see https://kc.mcafee.com/corporate/index?page=content&id=KB53690&pmv=print

;; Policy Enforcement Interferes with Real-Time Application

;;

;; Corporate KnowledgeBase ID:            KB66971

;; Published:            October 15, 2009

;;

;; Environment

;; Summary

;; CPU spikes that occur during a policy enforcement may interfere  with the

;; performance of real-time applications. When no other applications  are

;; being utilized on the client, McAfee Agent 4.5 utilizes the  available CPU

;; to complete its activity, in this case policy enforcement. This is  normal

;; and expected. If other applications are being utilized during the  policy

;; enforcment, or if they start during a policy enforcement, McAfee  Agent 4.5

;; will yield the CPU to the higher priority process. However, there  can be

;; momentary spikes in CPU during this time.

;;

;; Policy enforcement is a CPU intensive function, as is running most  real-

;; time applications. McAfee Agent 4.5 has improved performance  during

;; policy enforcement, and in many cases interference with other  applications

;; is not noticed at the end point. While performance has improved,  some

;; degradation may be noticed depending on the nature of the  application.

;; Because of this, voice degradation might be noticed when using  products

;; such as Voice over IP software. In situations where interference  does

;; occur, the default policy interval of five minutes might not be  ideal.

;;

;; Solution

;; McAfee is investigating this issue. As a temporary measure,  implement the

;; workaround shown below.

;;

;; Workaround

;; CAUTION: This article contains information about opening or  modifying the

;; registry.

;;

;;    * The following information is intended for System  Administrators.

;;      Registry modifications are irreversible and could cause  system failure

;;      if done incorrectly.

;;    * Before proceeding, McAfee strongly recommends backing up your  registry

;;      and understanding the restore process. For more information,

;;      see: http://support.microsoft.com/kb/256986

;;    * Do not run a .REG file that is not confirmed to be a genuine  registry

;;      import file.

;;

;;    1. Increase the length of the policy enforcement interval. The  default

;;       is five minutes. Increasing the length of time might make

;;       noticeable interference less frequent.

;;    2. Implement a lower thread and lower process priority for  McAfee Agent

;;       functions on clients:

;;       [HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared  Components\Framework]

;;    3. Under the Framework registry key, do the following:

;;           * Change the SetProcessPriority DWord value to 1.

;;             This lowers the process priority.

;;           * Change the LowerWorkingThreadPriority DWord value to  1.

;;             This lowers the worker thread priority to below  normal.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared  Components\Framework]

    "LowerWorkingThreadPriority"=dword:00000001

;;  "LowerWorkingThreadPriority"=-

    "SetProcessPriority"=dword:00000001

;;  "SetProcessPriority"=-

    [HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy  Orchestrator]

;;  "NoUpdaterUI"=dword:00000001

    "NoUpdaterUI"=-

;; - - - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - -
;;  ScanProcessesOnEnable

;;

;;  see https://kc.mcafee.com/corporate/index?page=content&id=kb60651

;;

;;  Should be Off under normal conditions. Having it on can cause

;;  additional stress to the system, causing McShield.exe to what

;;  appears to be random high use of the CPU. It should be On only  for

;;  PCs where Security is paramount and performance is not even

;;  considered.

;;

;;  See VSE8.7i Patch 1

;;  2. Issue: With the improved functionality of the on-access  scanner

;;     memory scan, lower and middle ranged systems may see a

;;     performance impact at startup and after a successful  AutoUpdate

;;     of the engine or DATs.

;;     Currently the Process on enable option is enabled by default  on

;;     the shipping version of VirusScan Enterprise 8.7i. McAfee

;;     recommends that in a managed environment, disable this option

;;     prior to deployment of the Patch, until the impact of memory

;;     scanning can be determined for your environment. It is not

;;     possible to maintain both the more comprehensive scanning that

;;     comes with Patch 1 and later, and the former level of  scanning.

;;     Therefore, only the more comprehensive scan is used.

;;     NOTE FOR CURRENT AND NEW USERS:

;;     -- The Patch installation does not modify current settings to

;;        disable the Process on enable option.

;;     -- The VirusScan 8.7i NAP and extension that are included with

;;        the Patch do change the McAfee Default policy, but do not

;;        modify the My Default policy, or any custom policy settings

;;        that were made prior to the checkin of the new  NAP/extension.

;;     -- The VirusScan Enterprise 8.7i Repost with Patch now  installs

;;        with the Process on enable option disabled, unless the

;;        Maximum Security option is selected during the  installation.

;;

    [HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\VSCore\On Access  Scanner\McShield\Configuration]

    "ScanProcessesOnEnable"=dword:00000000

;;  "ScanProcessesOnEnable"=-

Hopefully  this is helpful, and post back with any  questions.

Ron Metzger

Thanks,
Ron Metzger

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: McScript_InUse.exe High CPU Performance

Try Disabling Process Scanning by un-checking the option "Processes on Enable" under general settings of On-Access Scan properties.

Re: McScript_InUse.exe High CPU Performance

Highlighted
akill
Level 9
Report Inappropriate Content
Message 28 of 29

McScript_InUse.exe High CPU Performance

VSE 8.5 is a criminal of the resources try to upgrade to 8.7 Patch 5 at least!!  I hate 8.5

Re: McScript_InUse.exe High CPU Performance

Dont know if this is "scientific", but I have been having the mscript_inuse.exe performance problem and seem to have stumbled on to this observance:

1.  Problem only seems to occur if you do a start->shutdown->restart command from windows to boot the machine. 

2. My problem WENT AWAY  when I did a start->shutdown->shutdown and let the computer completely shutdown.  Then when I restarted windows from a complete shutdown the mcscript issue did not appear.

Hope this works for others.

Chris

More McAfee Tools to Help You
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • Visit: Business Service Portal
  • More: Search Knowledge Articles
  • ePolicy Orchestrator Support

    • Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center