Why does the window asking you to enter a password to decrypt the partition with the Win OS appear earlier than the window with the bootloader menu?

Echor

New member
Hello.

I am studying the issue of existing encryption programs for PCs in the world as a private researcher.
My research has led me to you today.
Understand that due to the vastness and diversity of existing schemes and methods, I am physically unable to study each method at the application level.
First, I will present you with the input data - Hard disk [Harddisk0] with the MBR partition scheme. BIOS system. Windows 10 OS. The active partition with the bootloader is located on Harddisk0\Partition1. The system partition is located on Harddisk0\Partition2 - these input data are not important in themselves and may be different in each case.
For encryption, the basic version of dcrypt_setup_1.1.846.118.exe was taken
The system partition [Harddisk0\Partition2] with Windows 10 OS is encrypted.
In addition, the hard disk has password protection via BIOS from the manufacturer [Dell].
After encryption and reboot (when turning on again) the PC and unlocking the hard drive protection (entering the password set earlier via BIOS), the bootloader menu does not appear, as one might expect - after all, only the partition with the OS is encrypted, and the partition with the bootloader is not encrypted. Instead of the boot menu, a window immediately appears asking you to enter a password to decrypt the partition with the Windows OS, as if the partition with the bootloader was also encrypted.
(For example, with the same incoming data and encryption using BitLocker, the boot menu appears earlier than the window asking you to enter a password to decrypt the partition with the OS).
I have a question for you: why does the window asking you to enter a password to decrypt the partition with the Windows OS [Partition2] appear earlier than the window with the bootloader menu?
(After all, the bootloader is on another unencrypted partition Partition1)?

To save time, I decided to write to you first and not encrypt the active partition with the bootloader, although your program allows you to do this without warning about the subsequent loss of boot ability.
And this is my second question: why doesn't the program warn the user about the danger of encrypting the active partition with the bootloader? If your program encrypts the active partition where the boot manager is located, won't the PC become inoperable?

I wrote this letter, which I couldn't send to you by email,
because the address on the page is https://xanasoft.com/contact/
You specified it rather strangely
E-Mail: xanatos david [at] gmail [dot] com (no spaces and add . and @ where indicated)
I don't understand what you mean.

I came to your forum with questions about diskcryptor and wanted to open a new discussion.

Then I saw this question https://forum.xanasoft.com/threads/why-encrypt-first-partition.2669/

which no one answered, including you.

I thought that if I open a new discussion on the forum, my questions will remain unanswered.

That's why I'm writing through this contact form.

I hope for your clarification.
(With concern for the destruction of the democratic order in the World, in connection with the loss of the individual's ability to protect himself from interference from the special services, which are beginning to serve not society - the latest mind-boggling example of a criminal as the US President)


P.S. Also, tell me, are you considering the possibility of translating the diskcryptor program interface into other languages?


P.P.S After I sent the above via the contact form, I did not receive any notification that my request was sent or received.
In order not to be a bore, I did not re-send the request and decided to register and ask my questions on the forum.

Thank you.

Best regards, Echor
 
Back
Top