Customising Windows 10 Builds

[RobertX]

I am looking for a piece of software that will help me customise the setup on a Windows 10 Pro image that I got from here: https://tb.rg-adguard.net/public.php

With theSEMAR's help, I am not going to worry about pre-activating it as it is already activate it.

I just need to customise, maybe slipstream updates to it from Microsoft, and leave things out like CD-key prompts and the like. I believe it's called "unattended setup."

What do you use for that purpose?

P.S. I am opening a new thread instead of putting this request in theSEMAR's KMS_VL_All thread since it's got nothing to do with it. However, if I am in error, just attach it to his thread.

OK, fire away.

[waregim]

You may want to try:
https://www.ntlite.com/features/
https://winbuzzer.com/2015/08/02/how-to-...es-xcxwbt/


I *believe* there is a better one, but canot recall it at the moment.

There is, of course the *hard way*:
https://web.sas.upenn.edu/jasonrw/2016/0...eployment/

Slipstreaming is by nature a complex process. You can add what you want to an ISO and copy and install afterwards simply using any good ISO program.
But slipstreaming adds the new stuff directly to the install scripts as part of the OS.

Personally, I would not trust Insider stuff, as they probably have a kill switch built into them after a certain date. For M$ it would not make sense otherwise.
Use a nice hacked version and slipstream from that. KMS works fine, though M$ updates and Adobe might try to kill it. Just reinstall it. (Its listed under services.msc).

Meself, it would not make sense to add programs to an install of Win. As the first thing I do afterwards for days is chop. And chop. And chop.
I would be wary of *removing* crap during install like the store, Cortana, and Win Defender. Checks during the process may well determine that the ISO is damaged and terminate.

[RobertX]

Thanks, waregim.

I did try to remove the default firewall and, sure enough, the installer crapped out. It was a good thing that I was using ISOs to install on an OS simulator like VirtualBox.

But thanks for the info anyways. Now I know why.