Hi,

I followed this article in order to create TS to upgrade OS to Windows 10 with MDT:

https://technet.microsoft.com/en-us/library/mt426643(v=vs.85).aspx

Environment:

OS: Windows 8.1

PC: VM (Hyper-V)

However, when I run Litetouch.vbs deployment starts (Running action: Upgrade Windows) but after few minutes also stops without any error. In logs I can see this:

<![LOG[Upgrading from \\MDT-TEST\Windows10Upgrade$\Operating Systems\W10EX64RTM\setup.exe using command: "\\MDT-TEST\Windows10Upgrade$\Operating Systems\W10EX64RTM\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /DynamicUpdate Disable /ImageIndex 1]LOG]!><time="14:13:51.000+000" date="08-24-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\MDT-TEST\Windows10Upgrade$\Operating Systems\W10EX64RTM\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /DynamicUpdate Disable /ImageIndex 1]LOG]!><time="14:13:51.000+000" date="08-24-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 5680)]LOG]!><time="14:13:51.000+000" date="08-24-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 5680)]LOG]!><time="14:13:52.000+000" date="08-24-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = -1047526904]LOG]!><time="14:15:58.000+000" date="08-24-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Setup failed to upgrade OS from  \\MDT-TEST\Windows10Upgrade$\Operating Systems\W10EX64RTM\setup.exe, rc = -1047526904]LOG]!><time="14:15:58.000+000" date="08-24-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Requesting reboot for setup.exe to complete Upgrade action]LOG]!><time="14:15:58.000+000" date="08-24-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="14:15:58.000+000" date="08-24-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI ERROR - Non-zero return code by LTIApply, rc = -1047526904  0xC1900208]LOG]!><time="14:15:58.000+000" date="08-24-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="14:15:59.000+000" date="08-24-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

I manually ran Windows 10 setup.exe from Operating System folder in Deployment Share and OS was installed properly. 

Kind Regards,

Hi,

I have done the exact same thing as you reading from the exact same source article and i have this same problem, did you ever find any answer to this? I have done quite a lot with MDT before and i never got stuck this bad, it's such a simple upgrade task sequence!

thanks

Steve

Can you post the logs?  Probably panther and bdd

Hello,

right i think this should work, don't use one drive much. http://1drv.ms/1ictdWd

the logs will reference the enterprise evaluation but i have only tried that this morning to see if it was an issue with the image, i was previously trying the professional edition and that didnt work either.

many thanks

Steve

I might possibly have found a clue as to perhaps why this is stalling.

the TS seems to pass a list of parameters to the setup.exe such as /auto upgrade /quiet /noreboot etc...

well i just ran this command from the client so i could see what was going on

"\\deployserv\windows10$\Operating Systems\Windows 10 Pro x64\setup.exe" /auto upgrade /dynamicupdate disable /imageindex 1

and it gets stuck on the screen "what needs your attention" simply stating that continuing with the installation of windows will change your display language, to change it back you'll need to reinstall the language pack. then there is an OK button.... is there any way to silently skip past this dialog box? maybe this why its getting stuck....

Steve

• Proposed as answer by Ty GlanderMicrosoft community contributor Wednesday, September 09, 2015 7:42 PM
• Unproposed as answer by Ty GlanderMicrosoft community contributor 13 hours 6 minutes ago

There is the expectation of same language to same language.  This is an unintended behavior though. Can you file a Connect bug?

I dont even know why that message appears though because my Windows 7 Pro is configured with UK settings and all display and keyboard and language settings are all UK, even added to new accounts and welcome screen and the system locale, i'm upgrading to the Windows 10 UK English version.

did you get a chance to look at the log files?? what errors did they indicate?

thanks

Steve

There should be a command line parameter that handles that. I don't know what it is though. 

As far as information gathered from the logs...  I am unable to determine anything useful (I haven't found any information on the specific Windows 10 error code).

The commandline parameter:

WindowsUpgradeAdditionalOptions=/compat IgnoreWarning

Hi,

thanks for the command line, so i pass that whole line against the setup.exe? so...

setup.exe WindowsUpgradeAdditionalOptions=/compat IgnoreWarning (and whatever other params i want)?

assuming this is correct (i havent tested it yet) how can i get MDT to handle this, which script is the one responsible for doing the actual upgrade bit - I assume the command line would be shown in that script for me to edit? it would also be useful to determine this so i can force a machine to auto-reboot since i will kick this process off at the end of the day, its default is not to restart. i dont want users coming in the next morning then face at least an hours upgrade process until they can start working.

Steve

• Edited by Steve Mills 2 minutes ago