The fix for the refresh scenario that doesn’t work with ADK 10586 that I blogged about a while ago which has been a pain for many of us got a fix last week, https://support.microsoft.com/sv-se/kb/3143760 Really great! 😀 😀
I realized that I have many environments to create new boot images and apply the hotfix in so I wrote two simple .cmd files to create them for me, so I thought I would share them here as well. The .CMD file is a combination of the instruction for how to apply the hotfix and the great blog post by Brandon which can be found here: http://blogs.technet.com/b/brandonlinton/archive/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager.aspx
Both of the .cmd files can be downloaded here:Download
A short how to create new boot images using WinPE 10.0.15086
1. If you are using an older ADK uninstall it on the Primary Site Server.
2. Download and install the new version of the ADK
3. Reboot the Site Server
4. Download the .cmd files from the link above
5. Download the ADK hotfix from the link: https://support.microsoft.com/sv-se/kb/3143760
6. Create a folder, example D:\Temp\ADKHotfix
7. Extract the Hotfix and the .CMD files to that directory.
8. Check the two .dat files for any alternate stream according to the KB article.
9. Edit the .cmd files so that it has the correct path’s for your environment, change the path to the ADK and the Mount folder to be used by DISM.
10. Open the “Deployment and Imaging Tools Environment” command prompt
11. Execute the .cmd file for the architecture that you want to create a boot image for and you are done!
Then you go and grab a “Configuration Manager cup of coffee” as a customer once called it.. and when you return you have a new fixed Boot Image that can be imported in Configuration Manager.
Hope it is helpful!
Thanks a lot for providing the scripts, I found some errors with them however, the Schema-x86.dat file wasn’t named correctly in the script so I had to modify that.
The xcopy command would fail if there were spaces in the path so I added “” around the path
Finally, I added a DISMPATH variable and called DISM from the new ADK folder as otherwise if it was using the native DISM from Server 2012 R2, it was not able to perform the injection of the updates.
Cheers
Shaun
So, would this need to be done every time you create a boot image? That’s how I understand it but want to make sure. And the same process with MDT boot images?
Hi,
Yes every time you create a new boot image and import in Configuration Manager.
/Jörgen
Hi Jorgen,
I’m running into some issues with this. In the “dism.exe /mount-wim /wimfile:%Mountdir%\boot.wim /index:1 /mountdir:%Mountdir%\mount” step in the script it attempts to load the boot.wim, I receive a DISM Error 3 “system can’t find the path specified”.
In file explorer if I type the path to the boot.wim it find it no problem so I’m wondering what I’m doing wrong. Any ideas?
Thanks for your time.
Is it still necessary with CB 1602?
Hi,
Yes it is still necessary, the bug is in the ADK.
/Jörgen
Hello Team,
When We Extracted this KB, what will happen to .EXE file? Do we need to run .EXE file as well apart from mounting the images? what is the role of that .exe file.
Thanks
Navneet
Thanks for this, it amazes me Microsoft doesn’t just update the online version of the ADK to include this fix inside it. I only installed the ADK yesterday as I am creating a new SOE with Windows 10 1511 and ran into this issue.
For some reason, actually if you Try to got the hotfix from support page article http://support.microsoft.com/kb/3143760 you may got Sorry, the page you requested is not available I tried to got it from windows catalog, not available. Any clues?
Thank you so much.
Hi,
I have CM 1511 and ADK for Windows 10, version 1607 which is the latest ADK available. May I know if the fix is still valid in my case as I have run into “You can not import this boot image. Only finalized boot images are supported” error.
The script runs file but where are the finalized wim files?