System can't boot after used DriveLock HP Support Forum 6110232

Drivelock Hp. Drivelock activated itself on my HP Desktop HP Support Community BIOS lock is related to access to the BIOS or power-on of the machine According to the HP website: DriveLock is an industry standard security feature that helps prevent unauthorized access to the data on specific hard drives

【HP】the hard drive’s security state cannot be changed. Cycle power to
【HP】the hard drive’s security state cannot be changed. Cycle power to from papamamameyou.com

HP DriveLock prevents unauthorized users from booting into your computer and accessing the contents of the hard drive DriveLock locks the content of the storage drive (HDD/SSD, etc) If you lock the power-on process of the machine with BIOS password, you will still be able to access the content of the drive by using a different computer.

【HP】the hard drive’s security state cannot be changed. Cycle power to

According to the HP website: DriveLock is an industry standard security feature that helps prevent unauthorized access to the data on specific hard drives Data protection—DriveLock, Disk Sanitizer, and Secure Erase technology Device security—Boot options and device control HP integrates BIOS capabilities and the HP ProtectTools software, a rich set of security features that works in Windows to enable enhanced security. HP Drive Lock is a proven, time-tested security feature in HP Elitebooks which provides protection against unauthorized data access

【技术分享】惠普笔记本电脑Drivelock常见问题及应用 惠普支持社区 1219816. Data protection—DriveLock, Disk Sanitizer, and Secure Erase technology Device security—Boot options and device control HP integrates BIOS capabilities and the HP ProtectTools software, a rich set of security features that works in Windows to enable enhanced security. DriveLock is an industry standard security feature that helps prevent unauthorized access to the data on specific hard drives

How to perform DriveLock quick setup. DriveLock 7.6.6 and higher supports UEFI Secure Boot If I moved it to a different system with the same firmware, it worked