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
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 188.8.131.5235
). 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 184.108.40.20618) for Windows should immediately replace it with the Patch 2 Repost build.
- If a removal or downgrade of McAfee Agent 220.127.116.1118 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.