Yes, if you select a different boot drive, your local boot partition will not not be touched.
For automation there are many command line options, see F1 - help.
I would ignore them. If there is no lpq.exe in system32 than that applications is no installed and does not need a .mui file.
If it get's installed (by dism) later, it should copy the .mui, too.
MinWin and RAM booting Windows was a - just for fun - project for me.
I don't share your passion about it. So if you want to create a database, be the first one adding something to it.
For me, I only provide the tool and a basic example.
Oh, wanted to improve that error message for years.
You have a WinPE selected as source, that's not supported and doesn't make sense.
Use bootice to create a boot entry for the WIM file.
No, Setup=1 just means the filter is only used for sources that are still setup mode (SystemSetupInProgress=1).
With some luck you can get the missing file logged somewhere in \Windows\Panther.
That sounds like the WIM has data corrupted.
Try to apply the WIM with wimlib-image.exe maybe it reports more error data.
If wimlib-image.exe failes and Dism works than it seems to be a wimlib bug.
You should not use DISM to capture a installation WinNTSetup has prepared for this one partition.
Either delete HKLM\SYSTEM\MountedDevices before capture or
always use WinNTSetup for capture to WIM and apply to disk.
Drive letter assignment is really simple stuff.
WinNTSetup will calculate and write \DosDevices\C: to HKLM\SYSTEM\MountedDevices
On first boot Windows will recognize a different drive letter and does all the work.
This version will add logging for black and whitelist as well MUI and MUN file removal.
@suxichao You the first one having that problem. Try to nail down what causing it.
@wuliyen Seems the MUI progression if a bit a aggressive. This should limit it to *.mui files only.