Skip to content

Troubleshoot OS Deployment

The following is a description of the common troubleshooting tools available for CapaInstaller OS Deployment. Some of the common pitfalls are listed with suggestions for solutions.

Log file Description
X:\Logs\OSDBootStrap.log Written in WinPE when the OSD client starts. Contains information about the startup, network and connection to the OS Deployment server.
X:\Logs\OSDClient.log Written in WinPE by the OSD client. Contains information about the selections and every step of the deployment.
X:\Windows\Logs\Dism\dism.log Written in WinPE when the image is applied and drivers are added.
<ScriptName>.log and CapaInstaller BaseAgent.log Written in WinPE to X:\Program Files\CapaInstaller\Client\Logs when OSD scripts and the CapaInstaller agent run.
C:\osdlogs Just before the client reboots, the OSD client copies the log files from X:\Logs to the osdlogs folder on the drive that Windows was deployed to.
Client log folder If the OS Deployment server has access to it, the OSD client also uploads its log files to the server during the deployment. You set the folder in the console options under OS Deployment → OSD Client installation logs → Client log folder. The folder is located on the Back-end server.
OSDLoader.log and OSDGUI.log Written to X:\Logs by the legacy OSD client (OSDLoader and OSDGUI) that legacy BIOS clients use unless Use OSDClient for Legacy clients is selected in the console options.
Console log Contains information about all operations conducted from the CapaInstaller console. See CapaInstaller log files.
SETUPAPI.log This log contains valuable information about the MiniSetup process and can often help to locate hardware-specific problems that occur during the MiniSetup process.

In WinPE, you can open the OSD client, bootstrap, DISM and base agent logs from the OSD client’s menu.

  1. All logs for the device from the Client log folder on the Back-end server. You don’t need physical access to the device. Earlier runs may be kept as zip files in a History subfolder. Include them, so you can compare a failed run with one that worked.
  2. A photo of the screen that shows the step number and the last line.
  3. The model name, the BIOS/UEFI version, the BIOS storage mode (RAID On/Intel VMD or AHCI), and whether Secure Boot is enabled.
  4. The CapaInstaller version and build number.

Each step is logged between a Step N - start line and a Step N - done line. The last start line without a matching done line is where the deployment stopped.

Look for Tells you
Modelname pulled: The model as WinPE detects it.
UEFI Boot: True or UEFI Boot: False The boot mode.
Builddiskpart : disk: lines in step 6 Which disks WinPE can see, and their sizes. This is the quickest way to spot a missing storage driver.
OS Deployment Done! The WinPE phase finished. Problems after this point happen when Windows starts.
Step 30 CleanUpBCD followed by multiple indistinguishable devices More than one disk has an EFI system partition.
Err lines Errors. Some are harmless. For example, LoadPartition failed with System.NullReferenceException is also logged in successful runs.
Symptom Possible cause Solution
Unable to PXE boot the client The BIOS/UEFI isn’t set up for network boot, or the boot ROM is disabled. OS Deployment and PXE Boot Issues
Unable to load the boot image The DHCP options don’t point to the cipcc.0 file, or the cipcc.0 priority settings are wrong for the network. If PXCONFIG.EXE has cipcc.0 open, no clients can boot from it until the file is closed. OS Deployment and PXE Boot Issues
Unable to load WinPE: Status: 0xc000000f The boot image (WIM) was mounted or changed with an unsupported tool, such as imagex.exe. Rebuild the boot image.
WinPE reports no disk, or the deployment hangs at step 7 Apply disk Configuration The storage driver is missing in the boot image. This is typical for Intel VMD in RAID On mode. Solution 13
WinPE reports a missing network driver The NIC driver is missing in boot.wim. Solution 9
The device starts WinPE again instead of Windows The firmware boot order doesn’t start Windows Boot Manager. Solution 8
A blue Recovery screen or a Windows Boot Manager error after OS Deployment Done!, for example 0xc0430001 A Windows start-up problem, not a WinPE problem. Solution 14
Windows stops with INACCESSIBLE_BOOT_DEVICE (stop code 7B) after deployment The BIOS storage mode (RAID On/Intel VMD or AHCI) was changed after Windows was deployed. Set the storage mode back to the mode used during deployment. To use the other mode, change it and deploy again.