none
MDT Failure with Unreadable Summary Screen

    Question

  • I have a system fail an OSD task sequence around half way through and the failure screen HTA popup that would normally be salmon colored with a description of what the problem was, popped up white with no readable text.  It was faded and blank as if "not responding" trying to load.

    What would cause this issue?



    • Edited by MyGposts Friday, February 19, 2016 5:43 PM
    Friday, February 19, 2016 5:41 PM

Answers

  • Just to follow up, root cause seems to be loss of network connectivity during the deployment process. We found that Windows Update was loading network drivers, and the timing of the network driver swap was causing random interruptions to the deployment process.

    Fix was ensuring that the most-up-to-date NIC drivers are in the deployment share, and also temporarily disabling Windows Update by GPO or by registry during the deployment process. To do this, implement the following Group Policy setting:

    Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings\Turn off Windows Update device driver searching
    = Enabled
    (or the underlying, equivalent registry key)


    • Proposed as answer by Frank E Lesniak Tuesday, November 15, 2016 6:36 PM
    • Edited by Frank E Lesniak Tuesday, November 15, 2016 9:25 PM Clarified how to disable driver updates via Windows Update
    • Marked as answer by MyGposts Tuesday, November 15, 2016 11:57 PM
    Tuesday, November 15, 2016 6:36 PM

