No fix yet as I said Our T3 tech hasn't heard anything and he is talking to the bods fixing this weekly. Re compensation I assume it is too minor an issue to offer as it "usually" goes away in 10 secs and I have only seen it 3 in 40 boots/shutdowns so for some not common.
You can always try customer service.
Re desktop I will ask if it is in the July patch or 2011Message was edited by: Peacekeeper on 30/06/10 8:33:42 AM
Now that is strange an uninstall reinstall should give you the 10.5 etc.
Did you use the MCPR removal tool to uninstall? See useful links tab above for removal faq
For what its worth, the following is my version and build information for my McAfee Internet Security running on my windows xp computer.
Last update: 6/19/2010
Last update: 6/28/2010
I have not had the shutdown error message or other related problems since receiving update on 6/19/2010.
I am asking mcafee if throttling eased or when it will be. I only got 10.5 on my test PC early last week so possible they are still throttling but uninstall path should work. I have said this before when new version released it is put on new installs first usually in low sales volume countries as an another QA test. After a week they then release it for new installs to larger markets . Usually US is 1-2 weeks behind the 1st release date.
Update installs come around then but throttled as they do not want all servers being hit with updates at same time so this throttling lasts a month. I would have thought 10.5 throttling complete so I have asked for an update from Mcafee re this.
I went 12 days using Version 10.5 without seeing the error and last night at shut down the McSvHost.exe reappeared. It was reported by a McAfee tech that the issue has been fixed on some computers with the version 10.5 update. Not true, it has just slowed down and doesn't happen as often as it used to. Before the Version 10.5 update I used to see it almost every time I shut my computer down. I guess if I only see it every 12 days or so I can live with that for now but sure would like to see this issue get fixed. It has been around way to long and I am getting tired of hearing they are working on it and its on there top priority list.