none
SCCM 2012 sp1 - can't add boot image - Only finalized boot images are supported.

    Question

  • so when i updated to sp1 i had to install the new assessment and deployment kit which i have done.

    when i try to add a boot image to sccm now i get the error:

    You can not import this boot image. Only finalized boot images are supported. For more information press F1.

    i have searched technet and on old versions of sccm you could re-install waik to fix this issue, i have tried re-installing ADK and its still doing the same.

    has anyone had this problem on 2012 sp1?



    • Edited by DennisMarinos Thursday, December 06, 2012 12:26 AM
    • Moved by Niall C. BradyMVP, Moderator Friday, December 14, 2012 7:02 PM wrong forum (From:Configuration Manager 2007 Operating System Deployment)
    Thursday, December 06, 2012 12:20 AM

Answers

  • Hi Guys,

    I had the same issue about the image could not be finalized. I have solved the problem by going into WADK 8 command prompt (as it is pre-req for SCCM 2012 SP1) and run copype amd64 c:\winpe_amd64. From boot\sources directory I have copied boot.wim to "Configuration Manager Installation directory\osd\amd64" folder. After that  I was able to import images without any issues. BTW, we are not using Mcaffee. The cause of the problem was that installation of SCCM 2012 SP1 did not updated default boot.wim in SCCM 2012 OSD folder. They were still based on Windows 7 SCCM 2012 default boot images.

    I hope I could help somebody out there.

    • Marked as answer by DennisMarinos Monday, January 14, 2013 6:28 AM
    Sunday, January 13, 2013 7:28 AM

