Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

10303 ZTIVHDCreate.wsf FAILURE: Verify that a new disk was
created.
10501 ZTIWinRE.wsf FAILURE: Verify a boot drive object was
returned.
10502 ZTIWinRE.wsf FAILURE: Verify a drive was returned:
1 4 See above. In this case, a new disk was found
because the count increased, but the script
couldn’t find it in the list. This should be
impossible.
2 4 The ZTIWinRE script wants to copy the Windows
RE boot image onto the boot volume. In order to
do that, it needs to know the drive letter of that
volume. If there is no drive letter assigned, it will
assign one. But in the case of this error, no boot
drive could be located, or no drive letter could be
assigned. Check the BDD.LOG to see what
happened.
1 3 In this case, a drive object was found but it had no
drive letter. This should be impossible. Check the
BDD.LOG to see what happened.
10503 ZTIWinRE.wsf FAILURE: Verify File: 8 2 The ZTIWinRE script tried to find the
LiteTouchPE_.wim file on the
deployment share, but it wasn’t there. That
typically happens when you haven’t yet updated
the deployment share to generate this WIM file (or
when that architecture isn’t enabled).
10504 ZTIWinRE.wsf FAILURE: Verify REAgentC.exe is found 1 6 The ZTIWinRE script tried to find the REAgentC
command needed to tell Windows RE about the
presence of a new boot WIM file, but it was unable
to find the file. This should not happen.
Page | 39