It was a bug with v7 and 16170 UUP files, one of the pro (n) indexes is cloud (n) instead of pro, it was solved with v8 but when i used it with 16179 UUP files the error was there again. Didn't try v9 yet.
Dism info show the "Display Name" and "Display Description", which MSFT choose to be branded as Pro for Cloud edition since RS3 insider preview uup converter only gather/export wim files as they are for AIO, Cloud edition is the second duplicate something to live with, until they correct it in final RS3 release
After uup-converter-wimlib-9 generated from (16170-16184) ISO, can only be a new installation, can not upgrade the installation, upgrade installation will be error, the new installation is normal.Upgrade installation will restart after entering the recovery interface, followed by the display error interface. Into the Microsoft troubleshooting instructions, that can not help. New installation is normal. In the end where is wrong?
Today with another tool (dism + +) from esd to select ActionList.xml, generated iso, can be a new installation, also can upgrade the installation, although the conversion time is slightly longer, thus proving uup-converter-wimlib-9 bug Cause, can not upgrade the installation of the problem. the author of the uup-converter-wimlib-9 can compare the use of your tools to generate ISO and (dism + +) the difference.
the tool is also very easy:Look at the picture ps my way:C:\Windows.old\WINDOWS\SoftwareDistribution\Download\de78c8105850d80f337b84cbbf26c425\ActionList.xml,-----Name and select the path you want to save
Could you share this file for the failed upgrade? thanks Code: C:\$WINDOWS.~BT\Sources\Panther\setupact.log $WINDOWS.~BT is hidden
I just deleted that VM, it got stuck on the shown screen (forgot that i always could map the VMDK to copy things for testing ) I will redo it if my 14393 > 15063 UUP test doesn't fail.