2019-11-12: Microsoft have confirmed on Twitter that there will be no updated ADK for Windows 10 1909, so keep using ADK 1903 with the fix as noted below. 2019-10-24: At the time of writing there is no ADK for Windows 10 1909 November 2019 Update (19H2), so I’ve tested this walkthrough using the ADK for Windows 10 1903 with the hotfix for Windows System Image Manager. I’ll keep these pages up to date when Windows 10 1909 is officially released.

2019-11-12: Microsoft have confirmed on Twitter that there will be no updated ADK for Windows 10 1909, so keep using ADK 1903 with the fix as noted below. 2019-10-05: At the time of writing there is no ADK for Windows 10 1909 November 2019 Update (19H2), so I’ve tested this walkthrough using the ADK for Windows 10 1903 with the hotfix for Windows System Image Manager. I’ll keep these pages up to date when Windows 10 1909 is officially released.

2019-11-12: Microsoft have confirmed on Twitter that there will be no updated ADK for Windows 10 1909, so keep using ADK 1903 with the fix as noted below. 2019-10-05: At the time of writing there is no ADK for Windows 10 1909 November 2019 Update (19H2), so I’ve tested this walkthrough using the ADK for Windows 10 1903 with the hotfix for Windows System Image Manager. I’ll keep these pages up to date when Windows 10 1909 is officially released.

Here’s a couple of helpful tips and tricks I’ve found from Windows 10 1909/1903 and previous versions. Let’s get into them! Search and Cortana Are Separated In 1903/1909 A good change IMO and my first impressions of the new search is that it’s back to being as good as Windows 7’s. The search bar on the Taskbar is now just search and has nothing to do with Cortana. By default the search bar is expanded on the Taskbar and Cortana is just an icon.

I’ve updated my previous post on removing the built-in apps from Windows 10 to reflect the minor changes in the Windows 10 1903 May 2019 Update. You can find that post here, or under the Windows Deployment menu at the top of the page, and click on 1903 May 2019 Update (19H1). If you have any questions or comments please leave them below. Thank you. -Mike

Current Known Issue: With the Windows 10 1903 ADK on 64-bit, the Windows System Image Manager (WSIM) will fail to generate a catalogue. Microsoft has issued a fix which you can download here. The fix contains two updated files, ImageCat.exe and ImgMgr.exe which need to be copied to the location the ADK is installed. By default the location is: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM. After installation you will still not be able to access the WSIM through MDT, but launching WSIM manually and then opening the install.

Current Known Issue: With the Windows 10 1903 ADK on 64-bit, the Windows System Image Manager (WSIM) will fail to generate a catalogue. Microsoft has issued a fix which you can download here. The fix contains two updated files, ImageCat.exe and ImgMgr.exe which need to be copied to the location the ADK is installed. By default the location is: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM. After installation you will still not be able to access the WSIM through MDT, but launching WSIM manually and then opening the install.

Microsoft Deployment Toolkit has been updated to build 8456 and includes support for: Windows 10, version 1809 Windows Server 2019 Windows ADK for Windows 10, version 1809 Configuration Manager, version 1810 The full release notes are available from Microsoft here. If you have any questions or comments please leave them below. -Mike

Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. Microsoft have posted about resuming the rollout and how they test and validate updates over on the Windows blog. There’s also a good post on the Windows IT Pro blog regarding the volume license availability of the new update.

Update 2018-11-13: Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. Hi all, Given I’ve posted my usual guides on how to deploy Windows 10 1809 with MDT, I thought it important to also post that Microsoft has chosen to delay the rollout of Windows 10 1809 and Windows Server 2019 for the time being due to some users reporting that files are missing after an upgrade.

Update 2018-11-13: Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. Continuing from a previous post: Building A Windows 10 1809 (October 2018 Update) Reference Image with MDT, this post will walk through creating a Deployment Share to deploy the Windows 10 reference image. It is assumed that you have a Server or PC with Microsoft Deployment Toolkit and it’s dependencies installed and have been through the post previously mentioned.

Update 2018-11-13: Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. This post will walk through installing and configuring Microsoft Deployment Toolkit to build a reference image of Windows 10 1809 (October 2018 Update) using a Hyper-V Virtual Machine. It is assumed that you have a Server or PC ready to install MDT onto and create an file share for MDT to build the image with.

I’ve been revisiting my MDT process as I wanted to try and use Windows Update to get drivers during deployment - by itself this is not a problem, I can just remove the WSUSServer=http://wsus:8530 configuration from the CustomSettings.ini. However as the device is added to the domain, Group Policy will configure the device to use the local WSUS for updates, this is desired as I still want to use WSUS for future updates, but I want to use Windows Update during deployment.