Having the same kind of WFP problems (see my previous posts) I am a "regular" visitor of this thread.
So I know.
A family friend -a lady "over retirement age" -has a Dell desktop running XP which she uses for emails, internet and so on. She is now plagued with this issue and asking me what to do! It is very problematic to resolve at a distance and because I don't have my "hands on" the pc and despite all your technical discussions it isn't clear whether just removing Mcafee resolves the issue or whether there are really file issues to resolve. What is slightly worrying is that the message is telling her to "insert XP Professional Disk 2" when her system in on XP, not Pro!
This is a real mess, particularly as M is not rushing to sort the problem. I have faced not disimilar issues over M recently not scanning avi files without falling over big time. This has been around since June and doesn't seem to be a priority either. I have had to move one pc onto Kaspersky just so I can scan my avi files. The other two may well follow!
So assuming Mcafee don't resolve this any time soon, if "we" remove the program does the WFP protocol sort the file issues from the cache without further intervention or do we need to play around with an OS disk (and which I suspect it may reject as being "the wrong disk"). Not even sure, because it's a Dell, she has an OS disk.
I dont think there are (yet) any graphics issues. She does, because of poor eyesight, run at fairly low res, so it might not be apparent.
Yep was lazy so went though and grabbed all posts here that mentioned anything tried and sent them to the tech. Siem Pm;d you my email.
Because I'm that kind of person who first must have his computer in a "working" state before doing anything (i.e. answer questions) and above that I'm that kind of person that refuses to give up on nasty driver / OS / Virus Scanner issue's I sorted it out.
Not only to be temporarely up again but (okay, did not had a new McAfee update yet) for me it works. I am up and running on WinXP SP3++(*1), McAfee Antivirus+ runs on the latest version with on access scan enabled, my ATI HD4600 AGP 1 GB works fine (however I'm not a gamer so did not check these borders).
(*1: The first + is for all the applied hotfixes/kb's etc after SP3, the 2nd + is for my way to trick WFP on the ATI driver issue).
For now I'm taking a nap and come back to you folks tomorrow. If by any means a roadkill would be my destination before I can answer you....... For the techies on WinXp, AMD Catalyst/ATI drivers and McAfee:
To the McAfee Techies: I do not know why the update of McAfee kicks in WFP but it does. To solve the problem the on-access scanner MUST be disabled.
To the Microsoft techies: In depth knowledge of your beautifull WFP proces shared with us during these months would have been a big advantage.
To the AMD/ATI driver developers: You make beautifull products but integration into an MS WinXP (do not know about the other OS's) OS is crap.
If all the three companies above get their heads together it can be solved in a right (dumb mode on) fool prove (dumb mode off) way.
P.S. What's it worth to you guys (Microsoft/AMD-ATI/McAfee) to get you on track on this ........
Okay, promised you my solution. It's not for the faint hearted but I think for the people who are trusting themselves in what they do and are experienced in technical (Windows) computer stuff it can be done. My solution is written for the ATI HD4600 AGPadapter. I will provide detailedsteps with notes and comments following these.
First of all: After solving the problem yesterday I was confident enough to switch it off, it still works.
Warning!: I do not take any responsibility of the instructions written in this document. You should back-up your computer before applying the instructions and know how to restore this if all goes wrong. Please read and understand the instructions, do not blindly follow them.
I’m an experienced computer technician and I assume that people taking these steps know how to operate a computer and may call themselves experienced on the Windows Xp OS.
Computer: MSI NeoV2mainboard (Headstart), Pentium4 3,2GHZ, 2GB RAM, 180GB HDU, ATI HD4600 AGP 1GBdisplay adapter, Hauppage WINTV 150PVR adapter, DVD rewriter, DVD-Reader, WinXPMedia Center Edition 2005 SP3 all hotfixes and KB's applied so up to date.McAfee Anitvirus+ Security center version 11.0.578 (27-08-2011),McAfeeVirusScan version 15.0.291 (31-08-2011), DAT version 6454 (30-8-2011),Startup DAT version 6446.0000 (22-08-2011), Egine version 5400.1158, McAfeePersonal Firewall version 12.0.338 (27-08-2011), McAfee Quickclean and shredderversion 11.0.393 (27-08-2011).
Problem: After restarting computer because McAfee update on 26th of August asked for it, the computer came back in a640x480 4 bits color resolution.
Cause: McAfee update touches system files so Windows File Protection kicks in and reverts drivers (which are good) to the latest version it knows about (in my case those from SP3), are older and do notwork.
Note: Because I’m Dutch I have a Dutch XP installation. I’m not sure if all my translations on buttons, menu’s etc are correct.
Because a resolution of640x480 4 bits is really not workable (windows and window buttons falling ofthe screen without possibility to reach them) first step is to revert the faulty driver to the standard Microsoft SVGA driver. This can be done by uninstalling the driver through display properties.
At this stage and after reboot the system will come up with the standard Microsoft display driver which is SVGA 800x600 256colors. It’s not the best but at least you can work on your computer.
Please Note!: After restarting probably your computer comes up with the wizard “New Hardware”. Do not touch this wizard, leave it as it is unless you do not rely yourself on the next steps to be taken to have a complete working ATI driver installation again.
If you do not trust yourself in taking the next steps but do not want 640x480 4-bits yust exit the wizard.Your system will be running fine on a resolution of 800x600 256colors with a working Virus scanner.
In this stage you will reinstall the ATI drivers and after doing that make a backup of all the necessaryfiles in case you have to reapply because you forgot something and WFP kicks inreverting some or all of your work. RememberOn-Access scan should stay turned-of 4ever unless you like repeating yourselfthese steps.
At this stage we want to make sure the drivers just installed are kept at the backup location, you will need them later.
Windows File Protection keeps track of changed files through comparing the versions in the DllCache and after that ServicePackFiles folder to the System32 folder and the System32\Drivers folder. If in the last 2 folders mentioned different versions are detected they will be overwritten if WFP is triggered. In the next step I will give instructions on copying the back-up files from step 4 to the right locations. I did this when my computer was running in “normal” windows mode. In “normal” windows mode WFP is guarding System32 & System32\Drivers folder. I took the risk to copy the files in “normal” operating mode and was to quick for WFP. If you do not trust yourself (please observe the system event log during the process) you can start your computer in “safe mode” and do the copy without the danger of WFP reverting your work.
Please obey the order of copying (1st DllCache, 2nd the other location)
Observe the corresponding back-up new location files with the System32 &System32\Drivers folder during half an hour together with the system event log. If they differ WFP kicked in; Advice: (see above) “Safe Mode”.
The first 2 steps from Finally. were merely for me to check if everything staid as it should be. For me it was reassuring that it did.
The above instructions can give you your normal computer operation back. However: Tricking the system this way is defeating WFP which, under normal circumstances, is not necessary.
On the ATI driver install the following can be said: Because the ATI driver install can only be done by it’s own installation program (as far as I know) there must be something lacking in this program that does not create the right files (or pointers to these files) to the right locations so WFP cannot find the right versions when triggered. The ATI drivers cannot be found online by the new hardware wizard (or not the right versions) thus leaving you with this procedure. The same problem with a Nvidia adapter was solved by de-install of the driver as written above and let Windows Hardware Wizard detect the driver on-line.
I do not know in what way the McAfee update has touched the files for WPF to kick in but it did. Even with a future update from McAfee which triggers WFP you should be safe.
Message was edited by: siem on 9/1/11 5:43:36 PM CDT
Passed onto the high level techs thanks for the time you took.
This issue is 3 months old today.
As a rough guess - how much longer until it is resolved?
Or, how much longer to wait until a tech from McAfee posts something here?
And who was on the grassy knoll that day?Message was edited by: blarty-fargo on 04/09/11 11:16:11 IST
We probably have a bettor chance of solving the grassy knoll Question
... and how many have given up waiting and found other AV solutions?
Me mate - I gave up after a week.
But I lurk here as, technically, I am still another big M customer.
Pity I can't get a refund for the unused (wasted) part of my subscription.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: