Showing results for 
Search instead for 
Did you mean: 

Technical Details


I was wondering if anyone would be able to give me some technical information on exactly what Endpoint Encryption does to the MBR?

Does it create a new partition within the MBR, or does it create a new MBR?

We have had cases where laptops have stopped booting into Windows some point after Endpoint Encryption, and our support staff have ran FIXBOOT and FIXMBR which has then created a whole load of work for us having to use Wintech to try and gain access to the data.

If this was to happen again, would simply placing a new Image on a currently encrypted drive render the disk useable again, albeit in an unencrypted state and as a clean install?
2 Replies

RE: Technical Details


We ran into the same thing and after some looking into the issue we found that the software was updating the number of heads (Sides) for the boot partion.

00B0 00 02 08 00 00 .....
0010 00 00 00 00 00 F8 00 00 3F 00 FF 00 3F 00 00 00 ........?...?...
0020 00 00 00 00 80 00 80 00 AE 39 D7 00 00 00 00 00 .........9......
0030 04 00 00 00 00 00 00 00 8D EF 00 00 00 00 00 00 ................
0040 F6 00 00 00 01 00 00 00 FC 5D E1 A4 99 E1 A4 B4 .........]......
0050 00 00 00 00 .....

We creating a new installation set without the "EEPC51 Option: update the number of sides reported in the OS boot sector" file set and under General>Miscellaneous> check "enable bootdisk compatibility."

I am not sure about the re-imaging the encrypted drive, but we have also found pushed the software without forcing the encryption initially and then if all goes well forcing later.

RE: Technical Details

we replace the code in the mbr with our own boot code, we don't change the partition info (unless it needs fixing and then only if you add the update sides tool to the install package).

that's all we do, no funny new partitions etc, just new boot code.