Hello,
For everybody, The staff (many thanks)found the problem and give me a workaround.
Hello, thanks for providing information about version of WADK10
installed.
We have found that there is a problem in the code for which the version of WADK10 you have is not correctly detected even if it is installed on
the machine.
We are going to open a defect to have this fixed
The feature we are interested in for leveraging dism command and
convert the install.esd is "Windows Deployment Tools".
In the meantime please run the following workaround
1) deinstall WADK10 from the machine where console is running.
2)deinstall any possible "windows deployment Tools" that could be on
your machine (for example if you have a previous version 8)
3) Install WADK10 GA feature "Windows Deployment Tools"
4) After the installation is completed verify that on you machine (where
bigfix console is installed) you have the following entry in your
registry
if the machine is a 64 bit machine
SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall
\\{56B71DBF-E9C9-B173-3298-78D76AA6A70B}
or
SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{56B71DBF-E9C9-
B173-3298-78D76AA6A70B}
if the machine is a 32 bit machine
Clicking on the 56B71DBF-E9C9-B173-3298-78D76AA6A70B key, you should
have "Windows Deployment Tools",
Display Version 10.0.26264.
5) Once you have verified that you have the
56B71DBF-E9C9-B173-3298-78D76AA6A70B entry in the
registries at that path, you can reimport the .iso.
We have tried the steps for workaround and even if the converting
for .esd takes lot of time to complete, it is successfully at the end.
Let us know if workaround works in your environment as well
I'll inform you about the defect (APAR)
number and the date the official fix if going to be released