Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

use.”) Then BCDBoot was used to create new boot
files on that volume, but it returned a non-zero
return code. Check the BDD.LOG to see what
happened.
6704 ZTIBDE.wsf FAILURE: Degragment Drive 0 3 This error can never be reported, see error 6726
below.
6705 ZTIBDE.wsf FAILURE: Shrink Drive 6 5 The ZTIBde script has detected that it needs to
shrink the existing volume to create a new boot
volume. But the DISKPART commands to do the
shrink failed. Check the BDD.LOG to see what
happened. Normally, this means that there wasn’t
enough contiguous disk space at the end of the
drive to shrink the volume the specified amount.
6706 ZTIBDE.wsf FAILURE: Testing for more than 1
partition
1 3 After creating a new boot partition (which ZTIBde
will only do if there is at most one existing
partition on the disk), it checks to see if there are
at least two partitions now on the disk. If not, this
error will be generated. This should not be
possible.
6707 ZTIBDE.wsf FAILURE: Create boot files 1 3 After creating a new volume, ZTIBde recreates the
boot files on that new volume using BCDBoot. This
error happens when BCDBoot returns a non-zero
return code. Check the BDD.LOG to see what
happened.
6701 ZTIBDE.wsf FAILURE: Configure Protectors 6 7 As part of the configuration process, the ZTIBde
script configures the BitLocker protectors that
were specified. This error means that one or more
of the protectors couldn’t be configured. Check
the BDD.LOG to see which one couldn’t be
configured.
6708 ZTIBDE.wsf FAILURE: Encrypt the disk. 0 7 The ZTIBde script instructed BitLocker to begin the
encryption process, but this request failed. This
error is impossible because the script function
called for this will signal error 6710 (below) before
the script has a chance to report this one.
Page | 28