Using Windows 10 volume licensing media to upgrade to 1709 using MDT

%3CLINGO-SUB%20id%3D%22lingo-sub-123190%22%20slang%3D%22en-US%22%3EUsing%20Windows%2010%20volume%20licensing%20media%20to%20upgrade%20to%201709%20using%20MDT%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123190%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20using%20the%20Windows%2010%20volume%20licensing%20ISO%20(SW_DVD5_Win_Pro_Ent_Edu_N_10_1709_64BIT_English_MLF_X21-50143)%20which%20now%20bundles%20Windows%2010%20Enterprise%2C%20and%20Windows%2010%20Education%2C%20and%20Windows%2010%20Pro%20together.%3CBR%20%2F%3EI%20am%20trying%20to%20perform%20a%20%E2%80%9CStandard%20Client%20Upgrade%20Task%20Sequence%E2%80%9D%20using%20MDT%206.3.8443.1000%20and%20WADK%2010.1.16299.15.%3C%2FP%3E%3CP%3EI%20have%20selected%20the%20%E2%80%9CWindows%2010%20Enterprise%E2%80%9D%20OS%20in%20the%20%E2%80%9CNew%20Task%20Sequence%20Wizard%E2%80%9D%20but%20I%20am%20getting%20the%20error%20%E2%80%9CSetup%20failed%20to%20upgrade%20OS%20from%20Windows10v1709%5Csetup.exe%2C%20rc%20%3D%20-1047526912%E2%80%B3%20followed%20by%20%E2%80%9CZTI%20ERROR%20%E2%80%93%20Non-zero%20return%20code%20by%20LTIApply%2C%20rc%20%3D%201%E2%80%9D%2C%20and%20then%20%E2%80%9CLitetouch%20deployment%20failed%2C%20Return%20Code%20%3D%20-2147467259%200x80004005%E2%80%9D.%3C%2FP%3E%3CP%3EI%20assume%20this%20is%20because%20the%20ISO%20now%20contains%20multiple%20images%20but%20do%20not%20see%20a%20way%20to%20select%20the%20Image%20Index%20in%20the%20%E2%80%9CUpgrade%20Windows%E2%80%9D%20Task%20Sequence.%3C%2FP%3E%3CP%3EThe%20%E2%80%9CUpgrade%20Windows%E2%80%9D%20Task%20Sequence%20displays%20the%20correct%20version%20we%20want%20ti%20install%2C%20%E2%80%9CWindows%2010%20v1709%20Enterprise%20install.wim%E2%80%9D.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138337%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Windows%2010%20volume%20licensing%20media%20to%20upgrade%20to%201709%20using%20MDT%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138337%22%20slang%3D%22en-US%22%3E%3CP%3EIndexes%20are%20automatically%20handled%20when%20you%20pick%20an%20OS%20during%20creation%20of%20the%20task%20sequence%2C%20but%20you%20need%20an%20update%20to%20MDT%20for%20the%20Windows%2010%20v1709%26nbsp%3Bupgrade%20task%20sequence%20to%20work%20correctly.%20Should%20arrive%20any%20day%20now.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20a%20temporary%20workaround%20you%20can%20implement%20this%20post%20from%20Keith%3A%20%3CA%20href%3D%22https%3A%2F%2Fkeithga.wordpress.com%2F2017%2F11%2F15%2Fwindows-1709-in-place-upgrade-bug%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fkeithga.wordpress.com%2F2017%2F11%2F15%2Fwindows-1709-in-place-upgrade-bug%3C%2FA%3E%2F%20-%20It%20works%20as%20you%20don't%20add%20a%20reboot%20in%20the%20TS%20after%20the%20upgrade%20(Fixed%20in%20the%20upcoming%20release).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136343%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Windows%2010%20volume%20licensing%20media%20to%20upgrade%20to%201709%20using%20MDT%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136343%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20tested%20on%206.2.8330.1000%20(Microsoft%20Deployment%20Toolkit%202013%20Update%202)%26nbsp%3Band%20dont%20get%20any%20errors.%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWaDK%20Version%2010.1.10586%20with%20no%20errors.%26nbsp%3B%20Testing%20on%20MDT%206.3.8443.1000%20and%20ADK%2010.1.16299.15.and%20get%20FAILURE%20(%205610%26nbsp%3B)%20false%20verify%20.....**bleep**%20forgot%20to%20update%20the%20deployment%20share.%26nbsp%3B%20Updating%20the%20deploymnet%20share%20and%20will%20test%20again.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20confirm%20if%20this%20is%20only%20happening%20on%20upgrades%20or%20is%20also%20happening%20on%20fresh%20installs.%26nbsp%3B%26nbsp%3B%20Also%20can%20you%20post%20how%20much%20free%20disk%20space%20you%20have%20(on%20the%20windows%2010%20client).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-127198%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Windows%2010%20volume%20licensing%20media%20to%20upgrade%20to%201709%20using%20MDT%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-127198%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Scott%2C%20I'm%20encountering%20the%20same%20issue%20and%20have%20the%20same%20version%20of%20MDT%20and%20ADK.%26nbsp%3B%20Did%20you%20manage%20to%20resolve%20this%3F%26nbsp%3B%20If%20you%20did%2C%20I'd%20really%20be%20pleased%20to%20know%20as%20it%20is%20very%20frustrating.%26nbsp%3B%20Thanks%20Paul.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

I am using the Windows 10 volume licensing ISO (SW_DVD5_Win_Pro_Ent_Edu_N_10_1709_64BIT_English_MLF_X21-50143) which now bundles Windows 10 Enterprise, and Windows 10 Education, and Windows 10 Pro together.
I am trying to perform a “Standard Client Upgrade Task Sequence” using MDT 6.3.8443.1000 and WADK 10.1.16299.15.

I have selected the “Windows 10 Enterprise” OS in the “New Task Sequence Wizard” but I am getting the error “Setup failed to upgrade OS from Windows10v1709\setup.exe, rc = -1047526912″ followed by “ZTI ERROR – Non-zero return code by LTIApply, rc = 1”, and then “Litetouch deployment failed, Return Code = -2147467259 0x80004005”.

I assume this is because the ISO now contains multiple images but do not see a way to select the Image Index in the “Upgrade Windows” Task Sequence.

The “Upgrade Windows” Task Sequence displays the correct version we want ti install, “Windows 10 v1709 Enterprise install.wim”.

3 Replies

Hi Scott, I'm encountering the same issue and have the same version of MDT and ADK.  Did you manage to resolve this?  If you did, I'd really be pleased to know as it is very frustrating.  Thanks Paul. 

I have tested on 6.2.8330.1000 (Microsoft Deployment Toolkit 2013 Update 2) and dont get any errors.    

WaDK Version 10.1.10586 with no errors.  Testing on MDT 6.3.8443.1000 and ADK 10.1.16299.15.and get FAILURE ( 5610 ) false verify .....**bleep** forgot to update the deployment share.  Updating the deploymnet share and will test again.

 

Can you confirm if this is only happening on upgrades or is also happening on fresh installs.   Also can you post how much free disk space you have (on the windows 10 client).

 

Indexes are automatically handled when you pick an OS during creation of the task sequence, but you need an update to MDT for the Windows 10 v1709 upgrade task sequence to work correctly. Should arrive any day now. 

 

As a temporary workaround you can implement this post from Keith: https://keithga.wordpress.com/2017/11/15/windows-1709-in-place-upgrade-bug/ - It works as you don't add a reboot in the TS after the upgrade (Fixed in the upcoming release).