[Pauldotcom] Bad Agent on encrypted disk

[Grymoire]

We have a problem. We use a full disk encryption product that is
installed in the BIOS. The systems are Windows XP. The product is
SafeBoot 4.2.

Our IT department deployed a new agent on all laptops too aggressively,
This is what happens
		The system boots up
		The user gives the BIOS username and password
		The Login console shows
		2 seconds passes
		A Blue Screen appears.

I'm trying to think of a way to intercept the login process,
and delete the bad file/program, so we can fis the systems.

Some systems use SafeBook 4.3, and we have a solution for that.
But SafeBoot 4.2 doesn't even have a "Safe Mode" to boot up.

Any ideas? Our IT department has not come up with a solution, and we
have a lot of unhappy users with unrecoverable disks.