We have recently upgraded our EEPC from 5.1.9 to 5.2.5. We had upgraded over 2,500 machines without any problems, but over the last few weeks we have gotten several machines that after the upgrade will not boot and get an error message. A few of the machines have gotten an error stating that the "wrong version is installed" and others are getting "Error: 0xe0050001 - Endpoint Encryption for PC is not installed".
Has anyone else seen this? If so, were you able to get it fixed without re-imaging. We have tried doing an emergency boot, tried removing Safeboot using the Safeboot tools, and also tried mounting the drive to pull of files or look at ini files. None of these options have worked thus far, because the drive is not seen or it will not complete the boot process.
Any assistance is greatly appreciated. I am opening a ticket with McAfee Support today also.
mostly I've seen this where people have mistakenly deployed an old install file group to newer machines, causing a mix of product versions. So, on a machine reporting this error, check the client log for recent file updates.
Our organization has also recently gotten hit with a number of "Error: 0xe0050001" issues. Our clients are currently at 5.2.4. I was able to recover a few systems by doing the following;
- revised recovery instructions -
What instructions did you follow to create Wintech and Safetech? We have the same issues but I'm struggling trying to get the right rescue resources in place.
Thanks.. Your procedure worked like a champ. Now if I could only get Safetech to run off a bootable CD. Floppies are not realistic. I need to distribute this procedure to 50 people. 0 of which have floppies. If you have any tips let me know. I tried using a procedure on this site but it required Nero.
When I got the machine booted up, there was a nice Virus message waiting for me. I guess we have to be extra sensitive when it comes to viruses on encrypted machines.
From a system with "McAfee Endpoint Encryption Manager" installed:
From ImgBurn (highly recommended free burning application for Windows):
I am also getting same error on several machines..
When I perform Restore Safeboot MBR it works for some machine.
1) For some machines after selecting Restore Safeboot MBR it giving the error as 92H..For this error I have performed emergency boot..After that i got the error as e0020001a Disk information not present.
2) For some machines I am unable to select the option "Restore Safeboot MBR" it is in invisible mode.
Could you advice on both case...Thank you in advance.
for 1, most likely you are using the wrong SDB file for the machine - it has probably activated more than once and you picked the wrong object.
for 2, the feature was only added in newer releases, so if a machine was activated prior to this, the SBR won't have been captured at that point, so won't be available in Safe/WinTech.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center