McAfee problem works in safe mode with networking

Hello, I am just wondering, isn't this a known issue, there is a folder in c:\windows\system32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} that has to have so many files in it. Any .tmp folder, in catroot, you have to copy to {F750E6C3-38EE-11D1-85E5-00C04FC295EE}. Rename bootcat.cache to bootcat.bck in c:\windows\system32\CodeIntegrity. I did all that. Also turn off Driver Enforcement in the F8 menu. I can get into safe mode with networking, and I can save to / copy from a remote share, any file, and I can ftp. This was a McAfee problem. I thought they fixed it? Still get a blue screen no matter what.

could you explain ??

sure - sorry. We began getting blue screens. Windows would attempt Startup Repair. We were told it was this issue:
https://kc.mcafee.com/corporate/inde...ent&id=KB75956 .

There was a fix involving copying a tmp folder to
c:\windows\system32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
In most cases, this worked. However, on one machine, it does not work. I can get into safe mode, with networking. I was hoping Mcafee, or Microsoft, would have had a patch by now. We were told they would. At the bottom of this post is what the McAfee website says. I am just surprised that Microsoft would give an outside vendor access to protected kernel or dll memory. Microsoft is clearly happy to step away from it and let McAfee sink or swim, if you will, is my perception. One set of instructions says, "Run this .msi file" but this is impossible in safe mode. If this explanation is unclear, then I apologize. I can almost certainly just re-image this machine. I was hoping not to. I thought people would know what I am talking about. I guess probably not. I guess will just give up and re-image.

Cause

McAfee is currently working with Microsoft to post a root cause analysis.



Solution

This issue is resolved in the McAfee Agent 4.6.0 Patch 2 Windows Repost (build 4.6.0.2935). This was made available for download on August 22, 2012 from the McAfee Download site, Service Portal, and Software Manager.

IMPORTANT:

• Customers using the original build of 4.6.0 Patch 2 (build 4.6.0.2918) for Windows should immediately replace it with the Patch 2 Repost build.
• If a removal or downgrade of McAfee Agent 4.6.0.2918 has already occurred, you must run the separate Setup_MA46p2fix.exe to repair the current broken state before restarting the client system.
  NOTE: This should be done before upgrading to the McAfee Agent 4.6.0 Patch 2 Windows Repost, but if the repost has already been installed, you can run it post deployment. In either case, the .EXE file must be run on the clients before a restart occurs to repair the current damage.

As a temporary measure, implement the workarounds shown below.

Well I understand what you explained here but i am not surprised... here is the irony

Most of solution we provide here is to remove Mcafee because we have seen countless number of people facing BSOD and freeze because of it and we suggest them to use MSE ( microsoft security essential)..

The only way to resolve your issue is to uninstall mcafee.... and either wait for a resolution or start using MSE...