Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

ut in this case a non-zero return code was found.
This shouldn’t happen.
5615 LTIApply.wsf FAILURE: Boot Drive was not found,
required
4 3 After the new OS image was applied and
BootSect.exe was executed, the LTIApply script
wants to use BCDBOOT.exe to create a new BCD
entry for the new OS. In order to do this, it needs
to find the boot volume (adding a drive letter to if
when required) as that needs to be specified on
the BCDBOOT.exe command line. In this case, the
boot drive could not be found.
5616 LTIApply.wsf FAILURE: Verify BCDBootEx 2 4 The BCDBOOT.exe command reported a non-zero
return code. Check the BDD.LOG to see if any
meaningful errors were logged by the utility.
5627 LTIApply.wsf FAILURE: Run DISM.exe 9 2 When applying an image using ImageX, the
LTIApply script applies the unattend.xml file using
DISM.EXE so that the servicing operations (drivers,
patches, language packs) and settings are
processed as expected. But in this case, DISM.EXE
reported a non-zero return code. Typically this
means that the unattend.xml was invalid or
contained invalid settings. Check the DISM.LOG to
see what the actual failure was.
5650 LTIApply.wsf FAILURE: Verify Directory:
5651 LTIApply.wsf FAILURE: Verify Directory: \
5628 LTIApply.wsf FAILURE: Boot Drive was not found,
required
3 5 The LTIApply script is attempting to find the folder
containing the files needed to perform an
unattended install of Windows XP or Windows
Server 2003, but the path specified on the
operating system entry cannot be found. Maybe
the OS has been deleted
3 5 The source folder was found, but the platformspecific
subdirectory (x86, amd64) that is required
for performing an unattended install of Windows
XP and Windows Server 2003 was not found.
Maybe the OS source files are not complete
4 3 After the new OS image was applied, the LTIApply
script wants to use BootSect.exe to install a new
Page | 23