Antonino

Well, I am glad it does the trick.

I could send you the one that works for me, but would it work for u as well? what i can suggest u do is go to https://schneegans.de/windows/unattend-generator/?PartitionMode=Custom&DiskpartScript=REM&InstallToMode=Available it will provide u with possible choices for u to make in order to obtain an autounattend.html that works for u. u can then put the resulting file in the autounattend slot provided in winntsetup and u will be good to go. i did this myself, but it is on a per-system or per-machine basis, not on a universal basis.

tx, so u suggest i should not reply anymore

what is an assembly? do u mean a good-to-go system? if that is the case, start by making a 15gig vhd, for example with the function provided in winntsetup (u will find the button on the bottom right corner of the application). then install the iso as indicated in the application itself. if u want a cleaner system, u can open sample.ini and take all the semicolons out (this will be important when winntsetup installs ur iso). after u have modified sample.ini, do a bit of studying of the various options wintsetup provides, and when u run into doubts, do not hesitate to ask in more detail here. I will reply asap.

and..., yet another caveat: I still use g4d 4.5c with ahci/nvme memory-mapping-based ramboot patch, the fastest ramloading implement I have found so far, altough it leaves us at least one version behind. unfortunately good old Kai Schtrom, the inventor of svbus, has not made the remapping kinda thing compatible with g4d 4.6a. this possibility is apparently even more remote if we consider the invasion of uefi-based mobos that, albeit probably wrongly, convinced many people to go along for the innovation ride in order to feel on the safe side (lest it should not work as it used to during the bios-based-mobo era). I say probably wrongly because the find line in the menu.lst file can be successfully adjusted to fit a full UEFI scenario. to cut a long story short, at least with new mobos, which still have a csm facility, the problem that might arise is the system's failure to boot even after mapping ok. I solved it with disktuna, a very effective disk and vhd analyzer, defragger, optimizer and compactor. I suggest u should run it both on the host disk (for outer vhd contiguity) and each of the vhds u use after mounting them, one by one. it will spare u various headaches if u use this ahci/nvme patch. By way of an expansion of the above, I can say I have found out one feature of jfx's winntsetup that deserves our attention for 2 reasons 1) it compacts vhd's like no other, and 2) raises the probability of the vhd in question to boot in ram ok, probably for leaving more space necessary for the booting process. viz, I suggest that u should click on the windows button on the top right corner and call the local windows installation of ur concern from the menu, then choose compact windows and let it do the trick. for either reason or for both reasons, u will not regret it.

I am glad it does work. thanx for the tips. as for what u wrote (If one really wanted, you could delete the dll files these services rely on, that'll also work. If you really want a barebones system, you can delete all autochk files, with voidtools search, as well as sppsvc too, if you don't use microsoft office) I strongly advise that anyone keep all the rest. just disable the services, lest the modern immersive control panel should not work anymore.

I am glad u like my proposal, but I haven't yet got an informed answer. if ur test proves right, we still do not know whether we can, and/or how we will, effectively automate it into winntsetup.exe. U got a point, though: if it cannot be pre-installed, we will keep using it on a post-install basis.

