1-Touch Client Fails to Start

If your computer fails to start after the 1-Touch recovery operation, there are several things you can check to resolve the problem.

Step 1: Check the Boot Priority in BIOS

If you see error messages such as Operating System Not Found or Missing Operating System, verify whether the boot device priority on the BIOS is set to a value of HDD.

Step 2: Check CLRestore.log

Verify that the ClRestore process finished successfully and that all components are restored successfully.

If the ClRestore process finished successfully and all components are restored successfully, the log file is as follows:

====================================================================

FclRestore::PrintRestoreReportStatus() - System State Component Report

FclRestore::PrintRestoreReportStatus() -

====================================================================

FclRestore::PrintRestoreReportStatus() - Component Method Status

FclRestore::PrintRestoreReportStatus() - ---------------------------------------------------------------

FclRestore::PrintRestoreReportStatus() - System Info Archive VSS Writers Successful

FclRestore::PrintRestoreReportStatus() - System Protected Files Legacy Successful

4FclRestore::PrintRestoreReportStatus() - COM+ Database VSS Writers Successful

FclRestore::PrintRestoreReportStatus() - Disk Quotas Legacy Successful

FclRestore::PrintRestoreReportStatus() - Event Logs Legacy Successful

FclRestore::PrintRestoreReportStatus() - WMI Database VSS Writers Successful

FclRestore::PrintRestoreReportStatus() - Offline Files Legacy Successful

FclRestore::PrintRestoreReportStatus() - RegMerge Legacy Successful

FclRestore::PrintRestoreReportStatus() -

=====================================================================

FclRestore::PrintRestoreReportStatus() - End System State Component Report

FclRestore::PrintRestoreReportStatus() -

=====================================================================

Step 3: Verify the Log Files on the Client

To open the command prompt, press the F6 key on the keyboard.
To open the Explorer, press the F7 key on the keyboard.
Verify logs at the following locations:
- X:\xxBMR\OneTouch\LogFiles\
- X:\xxBMR\OneTouch\ClientFiles\restore_client\
- X:\Windows\Temp\

Note

During a 1-Touch recovery, you cannot assign, create, or format the X drive to a new partition because the X drive is used by the client.

Step 4: Verify the Boot Loader Configuration

Verify whether the Boot Configuration Data Store (BCD) is configured correctly. Type the following command to verify the boot configuration.

Important

The drive letter on WinPE might be different than the one displayed when booted on the operating system. Ignore the driver letter mismatch because, after the computer is started, the correct drive letter is set to the correct volume.

C:\>BCDEDIT

Sample Output

bcd_command_execution_sample

Step 5: Fixing the Boot Loader

If the boot loader configuration is incorrect, re-create the BCD store using the following command:
```
C:\Windows\System32>bcdboot.exe c:\windows
```
If the command runs successfully, verify the BCD configuration. For instructions, see Check Boot Loader Configuration.
If the command fails, verify volume and partition details using the following command:
```
DISKPART
 list disk
```
Verify whether the BCDBOOT re-created the BCD store.
If the BCD store shows corrupt entries, after you rename or remove the old BCD store, create a new BCD store.

Note

Make sure to point to the correct store location on your computer.
```
C:\Windows\System32>attrib c:\boot\bcd -h -r -s
```
```
C:\Windows\System32>ren c:\boot\bcd bcd.old
```

Step 5: Verify Disk, Partition, and Volume Configurations

Verify volume and partition details using the following command:

DISKPART
lis disk

Step 6: Repair the Boot Sector

Repair the boot sector using the following command for all volumes:

C:\Windows\System32>BOOTSECT.exe /nt60 All

Repair the boot sector using the following command for a single volume:

C:\Windows\System32>BOOTSECT.exe /nt60 c:

To repair an Windows XP boot sector, run the following command:

C:\Windows\System32>BOOTSECT.exe /nt52 All

If required, use the force option to create a forced dismount of the partition.

D:\boot\bootsect /nt60 F: /force

Step 7: Run the System File Checker Tool

Verify that the files are not corrupted using the following command:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

After you run this command, a log file is generated at the following location, by default:

%WinDir%\Logs\CBS\CBS.log