-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Operating System and Recovery
- Re: McAfee drive Encryption. Fatal error 0xEE0E0001 failed t...

Create an account on the HP Community to personalize your profile and ask a question
06-16-2017 08:41 PM
06-18-2017 03:58 AM - edited 06-18-2017 03:59 AM
Hello @G_A7
Welcome to the HP Support forum. Thank you for posting.
Is this PC your personal one or company owned asset ? McAfee Drive Encryption is a software typically found on the PCs of business computers, corporations. If this is your work PC, please contact your company's IT support team and your local HelpDesk.
Any McAfee "fatal" error cannot be fixed remotely and requires onsite assistance. If the error you post is correct, this is what it is
0xEE0E0001 | Authentication User Interface definition file failed |
The issue you now have is probably caused because McAfee's PreBoot File System (PBFS) got corrupted. PBFS is stored on the HDD's Master Boot Record (MBR). This happens often with McAfee.
Some general tips you need to follow with regards to McAfee DE and Windows:
- Windows 10 needs to be deployed with Secure Boot OFF and Legacy mode ON - settings in the BIOS
- Ensure BIOS is updated to the latest version and check the above settings
Ensure McAfee DE is the latest version installed.
You need to contact your security administrator(s) and work with them to perform Emergency Boot > https://kc.mcafee.com/corporate/index?page=content&id=KB71868
Emergency boot is performed using XML file from the McAfee's ePO console and using DETech disc.
Emergency boot basically places Windows MBR, boots to Windows desktop. McAfee Agent communicates with the ePO, notifies the ePO about the Windows MBR , not McAfee MBR and eventually replaces and repairs the boot data/PBFS/MBR
If Emergency boot does not work, PC needs to be reimaged.
For further steps, get in touch with the company's security admins, disable McAfee PBA screen or get in touch with McAfee Technical support > https://support.mcafee.com/ServicePortal/faces/wcnav_defaultSelection?_afrLoop=1571452459502000&_afr...
If your company policy requires PBA screen (preboot authentication) but McAfee PBA is set to disabled by policy, you can enable BIOS start up password for enhanced security.
Hope this answers your queries. Provide your feedback/update.
Your company IT support may also reach to McAfee business support >> https://support.mcafee.com/
*** HP employee *** I express personal opinion only *** Joined the Community in 2013
06-19-2017 12:50 AM
Hi,
The error message I am getting is: Failed o display error message box.
06-19-2017 08:29 AM
Hi @G_A7
If decryption process has started but has failed somewhere in the middle during the decryption process, chances for successful data extraction is so low, minimal, pretty much zero. If the process has been stopped, interrupted, data is semi-encrypted, semi-decrypted and process needs to be started at same point where it stopped and this is the most difficult part.
If decryption hasn't been attempted yet, do not try it but first boot the computer using DETech tool (WinPE or A43), unlock the storage drive (HDD or SSD) using McAfee DETech tool and try to browse the storage drive to see if you will be able to browse the files (WinPE/CMD/A43)
Please, note that any encryption software (like McAfee) is there for data protection and McAfee does not guarantee successful data recovery. It is always recommended that you back-up your most important files and store them somewhere else (don't store them only in your HDD).
The 3 security principles (CIA) include: confidentiality, integrity and availability
You have come to a over-protective environment and data is no longer available/accessible, therefore, not protected.
Good luck. 🙂
*** HP employee *** I express personal opinion only *** Joined the Community in 2013