I learned a couple of things from 3 attempts at upgrading McAfee, including the "in-place" upgrade that precipitated the problem, the "clean" uninstall/cleanup/reinstall that reproduced the problem, and the final uninstall/cleanup from my factory image before installing my new, non-McAfee security suite.
1) Despite getting "cleanup successful" messages from the MCPR tool, it does NOT always cleanup all traces of McAfee (esp from the registry; forget about files/folders under Program Files, AppData, etc!). I was careful to run it TWICE, rebooting each time, when I made my final McAfee uninstall prior to installing my new security suite.
2) Although it varies from security suite to security suite, it is generally both preferable and recommended to fully disable both Windows Firewall and Windows Defender prior to installing a new suite. This is a 2-step process, involving both: 1) turning both applications off from the control panel > programs, AND 2) making sure they are both fully disabled from START > services.msc. Even when they are turned off from the control panel, they are highly integrated into the Windows OS, can be "running" in the background, and can cause conflicts. (Moreover, neither program is needed if you have other suitable FW and AV protection.)
That said, I also learned -- the hard way, thanks McAfee -- that multiple attempted uninstalls/reinstalls of the 2010 McAfee software corrupted files in the OS.
So, even when McAfee was fully uninstalled and the system appeared otherwise "stable", it was unable to properly boot into Windows.
This caused a totally BLACK screen when booting normally, a BSOD with stop-code when booting into safe mode with networking, and (thankfully) the ability to boot ONLY into basic safe mode,
Since extensive hardware testing showed that to be OK, it became necessary to restore the computer to the factory image on what had been an otherwise rock-stable, 6-month-old, high-end system.
Having done that > 1 month ago, removing McAfee once and for all, and installing another product permanently, everything is now fine.
So, you might want to be sure to REALLY clean McAfee off your system, and to be sure you have both Windows Defender and Windows Firewall completely disabled.
If you continue to get BSOD, especially with booting, and your hardware and chkdisk are OK, then you may well end up having to restore your OS to the factory image (or worse), in order to alleviate any OS corruption.
I've got a Dell Inspiron 546 MT with Windows 7. Last week's McAfee update resulted in the same blue screen crash after next re-boot, accompanied by hair-raising sound effects. After trying Virtual Technician, and then 'Restore' (which worked until another update), I contacted Chat. First experience: after waiting about 15 minutes I was told 'session expired'. Tried again next day: after 18 minute wait was connected with Basil, who must have been working with a number of customers as there were long (i.e., 3-5 minute) pauses between his questions. The good news: about 40 minutes later, after Basil remoted my machine and downloaded some software, I was back in business. So apparently McAfee have discovered the problem and are now equipped to repair it. Moral: stay patient!
"...accompanied by hair-raising sound effects."
Did you get that horrible grinding noise from the HDD, too?
When this happened both times for me (after the "in-place" upgrade and even after the clean install), I was forced into lengthy hardware diagnostics. (Fortunately, I have a paid contract for premium, N-Am-based tech support with Dell.)
Fortunately as well, everything checked out OK, hardware-wise.
But TMAVLSS, I ended up needing to restore the OS b/c of the damage...
I would have been "happy" for a bootable computer with non-functioning McAfee, or even a BSOD.
But I got a system that wouldn't even BOOT, except into basic safe mode.
(Normal boot --> black screen, no boot, no BSOD; safe mode with networking --> BSOD, no boot.)
CPU, GPU, PSU, OS, BIOS, DRIVERS.... I don't know what the root cause was. No one from McAfee cared enough to find out in an expert or timely manner.
All I know is that the "2009" McAfee that came bundled on the system in Feb 2010 worked fine.
The 2010 upgrade was an unmitigated catastrophe from Day 1.
That was more than a month ago -- if the svchost.exe thing for XP is any indication, it will be many months before a "solution" is devised.
I, for one, could not wait that long, since I depend on my computer for work.
Pondviewer - I am happy to hear your problem has been resolved by McAfee technical support.
I guess I have a different moral interpretation from the story - simply put, don't use McAfee products anymore.
My expectation of what McAfee should have done is to:
1. Prominantly post the problem on their website so that customers would not have to have the same experience waiting for technical support that you had.
2. Post a link to any/all patches for the problem - with instructions.
3. Post a link on forums like this one acknowledging the problem and directing customers to the appropriate site for a remedy
Given the competitiveness of the market for home computer protection it's hard for me to see why I (or anyone else) would continue to purchase McAfee products.
I think the combination of continued technical issues, e.g., updates that disable computers, combined with the poor follow-up to customers advesely affected is completely unacceptable.
The 'hair-raising' noise I reported was purely electronic, and did not involve the HDD; sounds like I was 'lucky'(?) My machines have always had Norton; this Dell (purchased Feb. 2010) came pre-loaded with McAfee. Since I never had anything like this with Norton, and had my McAfee 'experience' 6 months into its use history, I can understand the comments about a poor history of performance and service. I agree with hannenberg that the quality of my service experience should have been many levels higher than it was.
Ok some info I never knew before.
The beta version I run has a patch for BDODs in win 7 64 bit. It I thought was for Toshiba PCs with amd processors and a certain bios manufacturer. It appears it is not limited to Toshiba but other manufactures and CPUs where Mcafee asks the bioses how many cores in CPU and it misinterprets the answer thus a BSOD.
With the spate of Dell bsods would any1 be interested in uninstalling and trying the beta version. This needed to confirm/deny the fix works on other PCs. Of course you can uninstall the beta when the patch is released in 2 weeks ( anytime after 15th September but more likely end September and it will be throttled so it will come slow).
Any takers? The beta is stable I have been using it on my main PC for 12mths without issue. If interested PM me and I will pass on the info re the beta site.
Removed your duplicate post. Re how to know 2 ways
1 I or some mcafee person such as Somer will post here.
2 As you cannot run the program without bsods it I assume will not update itself so once told you can uninstall and reinstall from maybe the aussie server as it will get it at least a week earlier than the US/UK server.
I know the date but am not allowed to release it. last time I did they delayed it and that caused some angst. It is soonish.
I cannot confirm the fix is what you want that was why I asked for someone to try the beta version as it has the fix.Message was edited by: Peacekeeper on 15/09/10 4:39:02 PM