This content has been marked as final. Show 5 replies
If the machine you are having the trouble with is not encrypted (or you can boot it all the way up), just run a backup and reimage. I wouldn't work to hard on fixing a problem with one machine when the masses are in need of a significant upgrade.
Most of the issues we had with 4.x went away when we upgraded to 5.x. Sure 5.x has a few bugs too, but the support for it is definitely better since it is a more current product.
Thanks for your reply. As you correctly said I have an option of reimaging as the drive is not encrypted or boot protection is not enabled yet. That is always there for me in the pipeline.
However in most cases these machines will be available only through remote access and without any assistance from support team. It will be only an end user who will be available even for any offline recovery.
Just to avoid this eventuality I am trying to understand the actual issue, given that i have an option to hold this particular machine for some more time.
Later to this post only i have identified that HP's Protection tools consisting of another version of Safeboot are also installed on the machine happy and i have finally managed to unisntall them.
After that we had a hard time booting the machine due to the error 'Sbalg.sys not found', may be due to existence of another version of Safeboot (which was installed by us) Now waiting for the machine to be available again for confirmation. Hope this resolves the issue.
I will post updates.
That sounds like the SBALG.SYS file was delete from C:\Windows\system32\drivers folder. I have heard in previous posts, if you can get it into recovery mode, you can copy serial.sys and name it sbalg.sys. This will allow you to properly clean the registry and remove those dependencies. Once that is done, delete the fake sbalg.sys and reboot. You can then attempt to reinstall the software properly.
Problem is resolved by uninstalling the version of Safeboot that came with HP Protection Tools. Just to avoid spending time upon reboot to resolve the error 'Windows\system32\drivers\sbalg.sys not found' I simply reinstalled the version of Safeboot we use, before rebooting the machine.
This resolved the issue and Safeboot started functioning as expected.
It would have been much easier to figure out if at all HP hasn't kept Safeboot disguised under the name of HP Protection Tools.
but it's not SafeBoot (or McAfee Endpoint Encrypoint for PC's / Device Encryption for PC's) - it's a completley differnet product from HP.
sure, it's an OEM varient of the above, but it's certainly not the same product - there are a lot of pretty important differences, the boot code, management, client etc are all different.