Just as an FYI,. wanted to confirm that my experience appears to match your statement. I reported previously that I updated to the fix with SC 195 & FW 135 on 17/8 & was fine for "3 days" then error reoccurred on 20/8 at shutdown (had received "update" of Scan Engine & Site Advisor on that same date). Since then (17 days later & 34 shutdowns) , there has "not" been a repeat of the error; the only updates since that time have been on the DAT file. If this pattern is common for those of us who have experienced the error after the fix, I hope it is providing some insight for the techs. GB
I have been following this post since I received the 2010 update of McAfee Total Protection and I’m glad that McAfee have finally fixed the MvSvhost error, but for me (and judging by a lot of the comments across this site, for a lot of other customers) it’s too little too late.
I have been in contact with McAfee support to resolve some of the issues introduced by the update, and found the whole experience tiresome, invasive and with very little resolution to problems.
I take computer security and performance seriously; I recently ran some simple tests to see how McAfee impairs the performance of my machine, locked applications with false positives, and flooded virtual memory, it became apparent that absolutely no testing took place on XP for the 2010 update.
For this reason I have uninstalled Total Protection (Check the uninstall instructions), and installed Microsoft Security Essentials, (Check some of the independent reviews which compare all of the AV packages) and turned off my auto-renewal (You will need to email support to request this),
So goodbye McAfee, I now have my PC back running at top speed, applications not being locked, virtual memory ¼ the size, and a free AV application.
Thank you for the good years. Dom
Ok that is your right to do. Mcafee has taken a while with this but it was harder than expected as 1 fix caused other issues. It is fixed and should be working its way to users by now. Another fix the mcshield and mcagent issue fix is released to AU servers and I got this 1 today.
I reinstalled my XP test install and now firewall is showing 135.
Patch released to resolve the original mcsvchost issue.Message was edited by Somer Pyron to update status on the original issue. on 9/24/10 11:33:59 AM CDT
I appear to have found a fix for this issue on my Windows 7 X64 Ultimate install with the 2010 BT Netprotect verion of Mcafee Antivirus. I found a reference to a McAfee utility in the Knowledge base for an issue with PCPeople. I figured the issue must be caused by an install issue so I looked for a way to install the driver again. The solution was to run mfehidin.exe to install MFEHIDK.sys from the command line with the command "mfehidin.exe -i mfehidk.sys". mfehidin.exe resides in my c:\program files\common files\mcafee\vscore directory along with the MFEHIDK. inf, cat and sys files so you have to change directory on the command line to "cd c:\program files\common files\mcafee\vscore and then run the mfehidin.exe -i mfehidk.sys command. For other operating systems it may be in another place so you will have to search your McAfee program file directories to be sure. Then type "mfehidin.exe -i mfehidk.sys" (no quotes) into the command line and press enter. An alternative method that might work would be to right click on mfehidk.inf and select install from the popup window. This should install the driver again using the security catalog information contained in mfehidk.cat which is where I think McAfee got the install process wrong as it does not appear to register the security catalog details when installing the driver. After I did this I got a windows automatic certificate update for a Digicert SSL Certificate but I do not know if this was related. I have not got this error since doing this. Of course you mileage may vary! Good luck and let me know if it works for you. Daz.
That was an old old faq back in 2007 Where you having the mcsvhost memory error on shutdown If so it only happened on XP so if you were getting this on win 7 that is strange.
Will let Somer comment re that but why do you have to do this the fix was out 2 mths ago nearly. Can you post the security centre build and firewall build number as well as your affid.
BTW so BT supplies your mcafee wondering if your version was not updated.on 8/11/10 6:33:13 AM
After a couple of months of error free operating, on 7th November the McAfee program updated the Security Centre to Ver 10.5.216.
Three days later, ie 10th Nov I again got the dreaded Svchost.exe -application error - on Start Up!
Which appeared co-incident with log-in procedure.
Yesterday there was no error- I just hope this is not the start of another episode of the same problem.
Svhost or mcsvhost?????
I got that 1 time never again as did another in this thread after he manual;ly fixed the issue when we gave him the two files to replace. I hear that never happened again. Please keep us appraised...