we are using McAfee EE ver 5.2.4
while installing EE during the pre-boot installation phase, the PC was accidentally rebooted, i,e. the pre-boot installation was probably not completed. After restart, it was not able to boot to windows 7 (missing OS). There was no EE login authentication too.
Using the Windows Recovery option of the laptop, i am able to see a Windows 7 installation but the partition size is 0mb.
I boot up with WinTech CD, but using "authenticate from SBFS" gives the error 0xe0050001, so i used the sdb file instead.
After authentication and authorization, Disk Information shows error e002000a, but i am able to see the partitions and the respective drive letters. I am also able to view the files using the "A43 File Management Utility", so I copied the critical files to an external USB HDD.
From WinTech, Restore EEPC MBR is greyed out. Also unable to use Safetech Emergency Boot due to no disk information (e002000a).
How can i make the HDD bootable again?
Any help will be greatly appreciated.
Many thanks for your reply.
After some attempts (System Recovery from DVD worked one time, and after that i used fixmbr), i was able to boot to windows.
I checked the hdd for bad sectors but there were none. So i proceeded to install EE again. This time I made sure that pre-boot installation was complete and after the restart, i was able to login to EE.
unfortunately, after the login screen of EE, the following appears:
Resetting hardware ...
Disabling mouse ...
Starting operating system ...
Missing operating system
This time i was able to use WinTech's Remove EEPC, although i'd still need to use system restore's fixmbr before windows can boot up.
The laptop is a Fujitsu LH530, BIOS is Phoenix Tech ver 1.03 (dtd 15/1/2010), OS is Win 7 Pro SP1 x64. Are there any known issues with this laptop?
none reported that I could see with a quick search, but this is quite an old version of EEPC - you should try with the current version.
To the best of my knowledge no, I would suggest that you install 5.2.12 since there has been a few solutions added to the product patches since the 5.2.4 patch.
If after that you are still experiencing issues please engage our support and they will be able to help you further.