cancel
Showing results for 
Search instead for 
Did you mean: 
dans
Level 7

4.5.0.1499 agent upgrade to 4.6.0.3122 blue screen?

Can anyone verify whether a 4.5.0.1499 agent upgrade task to 4.6.0.3122 on Windows 7 causes blue screen? I just did a smoke test on my Mcafee testbed with one catch - I performed a series of windows updates as well as upgraded McAfee agent at the same time. I then rebooted. Now I have a bricked Windows 7 machine. Fortunately this is on a dedicated McAfee Testbed. Too bad McAfee doesn't seem to perform smoketest on there own product and they pawn off the task to customers....for the utmost cost cutting and poor software QA. This could be a unique case where upgrading the agent and windows patch at the same time causes the blue screen. Something I would like to pin point before I roll-out to a few thousand users who could come across a similar deployment snafu, in turn blaming the security team for breaking there computers as they love to do when we upgrade McAfee.

0 Kudos
3 Replies
dans
Level 7

Re: 4.5.0.1499 agent upgrade to 4.6.0.3122 blue screen?

Make that a definitely McAfee 3122 upgrade causing blue screens!

My 2k8 machines plural using McAfee MOVE upgraded from 4.6.2935 agent to 3122 agent bluescreened. No windows updates. Boxes are recovering but the first reboot caused blue screen. The Win7 box is unrecoverable.

0 Kudos
McAfee Employee

Re: 4.5.0.1499 agent upgrade to 4.6.0.3122 blue screen?

This sounds a lot like the issue in KB75956  - this was an issue that affected Patch 2. The article is comprehensive and should help.

HTH -

Joe

0 Kudos
ajha1
Level 9

Re: 4.5.0.1499 agent upgrade to 4.6.0.3122 blue screen?

Hi dans,

The issue mentioned in the KB75956, is mcuh similar to your issue, However, McAfee has addressed the issue in MA 4.6 patch3, if the suggested mentioned as per above comment doesnt help you, then would suggest you to open a Case with McAfee Techinical Support and provide them MER and crash dump logs from the machine where-in you are expeiencing the issue.

- you can also try to upgrade the MA version to 4.8 on one of the machine (having issues) and see whether that resolves the issue

Message was edited by: ajha1 on 19/5/13 4:09:02 AM IST
0 Kudos