Lawyers really this is a minor issue so minor my son in law went 2 mths having it before noticing it. He turned his monitor off as soon as he clicked shutdown so missed the 10 second message.
I have it 3 times in 54 shutdowns Ok some have it every boot those maybe the 1s mcafee can help by releasing the done fixes now.
Re refund usually only within 30 days of purchase is the rule but you can always try customer service. Contact via useful link tab above.
Is not only a shutsown problem. After update to ver 10.0 i have also svchost process than crash during normal operativity and cause error in win xp.
I have formatted my pc last sunday and installed a fresh copy of win xp. Everything is ok until i have installed Mcafee ver 10.
So the problem is not only on the shutdown. Is ridicolous not test before release a new version.
And more ridicolous if possible is not find a patch in over than 4 months
I just wanted to answer a couple of your questions for you.
The software was tested. Unplugging USB devices actually resolved this issue for some people, and I'll explain why. The issue is caused by this one service taking too long to close down as the computer shuts down. If this service was busy scanning a device, like a usb drive for example, or had hung scanning a drive, unplugging that device could cause the service to respond normally. This issue, in it's initial state, was thought to be a Microsoft issue because the Operating System (made by MS) was shutting down the service too quickly. Also, this issue didn't appear until after some MS patches went out. However, after getting samples from affected systems we found multiple causes for the issue.
We've rolled out fixes for this error, and many report no more problems, but new causes and newly affected users crop up again. We will continue to release updates and patches to address each cause we find, but it takes time to write the code for those fixes and to test them to make sure they fix the issue and cause no other issues.
Thanks Somer I forgot about the usb printer issue that was the first fix for this but been so long it slipped my mind.
BTW got no 4 popup out of 58 shutdowns yesterday on my test PC so still there.
Somer....Like DREWB, I (& no doubt many of us on this post) would appreciate details of the "fixes". We minions are in a position to "identify" if the "conditions" the "fixes" are addressing are present on our machines.. A little information could go a long way to reducing all the noise we are making. If you are introducing fixes, tell us what & when (version); we'll gladly give you feedback (positive or negative), but all this ad-hoc tweeking is "absurd". How is one to "know" when this software is truly functional (I know, I know, I understand the minor nature of this error message but, all these months of Developers "tweeking" this code makes me very nervous; USB connections? What else don't we know) I simply want to regain confidence in my Security Software & I'm not there yet. Any "concrete" information would be appreciated. Tx.
USB printers left on when one shuts down was the 1st cause of this issue. It was posted here but I forgot about it so chat's comment was partially correct not the blanket fix it comment just to try it.
I think the fixes are not added yet as they are chasing a 100% cure before release but we are trying to get what has been done released to at least fix some. There was a fix I mentioned way back in 10.5 that addressed the issue but it did not work widely.Message was edited by: Peacekeeper on 10/07/10 6:56:19 PM