Any ideas. Trying a couple of new install sets for HP DV6000 series laptops running Vista. Starting to run into issues with other HP and Dell models. Waiting for the info on those.
It is an indication of improperly written MBR record. Check product notes for compatibility info and check if any software conflicting with EEPC had been installed.
I agree with Peter, with a stock HP Vista machine, make sure it didn't already have HP's EEPC or BitLocker enabled.
going to check on the bitlocker. got an acer in today with the same problem. we have a non standard environment so its a lengthy process.
We've been having a rash of this lately, all HP hardware with proper BIOS and driver updates, v5.1.8 EEPC. Custom corporate disk images, no other encryption software, recovery partitons, etc. Ours have been happening on bootup, not past the EEPC login though.
I opened a support ticket with McAfee, they have no records of EEPC causing anything like this except in some circumstances if the autodomain script is used. I'm in a data gathering stage now to provide info back for analysis. Large spreadout environment so this might take some time.
Interestingly we had one tech report back that it happened to his recently built Win7 laptop that didn't even have EEPC installed yet.Message was edited by: mining on 2/5/10 8:13:03 AM CST
We got some more in last night with the same problem. Deleted the recovery partitions and the problem still exists. Put a call in to support as well. All HP's and one Acer. Crashes at pre-boot. When we try to recover the LT the OS is hosed.
HP. These are non-standard laptops. Users bring them in from home. Vista Home OS. Researches buy whatever they want to. I guess they were able to fix some of the media center editions but they didn't provide details.
If keep installing EEPC on systems that have applications potentially incompatible with it, you will contine to be getting problems.
At least check them prior to EEPC installation.
it's absolutely impossible for AutoDomain to cause this error - it doesn't touch the local machine at all ;-)
except in some circumstances if the autodomain script is used. I'm in a data gathering stage now to provide info back for analysis. Large spreadout environment so this might take some time.