I'm getting the error "The message you are trying to access is not available." when I try to reach your link.
I'm new to McAfee products, I'm not even sure that this is the tool I'm looking for, nor that this is the good forum section.
What I'm trying to achieve is to recover a disk that seems to have corrupted MBR.
What happened is after a few Windows updates, the system didn't boot. So I went in safemode and I used bootrec /FixMbr (unaware that it was encrypted).
I have a EETECH standalone on usb (read on that forum that emergency boot is able to fix MBR), but it seems it's unable to see USB devices connected to the laptop (most likely because of USB3, according to another post on this forum) so I can't load .xml file from ePO.
I also tried to used EETECH WinPE. Everything seems fine, I load xml, I authenticate using code of the day. But when I try to see the disk content via the file explorer, it says the disk need to be formated (like there's no partition at all). Disk informations show that there is a NTFS partition, so I don't get it.
This disk is on a m2 slot and I don't have a spare laptop to move it (and anyway it would be the same model). I don't know what to try next. I have another person in another team that is facing the issue, and according to our desktop support team, they faced the case numerous times without being able to solve it.
Any help or hint would be GREATLY appreciated.
The link will not be functional unless you create a free account to the McAfee Community forum. There is a lot of supporting content that can only be seen after you login with this account.
Since you tampered with the MBR you will need the machine recovery xml file for this system via ePolicy Orchestrator. It is the only way to obtain and reinstate the DE MBR. The reason you received this error is beacuse it is totally confused about your drive.
1. Make abosultely sure that the XML file you have is for this drive. An early indicator is after you check the machine recovery xml file into detech, it will not prompt you after it is checked in, otherwise it will tell you that it doesnt belong to that machine. If that is 100% you can proceed to reinstate the DE MBR and ignore the error.
After you are done, reboot.
Thanks for your answer.
Concerning the link, I created an account (from which I'm posting). Maybe it's another kind of account ?
About my problem:
- I have the xml file and I'm sure it's for my drive (it was provided by our desktop support team and it is named after my computer netbios name). I have no error when I load it into the tool. I also have the authenticated status (after I enter the code of the day).
- I tried the Restore MBR button. Everything seems fine (no error), bu it still does not boot.
The restoration of the DE MBR would have placed it back to a reasonable boot scenario. Sounds to me like you need to open a support ticket for added assistance. Sorry we couldnt move you to a workable system.
What bother me is that when I load sectors both from MBR and encrypted partition on workspace, I can clearly see readable text on the right BEFORE I did anything (didn't load xml or enter code of the day). On encrypted partition I can read: "A disk read error occured. BOOTMGR is compressed."
And after authenticating and loading XML, when I click remove EE I have an empty list.
Does that mean that the disk is not encrypted ?
When I click Disk Information I see:
Disk ID: 00
ERROR: Disk information not avaiable
But I still have a full list of partitions (every partitions have Recognized: True).
One more thing:
The error I get when I try to boot on system disk is:
Windows cannot start.
Status: 0xc000000f Info: An error occurred while attempting to read the boot configuration data.
I'm tempted to think that the problem is on Windows bootloader, but then why can't I see my disk data on EETECH ?
I tried to look a wider range of sectors on workspace. After a few sectors, I'm starting se see 0000 everywhere. When I click Decrypt Workspace, data appear. So I guess a number of sectors at the beginning of the disk are unencrypted, and the rest is crypted. Not sure if it's normal behavior of not.