attaboy jfre84. gonna try it out. now @everyone do not junction the following files and folder \progran files\windowspowershell \windows\system32\windowspowershell \windows\temp from anyplace else, or some powershell2-relying or wmi-calling programs may not run properly (it is certainly the case with microwin, inside Chris Titus' winutil.ps1). For the same reason, do not touch the following files and folder \windows\system32\microsoft \windows\system32\mispace.dll \Windows\System32\storagewmi.dll Still for the same reason, do not zerobyte the following folder \Users\USERNAME\AppData\Local\Microsoft\Windows\WebCache and now @jfx and @wimb your minwinning and wimbreducing respectively do not delete the following windows subfolders attached herein. To the best of my knowledge and remembrance, they have been left there because they are too small in size for anyone normal to quibble as to whether they serve any apparent practical purpose or not. As a notorious file and folder exterminator, I have been doing without them for quite some time now, with no hindrance or prejudice to any software functionality. I would like you to differ if you know or believe it is not so or confirm if you know or believe it is so. Thank you ever so much in advance. FolderListJFX.txt FolderListWimb.txt

says the file is infected with a virus

@ibay770 btw if u run this after install, ur system will be all the quicker disableservices.bat @JFX if u can tell us how the above file's content can effectively be integrated or embedded somewhere in winntsetup.exe for use during the install procedure, we would pretty much appreciate it without having to do it after install.

attaboy, then. now tell me if u have taken advantage of sample.ini in the tweaks section. if u have, just open the file with notepad or the like and erase all the semicolons. u can safely remove the appx's listed. I can also give u my version, with more appx's to be taken out. btw, how big is ur vhd? copy it rename the copy differently. make sure u cam boot off both of them. this way, if u modify vhd1 and something has gone wrong, u will still be able to reboot off vhd2 and copy it back on vhd1 so u will be back to your most recent best. no need to backup or restore anything - it is its twin which is its best backup version, the restore one being the vhd you will have copied back to the one that went wrong. if u have more than one disk u can have an omonymous vhd, as u will no longer need to change its name. d'dya get da drift?

guess i've already told u about that; anyway, after 11 my time I'll ask Virgus to explain it to u in more detail - not that easy, believe it or not. as far as the whole windows reduction process is concerned, have u installed win10 or win11 on a vhd yet? that is what I meant when I asked u whether u were ready for more. pls let me know.

ready for more, ibay?

well, as regards scraping off as much as possible from reboot.pro, I guess Virgus tried something of the kind, but as far as I can remember, he did not consider the initiative worth his while taking. only bits and pieces, and... what we really miss is the immediate interaction with the pundits there. scriptwise, Virgus is very good at writing scripts, so when he is not caught up with something else, he usually comes up with something useful. I usually test what he does - so far so good. me, I have good memory to keep track of wherever whatever is at. files, folders, junctions, etc. I usually go by intuition and/or by trial and error. so while waiting for Virgus to continue all the work done so far, I can tell you what scripts turned out alright. a couple of mine are actually empirical .reg files. say I have customized an os vhd and wanna try to customize another one, there is actually no need to do it all again from scratch, so I exported a few registry entries concerning my customization on vhd1.dhd and imported the same on vhd2.vhd. it is not a script but this is something close to what u mean. in these respects, I have been able to automate the repetitive. of course if u do not like my colors u cannot use them regs at once, u would have to do some tweaking inside. to give u a clue, this is the second stage, the first one being the install thru winntsetup. it will take care of most of it from scratch. just grab it and install an iso u already have and then u will recontact me as to what it is not yet clear. c u in a bit.

well, I'm back home, so I can answer u tenet by tenet what got reboot.pro shutdown, lack of funds for hosting? you are quite right Would it help to revive it? this is Virgus's idea, which I totally espouse, and I guess u would as well - virgus calculated that if 10 of us contributed €10, that would make €100. there is only one problem, nuno, the keymaster of reboot.pro, is unreachable. we lost track of him and the site masters probably don't feel authorized to let us know how he can be contacted, if I have understood correctly, but I guess Virgus could be more specific about it. or should we perhaps use this as the replacement? This is my idea for the time being, but I haven't gotten so much feedback as I used to on reboot.pro. JFX's answers are slow but sure, though. "great space gains can be obtained in shrinking the following folders: winsxs, driverstore, and some other ones as well." Curious how to shrink those, can it be done with a batch file? some bits can, while others can't. be ready for a plethora of instructions on the matter. I'm all for a tinyOS, I think a guy on the archive got a winPE of win7 to 65mb, winPE is the inspirational software for what we r doing, but I guess we basically do it the other way round. one could also go about adding things to winPE, whereas we tend to subtract things from an os. winPE is not an os proper, and does not keep any settings across reboots. I know ntlite has ways of deleting winsxs but it costs money. no need for ntlite or similar stuff. jfx's winntsetup, which can be downloaded here does most of the job. check it out and go to the tweaks section which shows a sample.ini where he commented out some appx to be kept; I took out all the semicolons I found in front of those appx because I do not need any of them (this concerns the 3rd section of the file, as the first 2 should be left as they are. In liew of ntlite, chris titus has offered his winutil.ps1 which, among other things, has a microwin function that does about the same, the only drawback being it does not take wims or esds, only isos with wims or esds within them. A guy tried to slim to down windows and make a win10to7 project but he got crucified in the comments so he stopped it: https://forums.mydigitallife.net/threads/project-10to7-slimming-down-debloating-windows-10.76459/ Virgus would find this interesting I know strelec who made a winPE, has unique ways of making his images on the smaller side, for example net framework is only extracted and added to the ramdrive if a program calls for it. we do something similar, but our net framework and vc++ are phisically on d:\ (the physical c:\ hosting the vhd) and logically junctioned back into c:\ (the vhd), just in case a program calls for it.