Intel® NUCs
Support for Intel® NUC products
Announcements
The Intel sign-in experience has changed to support enhanced security controls. If you sign in, click here for more information.
12755 Discussions

NUC7i7DN Bitlocker + Hardware SSD encryption = OPAL password prompt on every boot??

JClem3
Beginner
1,917 Views

I have a BLKNUC7i7DNH1 and enabled hardware encryption on my 860 EVO.

Now, every time I turn on or reboot the computer, the UEFI firmware asks for an Admin password. I hit enter a few times, and then it asks for a User password. I hit enter a few more times, and I get a UEFI error message saying the drive can't be unlocked and something about "OPAL". Then Windows 10 Pro boots up normally.

I am using UEFI BIOS firmware version 0049.

0 Kudos
9 Replies
idata
Employee
693 Views

Hello josephclemente

 

 

Thank you for joining the community.

 

 

If you have a BIOS password set on the UEFI BIOS you can try to clear BIOS password following these steps:
  1. Find and remove onboard configuration jumper.
  2. Plug in the computer to the power source and power on the computer.
  3. The computer displays the Config Menu.
  4. Select [2] Clear BIOS User and Supervisor Passwords.
  5. Power off the computer and disconnect it from the power source.
  6. Place the configuration jumper back to its original position.
  7. Replace the cover.
  8. Plug in the computer to the power source and power on the computer.

 

Reference link:

 

 

https://www.intel.com/content/www/us/en/support/articles/000007242/mini-pcs.html https://www.intel.com/content/www/us/en/support/articles/000007242/mini-pcs.html

 

 

In case of a password on the Samsung SSD 860 EVO, I would recommend getting in contact with the manufacturer to delete the password.

 

 

Regards,

 

Leonardo C.

 

JClem3
Beginner
693 Views

It is an incompatibility with Samsung's hardware encryption and the NUC7i7DN's current firmware.

I am currently using Bitlocker in software encryption mode instead to get around this issue. If I enable hardware encryption, the Intel firmware thinks I have to enter a password which should not be happening. If I keep hitting "Enter" repeatedly without a password, the drive will unlock anyway and boot Windows just fine.

idata
Employee
693 Views

Hello josephclemente

 

 

Thank you for your response.

 

 

I would like to gather more information about the configuration you have on the computer. Please attach to this thread the TXT file the Intel® System Support Utility will generate: https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility

 

Steps to save the report:
  1. Run the utility.
  2. Click on "Scan" to get the scanned system.
  3. Once the scan is complete click on "next".
  4. Use the "save" option, save the report to your desktop.
  5. To attach a file, you must click the "Attach" option on the bottom right-hand corner of the response box.

 

Regards,

 

Leonardo C.

 

JClem3
Beginner
693 Views

OK, the report is attached to this response.

idata
Employee
693 Views

Hello josephclemente

Thank you for your response.

 

 

I would like to verify that the hardware encryption that he is using is the TPM feature that comes with the Intel® NUC?

 

 

Could you please access BIOS and sent me a picture of the security tab?

 

 

Regards,

 

Leonardo C.

 

idata
Employee
693 Views

Hello josephclemente

 

 

I was checking your case and would like to know if you need further help. If so, please do not hesitate in replying back.

 

 

Regards,

 

Leonardo C.

 

JClem3
Beginner
693 Views

Hello,

I have attached the screenshot of the Security tab. Right now Bitlocker is set to use software encryption in order to avoid seeing the password prompt on every boot.

idata
Employee
693 Views

Hello josephclemente

 

 

Thank you for your response

 

 

Allow me to investigate the case; I will be posting back when news becomes available.

 

 

Regards,

 

Leonardo C.

 

JClem3
Beginner
693 Views

I have upgraded the firmware to 0052 and this issue is resolved.

Reply