Windows ICD 1703 no longer supports image customisation

One of the tools in the Windows 10 Assessment and Deployment Kit (ADK) is the Windows Imaging and Configuration Designer (Windows ICD).

Up to now, this has allowed users to customise a Windows image (.WIM) file by adding applications or settings, and also producing a USB installer which can clean-install that whole version of Windows 10 on a new device. It could also produce Full Flash Update (FFU) image format images (although I never got that to work, but I didn't try this with version 1607).

But it seems this functionality is being removed with Windows 1703 and the associated ADK. From:
https://msdn.microsoft.com/library/w...dware/dn898375

Important

In Windows 10, version 1703, the Windows Provisioning Framework and the Windows Imaging and Configuration Designer(WICD) no longer support design time customizations or generating customized images. In Windows 10, version 1703, only runtime settings are available in WPF, and only provisioning packages are generated by the renamed Windows Configuration Designer. This means that Windows Configuration Designer is now a provisioning-only tool that supports ITPros and system administrators. For that reason, we have updated and moved the appropriate topics to TechNet. Please see Provisioning packages for Windows 10.

If you are customizing Windows 10 desktop devices, you will use Unattend and Windows System Image Manager, along with specialized layout files for Start, Taskbar, and OOBE. For more information see Customizations for Windows 10 desktop devices. In addition, there is a small subset of settings that remain in answer files; those are described in the Configure power settings section.

I'm not sure what this part means for Provisioning Packages generated in previous versions or using Scanstate?

In Windows 10, version 1703, only runtime settings are available in WPF, and only provisioning packages are generated by the renamed Windows Configuration Designer.

I would not have upgraded to Windows 10 1703 if I knew I was going to loose the ability to work with wim files. Does anyone have a workaround or another solution?

joeyCoyle said:

I would not have upgraded to Windows 10 1703 if I knew I was going to loose the ability to work with wim files. Does anyone have a workaround or another solution?

You can still work with .wim files using DISM as before. However you can't use the WICD tool to create a new windows installer from a customised .wim file.