none
[RESOLVED] MDT - error while installing RRS feed

  • Question

  • Hello everyone.

    (Please excuse my bad english.)

    I use MDT (version 6.3.8330.1000) on Windows 2012 Standard) to deploy images.

    Usually, everything works just fine.

    Now I get this error message (while installing Windows 7 on Optiplex 7050) :

    [url]http://reho.st/medium/self/b3952dc540ae4bc875e5c0b57b9b0fbf6095d256.jpg[/url]

    Does anyone know this error? Tell me if you need more informations.

    Thanks so much for your help.


    • Edited by nutopiawood Tuesday, September 5, 2017 2:32 PM
    Tuesday, September 5, 2017 10:28 AM

All replies

  • 0x8004005 is a generic error that tells you that something went wrong as task sequence attempted to restart the system during OSD.

    Could you upload your BDD.log file and I will then take a look?


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Tuesday, September 5, 2017 11:30 AM
  • Thank you Anton for your reply.

    I managed to get this file but it seems to be too long to be posted.

    Do you have any idea how I can share it?

    (Dropbox asks for an email address and textuploader.com is limited to 60 000 characters)

    Tuesday, September 5, 2017 12:09 PM
  • I think it's OK with ObeDrive :

    https://1drv.ms/u/s!AqzTdn3CEEJJbGy8ZNulrbrwZJc

    Let me know if there is any problem.

    Thank you so much for your time.

    Tuesday, September 5, 2017 12:20 PM
  • Something is definetely wonky: as soon as MDT sets the PROPERTY = STATERESTORE variable, it starts cleaning up the task sequence environment. Usually, task sequence would restart your system, go through the specialize phase, autologon and resume execution. Is the issue reproducible? 


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Tuesday, September 5, 2017 12:53 PM
  • Thanks Anton.

    I finally resolved the problem.

    It was an option in BIOS, I had to deactivate UEFI...

    • Proposed as answer by tonibert Tuesday, September 5, 2017 2:51 PM
    Tuesday, September 5, 2017 2:32 PM