MDT 2012 'Failed to save Environment to (80070057) Error during Windows 7 x64 Pro Deployment RRS feed

  • Question

  • Hi There,

    I've been using MDT for a little while now, but I'm having problems successfully deploying an image to a batch of new laptops. The laptop HDD's are completely blank, and I am PXE booting using an x64 Litetouch Image via WDS. I have successfully captured my image from a reference laptop (the same model that I'm trying to image), and I am now trying to deploy it using a standard client task sequence.

    The 'Install operating System' phase seems to go ok, but then sits for quite some time at the 'Applying Unattend.xml' stage, then eventually, I get a general error 'Task Sequence Failed - 80004005'. I then exit MDT (it doesn't reboot as it should), and let the laptop boot, which it does, and logs straight on into Windows, but gives me error along the lines of 'can't find the litetouch script', which I assume means MDT hasn't been able to copy it across. The laptop is however joined to our domain, and I pretty much just have to tick the 'require a password to log on to this computer' box in user accounts, and all looks ok.

    So in summary, the image is applying, but the laptop is not rebooting and running the final cleanup scripts.

    I have already changed the SATA mode to IDE, instead of AHCI, having read this sometimes causes problems. I also read that systems with UEFI BIOS can also cause problems with MDT, but I'm not sure if this is the case.

    I have edited my customsettings.ini, to copy log files back to my server, which it has done for me. Having looked at the logs (with CM Trace), I can see these errors:

    Failed to save environment to  (80070057) TSManager 26/03/2014 15:48:09 1820 (0x071C)
    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 26/03/2014 15:48:09 1820 (0x071C)
    Failed to persist execution state. Error 0x(80070057) TSManager 26/03/2014 15:48:09 1820 (0x071C)
    Failed to save execution state and environment to local hard disk TSManager 26/03/2014 15:48:09 1820 (0x071C)
    The task sequence execution engine can not reboot the machine because we failed to persist execution environment TSManager 26/03/2014 15:48:09 1820 (0x071C)
    Fatal error is returned in check for reboot request of the action (Restart computer). 
    Unspecified error (Error: 80004005; Source: Windows) TSManager 26/03/2014 15:48:09 1820 (0x071C)
    An error (0x80004005) is encountered in execution of the task sequence TSManager 26/03/2014 15:48:09 1820 (0x071C)
    Task Sequence Engine failed! Code: 80004005 TSManager 26/03/2014 15:48:09 1820 (0x071C)

    Any help you can give me would be great, as I'd like to get this process running properly.



    Wednesday, March 26, 2014 3:33 PM

All replies

  • You don't mention what kind of OS this is (Windows 7 Pro x64?)

    This is a known issue/FAQ.

    I would recommending using MDT 2012 (update 1) for UEFI machines.

    Machines with uEFI 2.3.1 only support Windows 8.x.

    Recomendation: Convert the BIOS to CSM and/or upgrade to Windows 8.1 :^)

    Keith Garner -

    Wednesday, March 26, 2014 11:40 PM
  • Hi,

    Sorry I didn't mention the fact it was x64 Windows 7 - that makes sense, but I have a couple of questions: -

    - When i install MDT 2012 update 1, will i be able to just use all my existing boot & OS images?

    - Is there anything else I'll need to bear in mind?

    I can't just install 8.1, as we are a school environment, already partially migrated to Win 7. Our hardware isn't '8.1 ready'.

    Many thanks for you help,


    Thursday, March 27, 2014 9:52 AM
  • Sorry - I actually checked, and I am running MDT 2012 Update 1 - I must have updated it previously.

    I still have exactly the same problem - please can you advise? 



    Friday, March 28, 2014 12:35 PM
  • Can you run the machine in question in CSM mode?

    Keith Garner -

    Friday, March 28, 2014 4:18 PM
  • CSM mode is already enabled, and secure boot is disabled...
    Monday, March 31, 2014 2:52 PM
  • Did you verify CSM mode? Once you boot up to WinPE, check the BDD.log file and look for 'isUEFI' it should be "no/false" if "true/yes" then you booted up the machine using the uEFI firmware, and MDT will lay down the uEFI partitioning scheme which may be the root cause problem. Typically uEFI BIOS'es have a way to boot from *either* BIOS or uEFI.

    Keith Garner -

    Monday, March 31, 2014 4:44 PM
  • We also have this same problem. Our difference is this error is occurring at the beginning of the Tasksequence.

    Because of this BDD.log is not available yet.

    Any suggestions?


    Thursday, April 24, 2014 4:22 PM
  • The BDD.log is always available.

    Did you check my blog post above? Did it answer your question?
    Are you using a supported environment? If not please detail all components.

    Keith Garner -

    Thursday, April 24, 2014 4:25 PM