This problem could be caused by either incompatible Master Boot Record (MBR) or incompatible memory (BIOS bug). Please read the following problem descriptions carefully and select the appropriate solution.
Problem 1 caused by incompatible Master Boot Record(MBR)
You started the Safecode Defencecure setup in Windows. In the end, the setup prompted you to restart the computer. You restarted the computer, and Safecode Defencecure started the pre-OS recovery console installation. Unfortunately, the pre-OS recovery console installation progress bar reached 100%, and the computer wouldn’t boot into Windows after that.
- Reboot the computer.
- Press the HOME key to enter Safecode Defencecure pre-OS Recovery Console.
- While in the pre-OS Recovery Console, select Tools->Program settings.
- Type “UseStdMbr=1” in the settings (without the quotation marks) and press Enter.
- Restart the computer and check if it’s able to boot.
- If the computer still cannot boot into Windows. Follow the same steps above and set “UseStdMbr=2” (basically trying to use different MBR settings to boot the computer).
- If the steps above had failed to make the system boot—type “Resetmbr=1” in the settings, and press Enter.
- This will revert the pre-OS installation process. Windows should boot up after.
Problem 2 caused by incompatible memory (BIOS bug)
You started the Safecode Defencecure setup in Windows. At the end, setup prompted you to restart the computer. You restarted the computer, and you see a black screen with a blinking cursor after BIOS screen (Safecode Defencecure pre-OS recovery console installation did NOT even happen).
- Download our support utility, Fix Tools.
- Use the Fix Tools to restore the computer’s MBR.
- Windows should boot up after restoring the MBR.
After you boot back in the Windows, please send the following 4 setup log files to [email protected] for technical assistance:
setup.log, subconsole.log, 128.dat, Shield.dat
These files can be found in the c:\program files\shield folder.