Discussion in 'Windows 10' started by LiuBang, Jan 19, 2022.
You need to login to view this posts content.
i know a very good way to do this using all of these softwares with one iso . i already have the presets with me for 1607 LTSB ISO . it is slimmed down to the most slimmest iso ever . i already said that in msmg thread but mostly people are not interested in my tutorial thats why i restricted myself to let anybody know how to deal with these softwares upon one 1607 LTSB 14393 fully updated iso till date using w10UI by abbodi1406.
hmm i understand
ok i get it
thanks for your answer
I consider myself a n00b and would very much appreciate a tutorial on these tools. I've used nLite in the past, and recently MSMG tool kit, but never heard of the others.
There's always something new to learn. And someone who talks about using multiple tools on a single build surely is a winner in my eyes. Will greatly appreciate your tutorials.
i didn't expect someone to get this thread up again
in this case i have to say when i created this thread i didn't know much , right now i did make a some sort of sequence of steps to build an OS from windows images based on same programs but has steps on sysprep and more stuff in how to modify most windows files (doesn't Include any Paid programs , and result guaranteed to be exactly as u want it to be)
right now i'm planning to make a youtube channel but unfortunately it will be in arabic because i gave up on making videos in english due to the fact all the stuff i will be talking about are taken from english websites plus my testings and the stuff i tried and worked
i did make a website to put my stuff on to make things more clear for the users who does like my builds , you can check it maybe you find something you like
i will probably get banned if i posted the website link so just write in google search "Ankh Tech" and my site will be in the first result
i won't be making these tutorials sorry about that , it will take huge effort to make the videos in english than making them in arabic which is my native language and i'm sure they are needed more in arabic than in english
have a good day sir.
I don't understand the point of win-reducer
if you remove most of the components, Win. will stop working
what is the point of these tools ..
who said most ?
also who said i'm talking about winreducer ONLY
do them in arabic and add subtitles but not generated from you tube sometimes they are off. i would like to watch and read this tutorials.
You need to login to view this posts content.
My first computer had 16 kilobytes of RAM for programs and 8 kilobytes of ROM for the "OS", 1/5 of the memory of an average SIM card, and it worked.
41 years later I'm updating a Win7 image and the components db alone is 2.2GB (almost twice the size of a whole XP SP3 installation), clearly something went wrong in between.
Services in Windows do a lot of things some users never use 3/4 of them, and a good share of them is not there to serve the user, but to serve MS.
Even in linux there are distros that are almost as large and bloated as Windows, while there are (current) installations that take 200MB of storage space and less than 100MB of space.
So vague references are just pointless, we need to talk of a specific image, of the target scenarios and so on
Sorry, but Windows people will never understand hard links and how the WinSXS folder works. Tecnically windows don't need it at all to work, but if (hypothetically) you delete it completely (say a 10GB Winsxs folder) you aren't going to gain 10GB of storage, a good share of what's inside it are hard links to the whole windows installation. So you gain only the space taken by the not enabled components (and superseded updates).
Install the hard link shell extension, a great utility to manage (visually) hard links, symlink links and junctions, but an indispensable tool to understand how the thing works, for non Unix minded crowd.
Yes and no.
I mean your questions are super legit, but is a bit surprising that come from a well above the average user.
i wanna say something about windows
i consider it to be an AIO package , meaning it's for all purposes but the question do we all need all the stuff included in it ?
for an example there is ALOT of UWP apps comes pre installed , Biometric services while alot of people use PCs and some laptops doesn't have fingerprint and few users use it and u can lock with password anyway
so the point is if u keep looking around for what is inside the windows that is actually not needed for most people you can reduce it's size without breaking it apart
but there is a point , someone said "de bloating the windows is like stabbing in the dark" it means u don't see what happened until u install the build and try it for yourself , also you don't know what's broken until you find it by testing everything
about x lite builds , he still didn't go in the danger zone , i call it the danger zone probably no one else call it that , the danger zone is where you start removing stuff that everyone else say it's gonna cause problems for sure like netframework , Internet explorer , Windows Media player , fonts etc etc
he does something i don't like which is remove fonts and tell you if you want them download them and disable paging file and tell you to enable it and he does that to keep the installation footprint small for eye appeal (everyone out there looking for the smallest installation footprint) fonts doesn't get lzx compression and the paging file is 2gb added straight up to installation footprint
the point about WinSXS is simply that WinSXS = Windows Features , u remove it u lose Windows Features means you can't activate anything in it cause the files required to active what's inside are removed
you don't gain 10gb , they are 7gb but you only gain 1.5gb - 2gb in installation footprint and around 700-900mb in install.wim
if you integrate updates in the build this thing goes to 10gb maybe more increases installation footprint and install.wim drastically , the only way to reduce it again (it can't be done using any Tools) you have to install it in a VM then Reset Base then sysprep and capture it , guaranteed to reduce it's size to almost how much it was before updates
have a great day sir.
good idea , i think i have to try maybe i can manage that if i manage to keep the words simple and maybe the subtitles would match what i'm saying which more likely not gonna be precise but i have to try
thanks alot for that idea
Aside that the example of removing the whole winsxs was an hyperbole, and that a properly decrapped windows is fully usable, here whe have a bunch of kids that format and reinstall twice a week and don't care of their data because they keep all on the cloud, or on a external nas, or just don't have anything to loose.
Should we have much concern for this kind of users.
Be sure that skilled people are perfectly able to understand what they need and what they don't need when they tailor the ISO.
Perhaps the optional features on win sxs can be removed with the official dism /remove switch. Something that MS itself does with the .net 3.5 feature, which is present and activaable, but not included in stock winsxs (payload removed).
Just like in that case all you need is the original ISO as source. Something that was the norm before Vista.
In short just use your brain, and a bit of common sense and avoid the brainwashing process attempted here by some "genius", who talk continuously of butchering, chopping and other similar stupidities.
100% right , and about who formats and re install twice a week , the Tweakers out there who make a Zillion Custom OSes in an hour with fancy looking stuff or just some random stuff feed on these people with Ads on sites , downloads , youtube videos etc etc ( and i don't know what else to be honest if there is something inside their builds)
thanks for your great point of view