Windows XP SP3, did the "big" update today, Thursday, 3/19/14...and found the same problem as Edwin Kuster posted about 3 days ago...complete slowdown in the PC. After working on the machine for about an hour, I did a system restore to yesterday, 3/18/14 and, guess what, the machine is running in its normal fashion.
Of course, one of the first things that happened after the sys restore was the notice from McAfee that "your PC is in danger". The question is, who is putting my XP machine in danger??
Even the most recent MSFT update was kind enough to update my machine without fouling it up though they will be ending all support next moth.
Now, should I even think about doing the update on my Win 7 machine, or is the new update going to foul that machine as well??
You know, I was going to keep my XP machine running with McAfee even after Windows support ended and be very judicious in my internet travels. Now, how can I have any confidence in this service? I thought once McAfee folded into the Intel family things would improve...well, I thought they would.
McAee customer for 20+ years on 4 different machines.
Your PC is in danger means McAfee needs to be updated and of course it will return you right back to where you started.
It's a known issue and it would be best if you opened a case with Technical Support, linked under Useful Links at the top of this page.
It's free by phone or online chat.
I wont lecture you on XP reaching end of life on 8 April. McAfee will continue supporting it until sometime next year when the current XP software version (SecurityCenter v12.8) expires. The only thing I will say, after 8 April security updates for XP cease, so any new vulnerability in the system that occurs after that date wont be patched so let the user beware!
Couple of things...
The XP machine is a machine w/Photoshop installed and I infrequently connect to the internet with it. Even so, I have kept my McA subscription active for any web work I have to do.
That said, my main machine is a Windows 7 laptop. Has there been any reports of this same issue when downloading and installing the "big" update from this week? I do manual updates on my W7 machine and I'm holding off until I know there's no issue with this week's update. i searched the forums and i don't see any W7 complaints about the newest update, but I haven't searched all of the forum. Do you have any insight about this issue on W7 machines? I'd appreciate any heads up here.
Not sure about ":the big update" as I haven't noticed one in recent weeks, but Windows 7 as long as it is totally up to date, including IE11 whether or not you use it, should be fine.
The same goes for XP, as long as it's totally up to date, includign IE8, then it should be OK, but if you are having issues contact Technical Support as I suggested previously.
It's possible, if you don't use a machine too often, that it would experience a bigger than normal update, because the software does get upgraded from time to time.
This issue does not seems to exist in Win 7 Machines. If you have an XP machine and you facing this issue try the below step and post back the outcome.
Uninstall McAfee from Control Panel. Run the McAfee Removal Tool from this link and restart the PC.
Login to McAfee's Online Account and Download the Installer of McAfee Product. During Initial stages of Install Select Custom Installation.
Uncheck Vulnerability Scanner and continue the Installation.
Post back if the System is Speed enough as before the Update..!
Thanks for the info on this issue not affecting Win 7 machines. That's what I was really looking for.
I spoke w/ McA tech help yesterday and the first guy said he had not heard of it. I then asked to speak w/ a supervisor and that gent had heard about it.
That said, the supervisor did say there wasn't an issue w/ the Win 7 machines. And that was the most important issue for me. I updated the Win 7 machine this a.m. without a problem.
Now, honestly, I have no interest in doing another uninstall, re-install for the XP machine. I just took it off line and I'll keep it as my Photoshop machine. But really, over my 20+ years and 4 machines, all with McA factory installed, the number of hassles, issues, concerns and aggravations with McA products is legend in my circle of friends.
The irony here is that with XP, MSFT is stopping support in April and yet, their last system update went smooth as silk. I figured if anything would screw up XP, it would be MSFT's last update. Not the case. Then McA, which is supposed to support XP through mid 2015, creates a different "issue". It wasn't that long ago we were dealing with the 100% svchost issue.
I was actually thinking about keeping McA's product on the XP machine after MSFT support ended and just being "smart" about what I did on the internet with that mchine. But after this, I don't know why I even considered it.
I've really had enough...I can promise you this...my next machine will not have McA on it; intel or no Intel.
Thanks again for your suggestion and Best Regards.
If you still have the slow pc on the XP machine- could you mind going to BIOS and disabling the Floppy drive and let us know if that helps?
If it does- i might need some help in gathering a few logs
OK this is what I found when My Daughter complained yesterday that XP started to suck very bad.
1. There is an issue with performance and floppy noise if you have a floppy installed. This is being looked at fix for the moment is disable teh floppy in device manager.
2. In her case she had installed the full version trial of malwarebytes it has a real time scanner that was clashing with the Mcafee scanner badly. Disabling either scanner allowed the PC to function. Do you have anather full version scanner installed is so only use the free version of Malwarebytes or other free scanners.
3. She also had indexing of c drive selected on boot so the mcshield scanner was working flat out till indexing complete this slowed the PC till the indexing was complete. I deselected indexing of you could index only my documents. This is in open explorer right click on c drive and properties and deselect indexing.
I wonder if those using XP and complaining about slowness have either of 2 or 3 issues above. I need to know so I can point Mcafee to it. My other XP box is stable and does not have 2 or 3 present.