none
BcdEdit returned an error when generating an Media ISO in MDT RRS feed

  • General discussion

  • I have MDT 2013 Update 2. I installed ADK for Windows 10 1607. Afterwards, I can no longer generate a media iso from MDT for any Windows 10 build, it halts with "BcdEdit returned an error". Anyone else seen this?

    If I uninstall ADK for Windows 10 1607 and re-install ADK for Windows 10 1511, all works fine.


    • Edited by peopleman1 Wednesday, August 3, 2016 5:59 PM
    Wednesday, August 3, 2016 5:06 PM

All replies

  • Questions:  What OS are you running MDT and ADK on?  Any third-party antivirus software in use (maybe it excluded the old version)?


    Thanks,
    -Michael Niehaus
    Director of Product Marketing, Windows Deployment, Management, and Store
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com

    Wednesday, August 3, 2016 5:22 PM
  • Running all on Windows 7 64 bit. McAfee VSE/HIPS installed, but I uninstalled it (I had suspected an issue as it had known issues with Dism last year that a Mcafee patch remediated) to no avail.
    Wednesday, August 3, 2016 5:44 PM
  • I have the same problem.

    Windows 2008 R2 / MDT 2013 Update 2 / ADK for Windows 10 1607.

    I can't generate a media from MDT. I get the error "BcdEdit returned an error".

    After you read Michael Niehaus, I tried to uninstall antivirus SEP and reboot server MDT.

    I can't always generate a media from MDT.

    Sorry for my english.

    Friday, August 5, 2016 9:23 AM
  • Hi,

    I tried different OS to generate a media from MDT.

    The results are :

    1 - Windows 2008 R2 / MDT 2013 U 2 / ADK 1607 => BCDEdit error

    2 - Windows 10 1607 / MDT 2013 U 2 / ADK 1607 => OK

    3 - Windows 2008 R2 (an other) / MDT 2013 U 2 / ADK 1607 => BCDEdit error

    4 - Windows 2012 R2 / MDT 2013 U 2 / ADK 1607 => OK

    So, which OS supports ADK 1607 ?

    Tuesday, August 9, 2016 12:26 PM
  • Here are some findings, (thanks to Benjamin)

    1 - Windows 2008 R2 / MDT 2013 U 2 / ADK 1607 => Error BCDEdit
    2 - Windows 10 1607 / MDT 2013 U 2 / ADK 1607 => OK
    3 - Windows 2008 R2 (brand new) / MDT 2013 U 2 / ADK 1607 => Errorr BCDEdit
    4 - Windows 2012 R2 / MDT 2013 U 2 / ADK 1607 => OK


    signatureforums

    Tuesday, August 9, 2016 12:40 PM
  • This is not surprising.  I think Windows 8.1 and 2012 R2 or later are your valid options.  So it looks like support was dropped for older OSes with this version of the ADK.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.


    Tuesday, August 9, 2016 4:58 PM
    Moderator
  • This is not surprising.  I think Windows 8.1 and 2012 R2 or later are your valid options.  So it looks like support was dropped for older OSes with this version of the ADK.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.


    Do you have informations that we don't have ?

    Because I don't see information concerning ADK for Windows 10 1607 saying that Windows 2008 R2 and Windows 7 don't support this ADK.

    On the website Microsoft Support Lifecycle, Windows 7 and Windows 2008 R2 are supported until 2020.


    • Edited by Benjamin Ch Wednesday, August 10, 2016 7:50 AM
    Wednesday, August 10, 2016 7:34 AM
  • I have the same information as you.  However your testing was clear.   Which is why I think they dropped ADK support for old OSes.

    If you want a definitive answer the Windows 10 forums will have better information.


    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.


    Wednesday, August 10, 2016 4:49 PM
    Moderator
  • I tried to generate media for Windows 10 - 1607 with the ADK 1511.

    And the test is OK.

    I deploy my media on USB media and my computer has like OS Windows 10 - 1607.

    Thursday, August 11, 2016 10:20 AM
  • Benjamin

    Right. The new ADK is not needed to deploy Windows 10 1607. You can still use ADK 1511.

    I hope Microsoft will publish a statement in regard to deployment. ADK 1607 brings fixes for ConfigMgr and also new features on Windows 1607.

    I will suggest to use ADK 1511 for now if you generate media often.


    signatureforums

    Thursday, August 11, 2016 11:14 AM
  • This may be a moot point, but I had the same issue. I tried upgrading to Windows 10 ADK 1607 (10.1.14393.0) and to MDT 6.3.8443.1000. The MDT upgrade was fine, however I too was getting an error message "BcdEdit returned an error", when I was attempting to create standalone media. I uninstalled Windows 10 ADK 1607 (10.1.15393.0) and installed Windows 10 ADK 1511 (10.1.10586.0), and now I can create standalone media without issue.

    So you are probably right that Microsoft dropped support for Windows Server 2008 R2 in Windows 10 ADK 1607 (10.1.15393.0).

    Thursday, February 2, 2017 1:17 PM
  • Not sure if this will help, but I'm trying it right now.

    Found on another forum where someone posted links to the WAIK download (which wasn't part of the steps or software requirements needed per the documentation supplied on injecting Skylake drivers into Windows 7 ISO...) and a WAIK "Supplement for Windows 7 SP1"...

    Maybe the Supplement is now required to keep using the latest WAIK and build Win7 64-bit ISOs...

    Will update after I've tried this.

     
    Friday, June 9, 2017 4:07 PM
  • Some time has elapsed since this posting but thanks for this all the same. I encountered the same BCD Edit error after "upgrading" to MDT 2013 Update 2 and using Windows 10 ADK 1703, when developing a Win 7 Media Deployment solution. Took a bit of a trawl to find ADK 1511 to see if it worked. The following site was also a help with explaining the versions and obtaining the links:

    <http://renshollanders.nl/2016/12/download-windows-adk-the-numerous-versions-of-microsoft-windows-adk-assessment-and-planning-toolkit-and-where-to-find-them/>

    Now back up and running again with media deployments, which we use most of the time since our solutions require to be standalone.

    Thursday, September 28, 2017 10:19 AM