1. Here's an example of a deployment day: open winntsetup.exe, load 7-admin.ini for virtual machine testingsetup finished, take HDDinsert new HDD for windows 10 deploymentsame instance of winntsetup.exe, load 10-user.ini which contains image, unattend and OEM paths different than the 7-admin.ini If I do this 10 times a day, should I do it manually? I'm the only one who requested because I am the only one that actually uses it every day, and some times more than once a day. 2. Passing on to another issue... I think something is wrong withour XP deployment. If I already have a winNT.sif in XPDir\i386\, and trying to add an external winNT.sif or winNT.txt, the result is strange and unstable. Sometimes it applies the file in i386, otherwise the external one. I've tried it 3 times, and it is the same. It only worked when there is no winNT.sif in i386. If this is a normal behaviour, a suggestion might be to exclude the file in i386 if an external one is applied. Can anyone confirm? 3. Also, I would like to say that your application is the best and does not need any kind of change. Some points to look out for, and my humble two cents: always make it compatible with WinPE, cause that is where it will be used the most. All of them, because on some computers, the latest PE does not work, so try to maintain a PE2 (Windows Vista) To PE10 and beyondmake available the same options in the .ini configuration as well as in the command-line. Sometimes it is easier to work with .ini rather than batch, and other way aroundBe on the lookout for bloated stuff, keep it small, keep it simple, and focus on deployment only. Not other functions