This content has been marked as final. Show 7 replies
use SafeTech to decrypt the machine (login to SBFS using your user/password), then you'll have to clean up by uninstalling the products.
Okay.. I manage to get on hold the laptop.
Using SafeTech with Authenticate to Database no drive has been detected..
Using Wintech resulting BlueScreen
The issue is Drive Encryption for HP ProtectTools screen has been replacing our default Safeboot screen.
The Drive Encryption for HP ProtectTools screen Somehow not quite working with our safeboot.
I can ONLY do recovery from this screen.
The login token seem not functional.
Maybe can work with some tweak? Anyone know how?
Maybe i don't really need to remove safeboot afterall..
owh maybe i need to read through on Drive Encryption for HP ProtectTools document..
and wonder how it's replacing our Safeboot login screen..
As I said, use SBFS, not the database - there's nothing in the database for this machine...
what specifically is wrong with your logon token? What's the exact error?
yeap when authenticate with SBFS Hp Drive Encryption Protect Tools screen appeared.
No error but it's can't work with SafeBoot although the screen apeard with "Secure with Safeboot" We can scroll down names but can't type password..
virtual keyboard also not working
the only thing work from HP Drive Encryption protect tools is recovery options.
Since it's not working we using recovery to boot and remove Safeboot, remove any hp tools configuration and install Safeboot back.
HP Drive Encryption Login looks cool but doesn't work.
The reason you are getting Blue Screen could be due to the HDD be in AHCI Mode i.e. SATA. You will have to set it to IDE in BIOS and then try booting with Wintech.
Once you are through with this just perform emergency boot and uninstall HP Protect tools.
Please note when you uninstall HP Protect tools it will remove SBalg.sys and Safeboot.sys files from Windows Directory, so keep a copy of Original Safeboot files and after uninstalling HP Protect tools immediately copy these to files and then reboot.
If you don’t do this carefully, then there are chances that you OS may crash again and further it is a lengthier process to recover.
i do agree with you... while performing recovery once, i discovered that because of the SATA controller, i could not see the C:\ drive. However, fundamentally, when the disk is encrypted with another algorithm (used by HP), then that is a valid reason that the disk is not being visible.
Well, i shall get back tomorrow with some information, as some of my folks did the same mistake... It might be of some help.
Thanks for valuable Tips..