Follow us: 
User Rating: 1 / 5
ENGL Imaging Toolkit 11.0 is now available to download and includes:
For a complete list of changes in this release review the Imaging Toolkit release history and compatibility pages.
With the release of Windows 10 1803 and ADK 1803, we have performed extensive testing with Imaging Toolkit 10.0.9. During those tests we have found compatibility issues with Imaging Toolkit 10.0.9 when creating and deploying Windows 10 1803 using ADK 1803. We have also had several customers experience similar issues after upgrading to ADK 1803.
There is currently no workaround with Imaging Toolkit 10.0.9.
These issues will be resolved in Imaging Toolkit 11 which is due for release at the end of May 2018. In the meantime, ENGL recommends that customers do not upgrade to ADK 1803.
Compatibility testing of System Center Configuration Manager (SCCM) Version 1802 with Driver Manager and Imaging Toolkit has been completed.
Please review our product compatibility pages for detailed version information:
Driver Manager compatibility
Imaging Toolkit compatibility
Regards,
ENGL Team
ENGL ImageInvoker 2.0.1 for Symantec Ghost Solution Suite 3.x is now available to download.
This release includes enhancements to domain authentication and includes fixes to font-sizing on the WinPE client when run on hi-res displays. For full details of changes in the release visit the ImageInvoker release history.
ImageInvoker is available as a Free and Enterprise edition. Check out the product page for details.
User Rating: 5 / 5
In the realms of niche issues this one is pretty well up there but there is an issue with the x86 WinPE boot WIM file in the 1709 ADK whereby some of the files necessary to manage NVMe disks have been 'mislaid'.
The disk can be seen, selected and cleaned in diskpart with no issues but attempting to create a partition reports:
Virtual Disk Service error: The object is not found.
Whilst this should be fixed in the next ADK release be aware that if you are using x86 boot media from the 1709 ADK it might not be a failing disk drive as a general search of that error might suggest but this little niggle instead.
If possible, often simply by using UEFI rather than legacy/BIOS, use the x64 boot wim instead as this works correctly. If this is not possible, either use an older version of the ADK until the new version is released or applying the latest cumulative update to the boot.wim should restore the missing files.