I think you are wasting time trying to circumvent SAfeBoot encryption and tweaking the MBR and SFBR. Whenever a file is written to supported storage media the SafeBoot Content Encryption filter executes assigned encryption policies and encrypts the file if applicable. When an application later reads the file, the encryption filter automatically decrypts the file when it is read into memory. The source file always remains encrypted on disk.
When the application closes the file, the memory is wiped and the original file is still encrypted on disk. No decrypted traces of the file remain in RAM.
Encrypted folders and files are always visible to the user. Thus, the user can search for, and will recognize files and folders as before encryption. A small key hole icon can be optionally attached to the file or folder icon, marking it as encrypted.
You can create a policy from the SafeBoot Management Centre, and then create an install set from it. When the SafeBoot Content Encryption client then is installed, the user that logs on will be forced to retrieve the proper policy assigned to him/her in the central database.
With central management using the SafeBoot Administration System, and distribution of encryption keys using the secure SafeBoot Server, it is easy to allow sharing of encrypted files within an organization. By assigning groups of users to encryption keys, the users in the group can exchange and read encrypted files like any other file, without noticing any difference. Users not assigned to the key will not be able to read files encrypted with that key.
SafeBoot Content Encryption encrypts the Windows' pagefile. This feature is automatic and cannot be configured or disabled. The pagefile is encrypted with a temporary encryption key created at each boot occasion. Thus, the pagefile encryption key is discarded once the computer shuts down, while the pagefile still is encrypted.
