Missing tabs on Boot image after installing ADK for Windows 10 in ConfigMgr

If you install the ADK for Windows 10 after you upgrade to ConfigMgr 2012 R2 SP1, existing boot images won’t be upgraded and as a result you will be missing a few tabs on the properties of the boot image, such as adding Drivers and Customize.

2015-08-17 13_30_20-Coretech - ctcm01.coretech.intra - [SCCM 2012 server] - Royal TS

This happens because SCCM compares the version of the installed ADK to the version of the boot image, and if these do not match the tabs to modify the boot image will be hidden. When we update the distribution points the version is not checked and image just rebuild and redistributed.

the fix

Well, if you haven’t installed the SP1 yet, you can simply make sure to uninstall the old ADK and install the new one before installing SP1. The installer will update the boot image for you.

If you have already installed SP1 luckily there is a fix:

First you need to update the boot.wim file that SCCM uses for the default boot images.

Copy the winpe.wim file from the installation folder of the ADK such as: (make sure the architecture is the same, in this case 64-bit)

 C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us”

Copy the file to your OSD folder in the installation directory of your ConfigMgr such as:

“D:\Program Files\Microsoft Configuration Manager\OSD\boot\x64”

Delete the old boot.wim and rename the winpe.wim to boot.wim

Do the same for the 32-bit image.

If you have custom boot images, replace the source media in these as well.

Now we need to refresh the image data that ConfigMgr uses to decide whether or not  to show the extra tabs on the options dialog.

Create a new PowerShell script with the following content:

1 $SiteCode = "PS1" 2 $PackageID = "PS100005" 3 $BootImage = Get-WmiObject -Namespace "root\SMS\site_$($SiteCode)" -Class SMS_BootImagePackage -Filter "PackageID = '$($PackageID)'" -ErrorAction Stop 4 $BootImage.ReloadImageProperties()

Make sure to specify the correct site code and package ID for the Boot Image to update.

Now run the script with administrative privileges.

Voilà your boot image is now updated to Windows 10 ADK, and you can add drivers and customize to you image again. 

2015-08-17 13_55_58-Coretech - ctcm01.coretech.intra - [SCCM 2012 server] - Royal TS

Remember to update your distribution points to build the image and redeploy content.


