Answered by:
Windows 10 Upgrade fails with these error codes using MDT 2013 Update 1
Question
-
Hi,
trying to figure out why an in-place upgrade keeps failing, i have a set of log files at http://1drv.ms/1ictdWd but I am trying to find out specifically what the errors mean that i get in my MININT log files
from BDD.log
File C:\MININT\Scripts\LTITriggerUpgradeFailure.wsf already exists in Target LTICopyScripts 10/09/2015 11:54:17 0 (0x0000)
Setup failed to upgrade OS from \\deployserv\MDTProduction$\Operating Systems\Windows 10 Pro x64\setup.exe, rc = -1047526904 LTIApply 10/09/2015 11:56:07 0 (0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = -1047526904 0xC1900208 LTIApply 10/09/2015 11:56:07 0 (0x0000)
from LTIApply.log
Setup failed to upgrade OS from \\deployserv\MDTProduction$\Operating Systems\Windows 10 Pro x64\setup.exe, rc = -1047526904 LTIApply 10/09/2015 11:56:07 0 (0x0000)
ZTI ERROR - Non-zero return code by LTIApply, rc = -1047526904 0xC1900208 LTIApply 10/09/2015 11:56:07 0 (0x0000)what is the return code -10247526904 actually relating to?
thanks
Steve
Answers
-
Hi,
I solved this in two ways:
1. even though my Windows 7 installation was all set to UK English, if i deployed the en-US version it seemed to upgrade, but then i had problems with activation (license voilation blue screen even though the product had activated before the reboot)
2. added WindowsUpgradeAdditionalOptions=/compat IgnoreWarning to the customsettings.ini file and used the en-GB installation. still testing this at the moment but did have a couple of issues with blank screen. I think this thread can close now because it was due to language issues.
thanks
Steve
- Marked as answer by Milkientia Monday, September 14, 2015 11:17 AM
All replies
-
Do the SKUs match? Upgrade from Pro to Pro?
Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/
-
EnterpriseEval does *NOT* support upgrades from any other product.
Property TaskSequenceTemplate is now = ClientUpgrade.xml Property OSGUID is now = {aeafd5fd-513b-4724-bd25-de20f17889f6} Property ImageIndex is now = 1 Property ImageSize is now = 13003 Property ImageFlags is now = EnterpriseEval Property ImageBuild is now = 10.0.10240.16384 Property ImageProcessor is now = x64Please download Enterprise VL from TechNet or Microsoft Volume Licensing, and use that from MDT.
Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com
- Marked as answer by Keith GarnerMVP, Moderator Thursday, September 10, 2015 11:23 PM
- Unmarked as answer by Milkientia Friday, September 11, 2015 7:30 AM
-
-
Next step is to gather up the panther logs from the failed execution.
Search all directories (even hidden ones) for the panther directory, and find the setupact.log file that contains the error, or at least contains time stamps between 9/9/15 8:34:35 and 8:36:54
IF you still need help please zip up the logs to a public site like one drive and share the link.
Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com
-
Hi,
I solved this in two ways:
1. even though my Windows 7 installation was all set to UK English, if i deployed the en-US version it seemed to upgrade, but then i had problems with activation (license voilation blue screen even though the product had activated before the reboot)
2. added WindowsUpgradeAdditionalOptions=/compat IgnoreWarning to the customsettings.ini file and used the en-GB installation. still testing this at the moment but did have a couple of issues with blank screen. I think this thread can close now because it was due to language issues.
thanks
Steve
- Marked as answer by Milkientia Monday, September 14, 2015 11:17 AM