none
Windows 10 1607 Upgrade Task Fails in MDT 2013 Update 2 RRS feed

  • Question

  • Hi,

    I've followed this guide to create an upgrade task to use on our Windows 7 machines, but when I try to run it it's failing at installing the OS. The error I receive is:

    Setup failed to upgrade OS from  \\DEPLOY\MDTProduction$\Operating Systems\Windows 10 Pro x64 Upgrade\setup.exe, rc = -2147023582	LTIApply	22/03/2017 11:32:13	0 (0x0000)
    Event 41022 sent: Setup failed to upgrade OS from  \\DEPLOY\DEPLOYSHARE$\Operating Systems\Windows 10 Pro x64 Upgrade\setup.exe, rc = -2147023582	LTIApply	22/03/2017 11:32:13	0 (0x0000)
    ZTI ERROR - Non-zero return code by LTIApply, rc = 1	LTIApply	22/03/2017 11:32:13	0 (0x0000)
    Event 41002 sent: ZTI ERROR - Non-zero return code by LTIApply, rc = 1	LTIApply	22/03/2017 11:32:14	0 (0x0000)
    Command completed, return code = -2147467259	LiteTouch	22/03/2017 11:32:14	0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	22/03/2017 11:32:14	0 (0x0000)
    Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	22/03/2017 11:32:14	0 (0x0000)
    

    This should be a straight upgrade from Windows 7 Pro SP1 to Windows 10 Pro. 

    Does anyone have any steps for a hint here? Happy to provide more log info.


    Wednesday, March 22, 2017 11:53 AM

All replies

  • What ADK are you using?  If you are not using the Windows 10 1607 ADK, that may be the problem.

    Wednesday, March 22, 2017 1:07 PM
  • I'm using Version 10.1.14393.0 which I believe is the Windows 10 1607 version, so it's not that. I've also had no issue doing clean 1607 installs with this MDT/ADK setup.
    Wednesday, March 22, 2017 1:13 PM
  • Ok - so it looks like the upgrade runs if I perform it on a computer that is not on the domain but fails on a computer which is. Why would this be?
    Wednesday, March 22, 2017 2:33 PM
  • It might due to your group policy configuration, possibly blocking setup from running.

    Have you tried running setup manually to see what happens on a domain joined machine?


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Wednesday, March 22, 2017 6:43 PM
  • Have tried now and setup runs as normal, no errors. Still no wiser as to why MDT would fail however..
    Thursday, March 23, 2017 9:38 AM
  • Does the account you manually run setup from successfully and the account MDT is using to run setup have the same permissions and privileges?
    Thursday, March 23, 2017 3:22 PM
  • Yes, I used the same account for both for testing purposes.
    Friday, March 24, 2017 9:09 AM
  • error -2147023582 translates to -0x80070522 in hex:

    Using the trusty err.exe tool:

    C:\WINDOWS\system32>err 0x80070522
    # as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x522
    # for hex 0x522 / decimal 1314 :
      ERROR_PRIVILEGE_NOT_HELD                                      winerror.h
    # A required privilege is not held by the client.
    # 1 matches found for "0x80070522"

    Please cross verify that the account running MDT has the correct local administrative privileges.

    net user localgroup administrator

    IF you are still having problems, please copy your bdd.log file to a public share like onedrive and share the link here.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, March 24, 2017 9:26 PM
    Moderator