I have given you my conclusions and my recommendations.

But if you still want to go ahead with the same you can do that but you might get some issues while or after repackaging. Repackaging - Well being in this area for almost 9 years,an ACP (Altiris Certified Professional) and reading various articles from Microsoft and Bob Kelly's (author of App deploy) whitepapers it is SERIOUSLY NOT recommended to capture a device driver installation. Use Microsoft's DIF-X to install the drivers but this will not install the software, here is the link to DIF-X ĥ. If you want I can provide you with some scripts that would be some help to you in this regard.Ĥ. Incase you fail in step 1 and 2 above then make an autoit script with the hidden command line that I wrote in my msg earlier, this will just allow the setup pop-ups to flicker for a second and then they will disappear (I also do the same when we don't get help from any where as some setups are not created for enterprise use). Try to contact Epson for more options on this setup or for makepackage.exe utility or any other help that they can provide you to make this package silent (my team also does the same when we are stuck in an issue like this ).ģ. Contact Epson or look for vendor documentation which can tell you about making this setup silent (I agree with aogilmor here!)Ģ.

Well coming to the point here are your options:ġ. Thanks for giving me the package source, I have gone through the same and found that this package is created by Epson's own utility which is called 'Makepackage.exe' Please check if you have this utility given to you in a CD or otherwise because if you have the utility you can modify the setup and even make it silent.

Epson scan 2 utility