Comments (40):

  1. […] einem aktuellen Blog-Post hat Henrik Rading auf ein Problem bei der Installation des ADK für Windows 10 aufmerksam […]

  2. Richard Knight says:

    Hi,

    Thanks for a great post, worked perfectly for me.

  3. OK and what if you ran the PS script and your default/custom boot images are still not showing tabs?

    • Nickolaj Andersen says:

      Restart the SMS Executive service, or the Primary Site server for it to pick up the new ADK version.

      • Michiel says:

        Ran the PS script and restarted the SMS Executive service but I’m still missing the tabs. Anything else I need to do?

  4. pat says:

    wow… thank you for posting this I will try it out Monday.

    We had a consulting company come in and do the SP1 upgrade. it seems they didn’t install the win10 sdk prior to the upgrade so now i’m stuck with this mess. MS just pointed me to a blog that shows you how to create a windows 10 boot image and import it into config manager on a server running the 8.1 adk.

    they stopped responding to me when I inquired about having to use a command line utility to maintain the boot image for the foreseeable future.

    do the bottom instructions assume you have upgraded to the 10 sdk after upgrading to SP1 CU1, or do they work if you are still running the 8.1 sdk on the primary server?

  5. pat says:

    article for importing a boot .wim file created with the 10 sdk onto a server still running the 8.1 sdk:

    http://blogs.technet.com/b/configmgrteam/archive/2015/08/05/windows-10-adk-and-configuration-manager.aspx

  6. Henrik Rading Henrik Rading says:

    Sorry for not responding sooner, I did not get notifications of new replies due to a server malfunction that has now been fixed.
    @Pat: Yes the instructions calls for having the Windows 10 ADK installed on the primary server.

  7. Emort says:

    having this issue aswell anoying.! do i need the ADK on the server before i can get the driver tab back on the winpe10 image?`??

  8. Henrik Rading Henrik Rading says:

    Yes you need the ADK installed on the server. ConfigMgr checks the version of the wim file, and compares it to the ADK servicing tools. If they do not match, the tabs will be hidden.

  9. Emort says:

    When reading this
    https://technet.microsoft.com/en-us/library/dn387582.asp
    im stuck on “Supported Windows PE versions for boot images ****not**** customizable from the Configuration Manager console” = Windows PE 3.11 and Windows PE 10 on System Center 2012 R2 Configuration Manager SP1 …
    im i missing anything here???

  10. Henrik Rading Henrik Rading says:

    ConfigMgr can only service images that are based on the ADK that is installed on the server.
    This is the primary cause for this blog post. Existing images are based on ADK 8.1, and you perform an upgrade to ADK 10. Now you can not service your existing boot images, as they are still version 8.1. If you upgrade ADK prior to installing SP1, the installer will upgrade your boot images for you. but if you still had ADK 8.1 installed at upgrade time, they will remain as 8.1 images and can be serviced using ADK 8.1.
    To create Windows 10 based boot images, you will need to install ADK 10, and now your existing boot images are unserviceable, as there is a mismatch between the installed ADK and the bootimages.
    So by performing the steps in this post, you will update the existing bootimage source to ADK10, and have configMgr read the version of the source image to allow servicing the boot images.

    I’m not sure what you are trying to do, but hope that this explanation helps.

  11. Emort says:

    thx that is a good explanation! what if the adk 8.1 is not installed on the primary server? as in my case.

  12. John says:

    Hi,

    Thank you for this post! Helped me a lot.

    Question: I used your method so that I can access the missing tabs in my boot image. However now my old Windows 8(1) boot images are no longer showing the tabs.
    I know this is caused by the installation of ADK 10.

    How can I now use the WIndows 10 boot image and the Windows 8(1) boot image? Or can I also use the Windows 10 bootimage for deployment of Windows 8?

    Thank you.

  13. Henrik Rading Henrik Rading says:

    If you need to service your old Windows 8.1 boot images, replace the boot.wim that is used as source. then run the PS script above. this will reload the image data into ConfigMgr and the tabs will be available.
    Yes, you can use the Windows 10 boot images to deploy Windows 7, 8, 8.1 and Windwows 10, as well as the server operating systems.

  14. Hello,
    Thank you for this post.
    I did everything you suggested, but still i do not get the tab’s.
    We have 2012 r2 sp1 with adk 10. no old bootimages on the server, just new winpe 10’s. If i add an old winpe 8.1 the tab’s are available.
    I deinstalled adk, rebooten and tried again, no luck.

    Any suggestions?

    • André says:

      Did you manage to sort this out? I suffer from the same issue. Running scripts still doesn’t cause to show the missing tabs on Winpe 10 boot images.

  15. chatzki says:

    Hey, thanks a million, worked seamlessly!

  16. Peter Bajurny says:

    The one thing I’m curious about, is this the same process that the installer would do naturally? The reason I ask is because I wonder what will happen when vNext is released with a new ADK. If I use this process, will the next upgrade automatically upgrade my boot image or will I be stuck doing it manually forever?

    The timing of all the Win 10 and SP2/R2 SP1 releases really has made things tricky.

  17. Henrik Rading Henrik Rading says:

    Yes this is more or less the same process that the setup engine uses, if the ADK has been upgraded BEFORE upgrading ConfigMgr.
    If you use this process to update your boot images after upgrading your ADK, ConfigMgr is in the same state as if you had upgraded the ADK before installing ConfigMgr SP1…

  18. Monju says:

    Hi Henrick,
    I have a query re copying/importing boot image from one server to another.
    I have a completely new SCCM 2012 R2 server (with new site code) built and would like to use the boot image including custom driver from my old SCCM 2012 R2 server.
    Is there an easy means to achieve this??

    Can you please assist.

    Appreciate it.
    Monju

  19. emnavarro02 says:

    Amazing! It’s worked perfeclty! Thanks a lot for sharing!

  20. […] acordo com o blog Coretech, isso ocorre porque o SCCM compara a versão do ADK instalado com a versão da imagem de boot e, […]

  21. Hajiali says:

    I ran the above script for 32bit boot image and it worked perfectly. I can see in SCCM console OS version has been changed.
    But same thing is not working for x64 boot image, while running script i am getting error like Exception Calling “ReloadImageProperties” : Generic Failure.

    Could you please suggest where is the issue?

  22. Henrik Rading Henrik Rading says:

    All the script does is to invoke the ConfigMgr reload image properties, as if you would have hit the reload button in the console. Try to have a look in your SMS Provider log file (SMSProv.log) It might give a clue to why you are getting an error.
    Also try to restart the server as I have seen errors where the provider was failing and a reboot was the only way to solve.

  23. […] dieses Problem zu beheben hat Hendrik Rading auf seinem Blog (http://blog.coretech.dk/hra  | Link zum Artikel) einen […]

  24. DYG says:

    Hi Henrick,

    I got the same issue, the drivers tab is missing but when I installed ADK for w10 i didn’t check “Windows PE” option.
    so, why i got the issue?

    i can’t do the fix because I dont have any winmpe.wim in the install path “C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us”

    what can i do? I tried to uninstall adk with no luck…

  25. Henrik Rading Henrik Rading says:

    You need to have the WinPE part of the ADK installed to service boot images.
    Either install the old ADK (including the WindowsPE part) that was used to create your boot images, or install the new ADK with WinPE.
    The CM console checks the installed version of the ADK against the version used to create the image, but the files needed to service the image must also be present on the server.

  26. DYG says:

    ok, I will install the new one so, now with PE.
    But I use custom boot images, I think that I will lose all injected drivers if I replace it with the new ADK 10 boot.wim, isn’t it??
    Thanks for the quick reply.

  27. Robert Gowdey says:

    Worked like a champ! Thank you!!!

  28. Ian Taylor says:

    Hi Henrik,
    do you know if there is another step that needs to be carried out on servers that have had the following upgrade path?

    install SP1
    install SP1 CU1
    uninstall 8.1 ADK
    install 10 ADK
    install SP1 CU2

    our guys have tried the suggested solution and it has not worked. Any help is gratefully received :)

  29. Henrik Rading Henrik Rading says:

    You should be good to go if you follow this post after upgrading. After the upgrade sccm checks if the installed version of the ADK is the same used for the boot media. If not you will not be able to service it from within sccm console. What we do here is simply to replace the source boot.wim file with the new one from the ADK, and using powershell to help us get sccm to reload the boot media version.
    Also make sure the powershell cmdlets for sccm has been upgraded (seperate MSI)

    Some people have reported that a reboot is needed, before the script works.

  30. Nils says:

    Thanks a lot! Saved me a lot of time!

  31. Pavle says:

    I dont know how to thank You Ser! You have saved my summer.

  32. Craig says:

    Thanks for posting this, worked for me! :)

  33. Graham says:

    This is brilliant information I upgraded from 2102 SP1 to 2016 (1607)

    I had no major errors but after install I found my x64 WinPE 10 was not displaying the expected version

    On looking at the properties tab I have missing tabs on boot images properties

    I replaced the boot image files with new ones form the ADK 10, renamed to match the old file names

    When I choose to ‘update distribution points’ I got errors injecting drivers. These errors indicated which driver was a problem

    Using the powershell script you provided, I could then see the boot image properties, enabling me to deselect the offending drivers and retry

    This has enabled mt resolve my issue and replace my x64 WinPE without rolling back my whole installation to remove the problem drivers

    Please accept my sincere gratitude. I hope others are able to find this information!

  34. Robert says:

    Thank you, this worked after some tinkering

    For anyone wondering, the $PackageID is the part in the boot image which would be boot.something.SITECODExxxxxxx.wim

    It will be the sitecode+some random numbers.

    Also, when you go to change your custom boot images, replace the original boot image you made. I kept a backup of the old one called xxx.wim.old, then copied winpe.wim, then renamed it to whatever the one i backed up is called (without the .old)

    Then i ran the script. I just hope my powershell stuff works now in Win PE!!!

    Thanks a trillion!

Leave a Reply