All replies

  • I've the same issue (MDT 2013 Update 2), but i've resolve the problem of deployment.

    Open command line with F8 key and open notepad to find the log.

    Friday, February 19, 2016 7:18 PM
  • If you set SLShare=\\Server\Share then logs will copy to that location. Or as suggested above you can look at the logs on the machine.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Saturday, February 20, 2016 4:30 PM
    Moderator
  • We are seeing this as well. MDT 2013 Update 2 deploying Windows 10 1511 (specifically, 1511.1, the February 2016 updated ISO). I have reviewed the task sequence logs, and the root-cause for TS failure appears to be a failed application. However, like the OP, I would expect this to result in a salmon / red error page. Instead, we get an empty/blank HTA screen as described by the OP.

    Here is a screenshot of the problem: Link to Screenshot

    Here's a relevant snippet of the bdd.log:

    <![LOG[Return code from command = 0]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Application Oracle Java Standard Edition Runtime Environment 7 Update 76 with Updates Disabled installed successfully]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications001 is now = {aea9103d-c991-4885-a660-f8c2bc0d6cca}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications002 is now = {6cbceb37-6098-423b-9bd4-62494842ccdd}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications003 is now = {e390a33b-2794-4c2a-9003-2aed299286a9}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications004 is now = {b10bac1c-2d95-4544-a76d-1fa54735404d}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications005 is now = {bef2cd98-b1fe-46fe-9c1f-c2cdaf3eb150}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications006 is now = {7acfed74-5828-4ec8-a08e-9064f4e97456}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications007 is now = {4b73f153-1f85-4209-88d5-395fca79e4ef}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications008 is now = {ea9b3d0f-78e0-4f4b-bebd-08e7208d9056}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications009 is now = {c4ae0ff0-2aec-43e7-922d-de39b0611559}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[ZTIApplications processing completed successfully.]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Language/Locale Identified (in order of precedence): 1033,0409,0x0409,9,0009,0x0009]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Mandatory Single Application install indicated. Guid: {edd8b806-460a-42be-ad52-b87f3f6bd8fa}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[################]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Entry: {edd8b806-460a-42be-ad52-b87f3f6bd8fa}]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Name:  Oracle Java Standard Edition Runtime Environment 8 Update 74 with Updates Disabled]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[################]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Validating connection to \\domainname.net\Published\IT\Images\MDT\..\..\Software\Oracle\Java_Standard_Edition_Runtime_Environment\1.8.0_74]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Mapping server share: \\domainname.net\Published]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Already connected to server domainname.net as that is where this script is running from.]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[		Change directory: \\domainname.net\Published\IT\Images\MDT\..\..\Software\Oracle\Java_Standard_Edition_Runtime_Environment\1.8.0_74]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[		Run Command: \\domainname.net\Published\IT\Images\MDT\Tools\X64\bddrun.exe C:\windows\System32\wscript.exe Install_Unattended_No_Reboot_Updates_Disabled.vbs]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[ZTI installing application ]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[About to run command: \\domainname.net\Published\IT\Images\MDT\Tools\X64\bddrun.exe C:\windows\System32\wscript.exe Install_Unattended_No_Reboot_Updates_Disabled.vbs]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Command has been started (process ID 6756)]LOG]!><time="16:14:34.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 6756)]LOG]!><time="16:14:35.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Return code from command = -102]LOG]!><time="16:16:08.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Application Oracle Java Standard Edition Runtime Environment 8 Update 74 with Updates Disabled returned an unexpected return code: -102]LOG]!><time="16:16:08.000+000" date="03-18-2016" component="ZTIApplications" context="" type="3" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications001 is now = {aea9103d-c991-4885-a660-f8c2bc0d6cca}]LOG]!><time="16:16:08.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications002 is now = {6cbceb37-6098-423b-9bd4-62494842ccdd}]LOG]!><time="16:16:08.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications003 is now = {e390a33b-2794-4c2a-9003-2aed299286a9}]LOG]!><time="16:16:08.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications004 is now = {b10bac1c-2d95-4544-a76d-1fa54735404d}]LOG]!><time="16:16:08.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications005 is now = {bef2cd98-b1fe-46fe-9c1f-c2cdaf3eb150}]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications006 is now = {7acfed74-5828-4ec8-a08e-9064f4e97456}]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications007 is now = {4b73f153-1f85-4209-88d5-395fca79e4ef}]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications008 is now = {ea9b3d0f-78e0-4f4b-bebd-08e7208d9056}]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications009 is now = {c4ae0ff0-2aec-43e7-922d-de39b0611559}]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Property InstalledApplications010 is now = {edd8b806-460a-42be-ad52-b87f3f6bd8fa}]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[ZTIApplications processing completed successfully.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unregistering TSCore.dll.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: wscript.exe "C:\MININT\Scripts\LTICleanup.wsf"]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Re-enabling UAC for built-in Administrator account]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Logs contained 10 errors and 5 warnings.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[No Windows PE image to delete.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Checking mapped network drive.]LOG]!><time="16:16:09.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Z: mapped to \\domainname.net\Published\IT\Images\MDT]LOG]!><time="16:16:10.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Disconnecting drive Z: mapped to \\domainname.net\Published\IT\Images\MDT]LOG]!><time="16:16:10.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up C:\MININT directory.]LOG]!><time="16:16:10.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="16:16:10.000+000" date="03-18-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">


    • Edited by Frank E Lesniak Friday, March 18, 2016 11:36 PM clarified Windows 10 version
    Friday, March 18, 2016 11:33 PM
  • Why the relative path?

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Saturday, March 19, 2016 12:48 AM
    Moderator
  • This is exactly what I'm getting as well. It seems to be failing when trying to install applications post-install (Office 2016 suite fails due to file not found error although path is definitely valid). If I don't install applications, it completes successfully. I'm also using an image I built today using the 1511.1 ISO I also downloaded today. Same blank screen too. 
    • Edited by Jirv311 Monday, March 21, 2016 10:03 PM Added bit about applications
    Monday, March 21, 2016 10:02 PM
  • We are still seeing this randomly. 

    It will fail sometimes and if I start the deployment over again from scratch, it may work fine on the second or third attempt.

    We also install apps and HP drivers as an app (HP SSM), but I can't tell what fails because I have never been in front of the computer when the issue happens to witness which app is failing.

    It may be a network connectivity issue that isn't handled gracefully since it's not a consistently repeatable failure.

    • Edited by MyGposts Tuesday, November 15, 2016 6:38 PM
    Tuesday, November 15, 2016 6:32 PM
  • Just to follow up, root cause seems to be loss of network connectivity during the deployment process. We found that Windows Update was loading network drivers, and the timing of the network driver swap was causing random interruptions to the deployment process.

    Fix was ensuring that the most-up-to-date NIC drivers are in the deployment share, and also temporarily disabling Windows Update by GPO or by registry during the deployment process. To do this, implement the following Group Policy setting:

    Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings\Turn off Windows Update device driver searching
    = Enabled
    (or the underlying, equivalent registry key)


    • Proposed as answer by Frank E Lesniak Tuesday, November 15, 2016 6:36 PM
    • Edited by Frank E Lesniak Tuesday, November 15, 2016 9:25 PM Clarified how to disable driver updates via Windows Update
    • Marked as answer by MyGposts Tuesday, November 15, 2016 11:57 PM
    Tuesday, November 15, 2016 6:36 PM
  • We already have WSUS set up and the WSUS updates run near the end of the OSD.

    Still doesn't explain why there is a blank white summary screen preventing us from clearly seeing the cause of the failure.


    This seems like a bug.




    • Edited by MyGposts Tuesday, November 15, 2016 6:43 PM
    Tuesday, November 15, 2016 6:41 PM
  • Agreed that this behavior is a bug. In all cases that I investigated, it was caused by a loss of network connectivity in the middle of the deployment - all other failures did not trigger the blank UI problem.

    Try the workaround that I proposed - I believe it will stop it from happening.

    Tuesday, November 15, 2016 6:43 PM
  • Even though we have WSUS set up for the Windows Updates, the system still manages to download other drivers from Microsoft during the deployment such as unwanted, conflicting Intel AMT drivers.

    At the end of the deployment, we have to manually reinstall the correct Intel AMT drivers and click through a warning that says a newer version of the driver is already installed.

    Maybe this is contributing to this issue.

    Is there something we can do to make sure these Windows 10 systems ONLY get drivers from our deployment share and not from the Internet?




    • Edited by MyGposts Tuesday, November 15, 2016 6:51 PM
    Tuesday, November 15, 2016 6:47 PM
  • MyGposts,

    Try implementing the following Group Policy setting:

    Computer Configuration\Administrative Templates\System\Internet Communication Management\Internet Communication settings\Turn off Windows Update device driver searching
    = Enabled

    See: https://technet.microsoft.com/en-us/library/cc730606(v=ws.10).aspx#BKMK_Anchor2


    Tuesday, November 15, 2016 9:21 PM
  • On the machines I've seen where the screen just prior to the Final Summary page (the HTA wizard screen) is white and seems frozen, I've wiped the drive with Diskpart, updated the BIOS and then reimaged them. After updating the BIOS, every one of my devices went past that HTA wizard screen and onto a white Summary page stating zero errors. Try updating the BIOS. For me, I created a bootable USB (MS-DOS USB) so it boots to C:\ and on it I have a BIOS for many models. Something to try.
    Saturday, November 19, 2016 9:10 PM
  • This is caused by out of date drivers being updated by Windows Update (or Dell Command Update if you install that and have it perform updates) in Windows 10.

    To fix this, add this Run Command Line command to the beginning of State Restore:

    cmd.exe /c reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching" /v SearchOrderConfig /t REG_DWORD /d 0 /f

    At the end of deployment, use this to enable driver updates from Windows Update (if you choose to enable it again):

    cmd.exe /c reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching" /v SearchOrderConfig /t REG_DWORD /d 1 /f

    This is a bug that the Microsoft MDT team really needs to resolve, among other Windows 10 bugs.

    Monday, June 11, 2018 3:44 PM