Tested with NTLite and only with DISM but I don't remember the error with DISM With NTLite (uses DISM) it's Error 0x80070202 - [514] The target filesystem block is shared across multiple scopes.
With only DISM (command prompt) same error But perhaps DISM doesn't take into account the order specified in the command line, I haven't checked.
Use W10UI, it does the job well, as shown many, many, many times MSFT is battering the fun out of dism integrating updates, it sometimes needs some smart dev to circumvent that and we happen to have one of the best here.
Can't, if I remember correctly, need PowerShell, and I don't have it on the PC where I'm doing my tests (OC's PC) And I integrate new versions of certain apps (and remove the old versions), so I don't want to use multiple "softs".
Then maybe ask for help at the forum of the used tool? And maybe the fact of a f**ked up install could be part of the cause?
ISO unmodified, so no. We're debugging with the developer. I wanted to know if MS had changed anything since I'm getting an error just with DISM (command line) EDIT : all good, had an extraction problem when file crossed a certain size
some question on W10UI v10.59b update , may i ask is it the installer on this version update "bootmgr.efi" with already enable UpdtBootFiles =1 ? because check the installation media look like not update "bootmgr.efi" wtih enable UpdtBootFiles =1 , but other boot has been update excepted the file.
Search for "bootmgr.efi" in the search tool and check for answers by @abbodi1406 From here https://forums.mydigitallife.net/th...11-uups-with-ease.75052/page-302#post-1910011 and down.