All replies

  • Where are you getting the boot image you are trying to import from?

    Jason | http://blog.configmgrftw.com

    • Marked as answer by Yog Li Friday, December 14, 2012 6:44 AM
    • Unmarked as answer by DennisMarinos Tuesday, January 08, 2013 11:06 PM
    • Marked as answer by DennisMarinos Tuesday, January 08, 2013 11:06 PM
    • Unmarked as answer by DennisMarinos Tuesday, January 08, 2013 11:06 PM
    Thursday, December 06, 2012 1:58 AM
  • Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks,


    Yog Li
    TechNet Community Support

    Friday, December 14, 2012 6:43 AM
  • Actually  Thread NOT resolved - same thing this way - trying to import the Winpe from the windows 8 newly installed folder - assessment and deployment kit - as my SP1 install doesnt have any boot media available
    Friday, January 04, 2013 5:10 PM
  • Hi all,

    does anyone solved this issue with the boot Image? Is the only solution re-installing ADK? If yes, can someone provide the required steps/ link or tips which I need to know?

    Many thanks in advance!

    Michael

    Tuesday, January 08, 2013 9:44 AM
  • Make a new question if you still have this problem, nobody will pay any further attention to an already "answered" question. But please revisit the question if somebody needs more details, not like the OP here who just disappeared.
    Tuesday, January 08, 2013 12:36 PM
  • No This question is not answered.

    The boot image is coming from multipul sources, i have tried a custom one i created which works in WDS fine, also tried boot.wim from various Windows install Media.

    Tuesday, January 08, 2013 11:09 PM
  • I reinstalled ADK and it is still happening to me anyway.
    Tuesday, January 08, 2013 11:12 PM
  • how is: "Where are you getting the boot image you are trying to import from?" and answer to my question, its another question not an answer.

    Because its been over a month and you never answered the question posed back to you. Very hard to help you if you don't answer questions requesting further and more detailed information.

    Boot images (boot.wim) from the Windows media are not supported for use as boot images in ConfigMgr.

    In ConfigMgr 2012 SP 1, the boot images must be Win PE 4.0 based. Thus, working in WDS is meaningless. You should use the default boot images (why aren't you) or create new Win PE boot images from the ADK.


    Jason | http://blog.configmgrftw.com

    Tuesday, January 08, 2013 11:19 PM
  • What do you mean by win pe 4.0 based, is this based on windows 8?

    What default boot images are you refering to the ones built in to SCCM 2012 sp1?

    I have tried these SCCM default boot images and they do not work for me.

    Some setup guides or etc would be great if anyone has a link to them? I'm trying to image some thin clients via SCCM's PXE boot functionality to run a task sequence to install the image i have captured on to the the devices but can not get it to work.  

    Thursday, January 10, 2013 3:39 AM
  • Yes, PE 4.0 is based on Win 8. Don't draw a bad conclusion from this though as all down-level OSes (except Win 2000 which isn't supported at all anymore) can still be deployed.

    Yes, the built-in boot images are the default ones.

    What do you mean by "do not work"?


    Jason | http://blog.configmgrftw.com

    Thursday, January 10, 2013 3:45 AM
  • My colleague is having the same problem.

    ADK

    Clean windows 2008R2 install with SCCM 2012 SP1(integrated)

    SQL is 2012

    Thursday, January 10, 2013 3:43 PM
  • Please add details. "Having the same problem" does not help especially not in this case, because the thread started with a failed upgrade to SP1 and you installed CM12 SP1 from scratch.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, January 10, 2013 3:48 PM
  • Well, I have the same issue.

    Installed a new Windows Server 2012, with SQL Server 2012 and System Center Configuration Manager 2012 SP1.

    The old SCCM 2012, hade 2 perfectly updated boot images (with all NIC drivers that we need on them). So I try to import them to the new fresh insall of SCCM 2012 SP1, but also I gets the error message "You can not import this boot image. Only finalized boot images are supported. For more information press F1." (well pressing F1 dosent help, no information there that can help me in this case).
    So I tryed to copy and import the boot image that already is installed in SCCM 2012 SP1, but get the exact same error message.

    I have tryed to update the boot image in SCCM 2012 SP1 with drivers, and has put it on the DP, veryfied that it was succesfully distrubated to the DP.
    After that I created my boot-usb (yes, no pxe-boot here) and started the computer on it, choosed my task for installation, put in the new computername (using collection variables for all unknown computers) and hit enter, volia, error message saying that my boot image is'nt present on the DP... :/

    Sorry for my poor spelling, but I hope you understand, and have some ideas for me to try out!

    regards

    MB

    Thursday, January 10, 2013 4:16 PM
  • I had the same problem.

    Fresh install SCCM 2012SP1, No Boot Images.

    Afterwardd I could not import any boot image in the SCCM2012 console.

    After disabling McAfee Access Protection.

    I could import boot images again.

    McAfee is blocking the creation of the boot image package.

    Friday, January 11, 2013 9:54 AM
  • I had the same problem.

    Fresh install SCCM 2012SP1, No Boot Images.

    Afterwardd I could not import any boot image in the SCCM2012 console.

    After disabling McAfee Access Protection.

    I could import boot images again.

    McAfee is blocking the creation of the boot image package.

    Friday, January 11, 2013 9:55 AM
  • I've tried using the new WinPE 4 images, but they are based on Windows 8 and require PAE to startup properly.  I have older laptops and computers that I need to deploy Windows XP to, but they can't boot these new PE images.  I tried using older images from WAIK that are Vista and Win7 based, but those won't properly update and deploy. I get the following error:

    ErrorCode = 2152205056;
    File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
    Line = 4566;
    ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    Operation = "ExecMethod";
    ParameterInfo = "SMS_BootImagePackage.PackageID=\"DA20000E\"";
    ProviderName = "WinMgmt";
    StatusCode = 2147749889;

    So...any idea how I can get around this other than throw away all my old systems?  Don't get me wrong, I'd love to, but I can't as we're a small school district in California and have zero funding.

    Saturday, January 12, 2013 5:14 AM
  • Hi Guys,

    I had the same issue about the image could not be finalized. I have solved the problem by going into WADK 8 command prompt (as it is pre-req for SCCM 2012 SP1) and run copype amd64 c:\winpe_amd64. From boot\sources directory I have copied boot.wim to "Configuration Manager Installation directory\osd\amd64" folder. After that  I was able to import images without any issues. BTW, we are not using Mcaffee. The cause of the problem was that installation of SCCM 2012 SP1 did not updated default boot.wim in SCCM 2012 OSD folder. They were still based on Windows 7 SCCM 2012 default boot images.

    I hope I could help somebody out there.

    • Marked as answer by DennisMarinos Monday, January 14, 2013 6:28 AM
    Sunday, January 13, 2013 7:28 AM
  • Hi Sabioncello,

    This sound intresting, but I'm failing with the WADK, can you please tell me all the steps?

    regards

    MB

    Sunday, January 13, 2013 10:03 AM
  • I've tried using the new WinPE 4 images, but they are based on Windows 8 and require PAE to startup properly.

    Not sure where you getting that from but it is not accurate. WinPE 4.0 *will* boot your older systems fine.

    As for using your older WinPE 3.0 images, it simply won't work so of course you are getting odd errors.


    Jason | http://blog.configmgrftw.com

    Sunday, January 13, 2013 11:36 PM
  • Hi Guys,

    I had the same issue about the image could not be finalized. I have solved the problem by going into WADK 8 command prompt (as it is pre-req for SCCM 2012 SP1) and run copype amd64 c:\winpe_amd64. From boot\sources directory I have copied boot.wim to "Configuration Manager Installation directory\osd\amd64" folder. After that  I was able to import images without any issues. BTW, we are not using Mcaffee. The cause of the problem was that installation of SCCM 2012 SP1 did not updated default boot.wim in SCCM 2012 OSD folder. They were still based on Windows 7 SCCM 2012 default boot images.

    I hope I could help somebody out there.

    Thanks this was the answer to my trouble, was able to add boot.wim's ok. need to test if i can image some Thin Clients running windows embedded standard 7 now....

    Thanks again.

    Monday, January 14, 2013 6:29 AM
  • THANK YOU  Thierry!

    Our McAfee has an iron grip on our systems.

    Once I called security and got it disabled, Voi-flippin'-la!

    My new WINPE 4.0, SCCM 2012 SP1 ADK boot wims are finalized and distributed.

    Friday, February 15, 2013 5:34 PM
  • I've tried using the new WinPE 4 images, but they are based on Windows 8 and require PAE to startup properly.

    Not sure where you getting that from but it is not accurate. WinPE 4.0 *will* boot your older systems fine.

    As for using your older WinPE 3.0 images, it simply won't work so of course you are getting odd errors.


    Jason | http://blog.configmgrftw.com

    Jason,

    I am seeing the same issue trying to migrate machines running Pentium 4 CPU's (yes they are way old but that is why they are being replaced :) ) WinPE 4.0 will not boot a P4 machine. They have fallen off the compatibility list for windows 8 (hence the winpe won't boot it)

    Friday, February 22, 2013 11:06 PM
  • Yes, you are correct -- my statement above is inaccurate. WinPE 4 has the same hardware requirements as Win8 which means many older systems simply won't boot. It has nothing to do with PAE though. There's a longer, better discussion of this at http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/8faa337b-a648-49b4-8431-49c022b96e04

    At this time, there is no supported work-around although Microsoft is aware of the issue and will hopefully have a response soon.


    Jason | http://blog.configmgrftw.com

    Sunday, February 24, 2013 10:08 PM
  • how is: "Where are you getting the boot image you are trying to import from?" and answer to my question, its another question not an answer.

    Because its been over a month and you never answered the question posed back to you. Very hard to help you if you don't answer questions requesting further and more detailed information.

    Boot images (boot.wim) from the Windows media are not supported for use as boot images in ConfigMgr.

    In ConfigMgr 2012 SP 1, the boot images must be Win PE 4.0 based. Thus, working in WDS is meaningless. You should use the default boot images (why aren't you) or create new Win PE boot images from the ADK.


    Jason | http://blog.configmgrftw.com


    Thanks man, I lose allot of time trying to import a windows 7 image :).
    Wednesday, February 19, 2014 5:41 PM
  • Hi,

    It works to import x86 image of windows 8 and now I have some problems when I try to import x64 boot image of 8.1.

    Where I can see errors in logs. Are sow many log files and I'm little confuse and I cant find error to see what is the reason of this error.

    And the error is:

    Error: Data Source Information
    Source location: \\xxx\yyy\X17-24269\sources\boot.wim
    Boot Image: 1 - Microsoft Windows PE (x64)

     
    Error: Package Information
    Name: boot

     
    Error: Errors
    You can not import this boot image. Only finalized boot images are supported. For more information press F1.

    Thursday, February 20, 2014 10:50 AM
  • I take another dvd with 8 X64 and it works, don't works with 8.1 X64.
    Thursday, February 20, 2014 3:04 PM
  • I recently had same issue with ADK 8.1 and SCCM 2012 R2. My problem was the same one Thierry highlighted with Access Protection in McAfee VCE 8.8 Patch 2 causing various issues including:

    Cannot add packages to boot images with DISM (access denied error 5)
    Default boot images are not added to SCCM 2012
    Cannot import new boot images into SCCM 2012 (only finalized boot images are supported error).

    Here is a KB from McAfee regarding the DISM issue:

    https://kc.mcafee.com/corporate/index?page=content&id=KB76867

    Saturday, June 21, 2014 11:39 AM
  • After disabling McAfee Access Protection - I've finally imported boot images in ConfigMgr 2012. Thanks a lot.
    Monday, January 12, 2015 3:20 PM
  • this was the cause of my failures as well. Disabled MAP and it worked fine. 
    Friday, April 03, 2015 3:52 PM