DISM GUI is only a GUI that can execute standard DISM commandlines. NTLite does that too but also can do things that bodge up the wim/live install beyond recovery.
Well aware of that, I just use DISM GUI for simple additions, usually flash updates, cumulative updates and drivers. I used DISM exclusively until I found that cool little tool. As far as RS3 in general goes, I am not building a new image until MSMG Toolkit 8.0 comes out.
Hello guys, If you have the black screen with flickering cursor that I had, you shouldn't use Custom UXTheme as I think it is incompatible with RedStone 3, hopefully the next update will fix the issue. Regards. addas
I don't want to mix NTlite with MSMG Toolkit. It will get messy for me to keep track all the changes that happen during editing. My standard procedure is remove, cleanup, integrate and pack all into install.wim, then I use Multi-OEM/Retail Project to activate and add registry tweaks to windows. If I could resolve this 'issue' it would mean -1 step I have to make post-install (set windows gui language). What do you recommend in my case?
I always do the opposite. I build the image up and then remove the components I don't want. I figure that cumulative updates might modify stuff it expects to be there so integrating them at the end after removing stuff might cause issues.
I have had issues in the past where I try to add a cumulative update to an image I have messed with and it fails. If I add the updates first it just works.
I used MSMG ToolKit and afterwards NTLite and now I have the "something went wrong" message appearing after setting the account name, the password and the password hint, again!
It looks like disabling the Biometrics service with NTLite caused this. Weird. Does that mean that if I remove Biometrics with MSMG ToolKit when it is possible this will happen again?
Guys? Please help, I'm sure somebody would exist that knows the answer of my question.... You can ask incase you think that I wasnt clear enough.
What is beneficial? I think that is a matter of opinion. Then one needs to consider if using LTSB is beneficial in a home environment.
In terms of customizing windows files further, selecting what to be installed etc. ? Yes, I throughoutly searched the stripped down Enterprise - LTSB 2016 and its limitations.
I think there is a misunderstanding between us. I dont think so because then I'd have to deal with all the crap programs that Pro forces you to install as well as non stop updates. The whole point I stick with LTSB is to avoid these nuisance and inconvenience. That is why I initially asked if MSMG toolkit would be viable and has any effect on Enterprise.
Not only that but the updates keep you safe(ish) from 0day exploits that require the user to literally do nothing to get infected. Avoiding OS updates in the world today on any PC you surf the web with is seriously stupid.
Maybe referring to the auto-installs of Candy Crush and other crap games that take special tinkering to disable.