I agree the debugging of switches could be improved, and one of the future goals is to have a mini execution tool which would nicely prompt what happened.Ĭurrently it is executed during the time Windows shows no UI, not blaming Windows but this was not a priority so far. Then if it's unclear which installer reports some error, edit the setupcomplete.cmd to remove off' line, then you'll see the command before it fails to know which it was. When the script is fully executed, it auto-deletes itself, so when retrying recopy the entire \Windows\Setup\ folder content from your ISO/USB '.\Sources\$OEM$\$$\Setup' folder. Just make sure to skip those that were already installed with the stuck first attempt. The installer which shows an error message or prompts something needs a different switch probably. You can test the resulting script manually in command-line, best is from a virtual machine, and see which installer complained.Ĭ:\Windows\Setup\Scripts\setupcomplete.cmd If it doesn't work from first go, some additional info:Īll post-setup installers need to be set with the silent switch, and have no prompts. Regarding the additional software question, I'll copy from one of our first emails:
1 Comment
|