Can't find windows boot manager after Disable PBA and Disable lockingrange

[fong09]

I am using sedutil on Windows, and the processes like loading PBA, enable lockingrange, and set lockingrange work fine. However, after I disable PBA and disable lockingrange, I am unable to find the Windows OS upon reboot. I have tried many different BIOS platforms, and this error occurs on all of them.I want to ask why this happens when I disable PBA and locking range, and the system cannot detect the boot partition for Windows BIOS.

I tried using the Bcdboot method to rebuild the boot partition. This method successfully recovered the missing OS boot manager. After performing Bcdboot once, no matter how many times I lock or unlock the device, the boot manager can always be recognized in the BIOS.

I want to know what happens during the process after disable PBA and disable lockingrange on windows that causes the BIOS to fail to recognize the device.

Thanks!

[r0m30]

hi,
Try this:
Set mbrdone on
set lockingrange 0 rw < rest of command >

I believe that when you disable locking some of the internal state flags are not set to be consistent with over arching state.

[fong09]

hi, thank you for your responses. I have two questions for this:

1.The commands you provided, should I run them after sedutil-cli –-setMBREnable off or after sedutil-cli -–disableLockingRange 0 , or after both?

2.Regarding the unlocking process, do these two commands:

sedutil-cli -–disableLockingRange 0

sedutil-cli –-setMBREnable off

need to be executed in a specific order? Will their execution order have any impact?

[neo125874]

@r0m30 hello, same here, using nvme ssd on windows and follow
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Encrypting-your-drive

it works using PBA, but when trying to disable Locking and the PBA
then couldn't boot into windows (the ssd not locked and the data exist)