locked
Windows 10 1703 image failed on computer with DVD. RRS feed

  • Question

  • We are having problems installing our Windows 10 1703 build on computers that have dvd installed.

    The installation is able to distribute the Windows 10 1703 image and everything goes okay until the first boot when the computer with DVD shutdown and does not continue. When we start the computer, the installation continues. When we remove the DVD the computer image is distributed as it’s supposed to.  

    Thursday, October 5, 2017 1:28 PM

All replies

  • Could you please be a bit more specific as to when the shutdown happens? Before the specialize phase? That would be highly unusual, but then again, stranger things have happened. Any insights in the BDD.log?

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, October 5, 2017 1:39 PM
  • This happens after the Install Operating system task when it boots the first time.

    But for the computers with DVD it shuts down the computer instead restarting.

    Thursday, October 5, 2017 1:50 PM
  • This is ... weird, to say the least. I never ever seen any issues even remotely resembling what you are describing above, so I am going to take a few stabs in the dark. Maybe we can narrow it down. How are you booting your systems? PXE? USB? DVD? Also, could you post a sample BDD.log? I do not have high hopes that it contains any clues, but taking a look never hurts.

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, October 5, 2017 4:13 PM
  • We boot via PXE.

    I've copied the relavent part of BDD.LOG

    As you see from the log it shutdown and continues 16 minutes later when I manualy start the computer and it compliets as it should.

      Console > The operation completed successfully. LTIApply 09.10.2017 12.13.28 0 (0x0000)
    Return code from command = 0 LTIApply 09.10.2017 12.13.28 0 (0x0000)
    Property LTIDirtyOS is now = TRUE LTIApply 09.10.2017 12.13.28 0 (0x0000)
    The image \\x\Windows10_1703_Deployment$\Operating Systems\W10_1703_Off16_ver10\W10_1703_Off16_ver10.wim was applied successfully. LTIApply 09.10.2017 12.13.28 0 (0x0000)
    Event 5625 sent: The image \\x\Windows10_1703_Deployment$\Operating Systems\W10_1703_Off16_ver10\W10_1703_Off16_ver10.wim was applied successfully. LTIApply 09.10.2017 12.13.28 0 (0x0000)
    About to run command: "\\x\Windows10_1703_Deployment$\Tools\X64\bootsect.exe"  /nt60 C: LTIApply 09.10.2017 12.13.28 0 (0x0000)
    Command has been started (process ID 2824) LTIApply 09.10.2017 12.13.29 0 (0x0000)
      Console > Target volumes will be updated with BOOTMGR compatible bootcode. LTIApply 09.10.2017 12.13.29 0 (0x0000)
      Console > C: (\\?\Volume{8f5e6008-0000-0000-0000-107d00000000}) LTIApply 09.10.2017 12.13.30 0 (0x0000)
      Console >     Updated NTFS filesystem bootcode.  The update may be unreliable since the LTIApply 09.10.2017 12.13.30 0 (0x0000)
      Console >     volume could not be locked during the update: LTIApply 09.10.2017 12.13.30 0 (0x0000)
      Console >         Ingen tilgang. LTIApply 09.10.2017 12.13.30 0 (0x0000)
      Console > Bootcode was successfully updated on all targeted volumes. LTIApply 09.10.2017 12.13.30 0 (0x0000)
    Return code from command = 0 LTIApply 09.10.2017 12.13.30 0 (0x0000)
    Find the boot drive (if any) [Sann] [10.0.15063.296] [Usann] LTIApply 09.10.2017 12.13.30 0 (0x0000)
    New ZTIDiskPartition : \\MININT-IIM5CD7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-IIM5CD7\root\cimv2:Win32_LogicalDisk.DeviceID="V:" LTIApply 09.10.2017 12.13.30 0 (0x0000)
    New ZTIDisk : \\MININT-IIM5CD7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LTIApply 09.10.2017 12.13.30 0 (0x0000)
    Found bootable drive (No Boot File Test) [ V: ]: \\MININT-IIM5CD7\root\cimv2:Win32_LogicalDisk.DeviceID="V:" LTIApply 09.10.2017 12.13.30 0 (0x0000)
    Ready to Prepare boot partition: V: LTIApply 09.10.2017 12.13.30 0 (0x0000)
    About to run command: cscript.exe //nologo "\\x\Windows10_1703_Deployment$\Scripts\ztiRunCommandHidden.wsf" ""\\x\Windows10_1703_Deployment$\Tools\X64\BCDBoot.exe" C:\windows /l nb-NO  /s V:" LTIApply 09.10.2017 12.13.30 0 (0x0000)
    Microsoft Deployment Toolkit version: 6.3.8443.1000 ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    Write all logging text to \\x\windows10_1703_deployment$\logs ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    Validating connection to \\x\windows10_1703_deployment$\logs ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    Mapping server share: \\x\windows10_1703_deployment$ ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    Already connected to server x as that is where this script is running from. ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    About to run command: \\x\Windows10_1703_Deployment$\Tools\X64\BCDBoot.exe C:\windows /l nb-NO  /s V: ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    Command has been started (process ID 2972) ztiRunCommandHidden 09.10.2017 12.13.30 0 (0x0000)
    ZTI Heartbeat: command has been running for 0 minutes (process ID 2972) ztiRunCommandHidden 09.10.2017 12.13.31 0 (0x0000)
    Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 2972) ztiRunCommandHidden 09.10.2017 12.13.31 0 (0x0000)
      Console > Boot files successfully created. ztiRunCommandHidden 09.10.2017 12.13.31 0 (0x0000)
    Return code from command = 0 ztiRunCommandHidden 09.10.2017 12.13.31 0 (0x0000)
    Command has returned: 0 LTIApply 09.10.2017 12.13.31 0 (0x0000)
    Run Command: X:\WINDOWS\SYSTEM32\bcdedit.exe /Store "V:\boot\bcd" /timeout 0 LTIApply 09.10.2017 12.13.32 0 (0x0000)
    BCD> Operasjonen er utf.rt. LTIApply 09.10.2017 12.13.32 0 (0x0000)
    BCDEdit returned ErrorLevel = 0 LTIApply 09.10.2017 12.13.32 0 (0x0000)
    Created scratch folder. LTIApply 09.10.2017 12.13.32 0 (0x0000)
    Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml LTIApply 09.10.2017 12.13.32 0 (0x0000)
    Copied unattend.xml to C:\Windows\Panther for image apply. LTIApply 09.10.2017 12.13.32 0 (0x0000)
    About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch LTIApply 09.10.2017 12.13.32 0 (0x0000)
    Command has been started (process ID 1388) LTIApply 09.10.2017 12.13.32 0 (0x0000)
      Console > Deployment Image Servicing and Management tool LTIApply 09.10.2017 12.13.32 0 (0x0000)
      Console > Version: 10.0.15063.0 LTIApply 09.10.2017 12.13.32 0 (0x0000)
      Console > Image Version: 10.0.15063.0 LTIApply 09.10.2017 12.13.34 0 (0x0000)
      Console > The operation completed successfully. LTIApply 09.10.2017 12.18.32 0 (0x0000)
    ZTI Heartbeat: command has been running for 5 minutes (process ID 1388) LTIApply 09.10.2017 12.18.32 0 (0x0000)
    Event 41003 sent: ZTI Heartbeat: command has been running for 5 minutes (process ID 1388) LTIApply 09.10.2017 12.18.32 0 (0x0000)
    Return code from command = 0 LTIApply 09.10.2017 12.18.33 0 (0x0000)
    LTIApply processing completed successfully. LTIApply 09.10.2017 12.18.33 0 (0x0000)
    Event 41001 sent: LTIApply processing completed successfully. LTIApply 09.10.2017 12.18.33 0 (0x0000)
    Command completed, return code = -2147021886 LiteTouch 09.10.2017 12.18.34 0 (0x0000)
    Property LTIDirty is now = FALSE LiteTouch 09.10.2017 12.18.34 0 (0x0000)
    If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation. LiteTouch 09.10.2017 12.18.34 0 (0x0000)
    Property OSDTargetDriveCache is now = DIRTY LiteTouch 09.10.2017 12.18.34 0 (0x0000)
    LTI initiating task sequence-requested reboot. LiteTouch 09.10.2017 12.18.34 0 (0x0000)
    Event 41017 sent: LTI initiating task sequence-requested reboot. LiteTouch 09.10.2017 12.18.34 0 (0x0000)
    Property start is now =  LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    Microsoft Deployment Toolkit version: 6.3.8443.1000 LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    Write all logging text to \\x\windows10_1703_deployment$\logs LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    Validating connection to \\x\windows10_1703_deployment$\logs LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    Mapping server share: \\x\windows10_1703_deployment$ LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    Mapped Network UNC Path Z:  = \\x\windows10_1703_deployment$ LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    Found Existing UNC Path Z: = \\x\windows10_1703_deployment$ LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    Successfully established connection using supplied credentials. LiteTouch 09.10.2017 12.34.23 0 (0x0000)
    ZTIUtility!GetAllFixedDrives (Usann) LiteTouch 09.10.2017 12.34.23 0 (0x0000)

    Monday, October 9, 2017 1:55 PM
  • Could you post the entire BDD.log please? It makes it so much much easier to parse for possible causes using CMtrace tool. 

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Monday, October 9, 2017 2:36 PM
  • Tuesday, October 10, 2017 11:17 AM
  • Thanks. I just took a quick glance at the log - is the TS reboot being initiated before MDT executes the POSTINSTALL phase? You OSD also never goes into the STATERESTORE phase. It is somewhat difficult to understand what is going on without seeing your TS - these two things jump out from the initial perusal.

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Tuesday, October 10, 2017 1:41 PM