Antonino

and, yet another caveat. do not take out c:\windows\globalization\ICU if u want ur most recent winhance to work.

BTW, another caveat, before I forget to tell you: cleaning ur windows side-by-side configuration folder (winsxs) might leave u unable to run certain software that usually worked before. no worries. make a backup of the folder and place it anyplace else but where it's at, and then run the cleaner. Once u spot the software that halts as a result, copy the backup back to its original; rerun the software - now it will work. Once u make sure of this, leave the software running and try to delete the whole content of the winsxs: u will not succeed in it because, while the software is on, it involves a few winsxs subfolders that have open files. Now copy this select list of subfolders and elsewhere and keep them in a folder named, say, "softwarename"sxsstuff. u can now have the whole winsxs back again where it should be at, rerun the cleaner and add the content of softwarenamesxsstuff back to where it was before the cleaning, and u r good to go. I am sure you will find it much simpler to do than I have explained.

Attaboys!!!

windows version u mean? ?querés decir la versión de windows?

thank you, I'll check it out and let you know.

@JFX btw, sometimes I get a "could not copy the offline registry" message at the end of the minwinning procedure. Any idea how to troubleshoot it? if I try to reboot this specific vhd, it gets stuck at the first stage of the booting process saying it could not find system or system is corrupt; instead, if I copy the whole config dir to the windows\system32 subfolder before rebooting, everything goes spick and span, also the letter z:\ for ramdisk which, as I mentioned in earlier posts, was loaded as j:\ (the next useful drive letter) at other times.

I figure u r talking about sample.ini, which already contains a list of apps u have surely added. is that all the lot there is to it or are there any more to possibly and safely remove?

Oh, btw, one more caveat, before I forget: could we have a list of "officially" redirectable folders and subfolder in windows (those with the location tab in the properties mask, so to speak) and possibly a way of making "officially unredirectable" folders redirectable (provide them with the location tab in the properties mask)? It is somewhwt frustrating, if I may, to find out about this "new" opportunity only after years of us going about in the realm of OS reduction. It is just awkward of us to resort to junctions to do what can be done naturally and/or (if possible) "naturalize the not-so-natural folders and subfolders" by a facility that the OS offers. The aim of the quest delves upon a remote wish of mine to keep just the "sheer Os core" (whatever contributes to and guarantees the booting to the desktop inferface, perhaps the windows system32 and syswow64 files) inside the vhd, and move the rest of files and/or folders outside the vhd, especially if we find that they can coexist and be shared with other corresponding ones in another os vhd (windows 10 and windows 11, for instance). thanks in advance for your possible contribution.

hi again, here is another one of my latest findings, which I would like to share with u in the form of a tip do not get rid of \Windows\System32\ServicingUAPI.dll lest u should not be able to have a stable immersive cpl any longer I will tell u about any other must-leave-alone dll in a bit. well, here's another one of them coming up \Windows\System32\SwitcherDataModel.dll \Windows\System32\SettingsHandlers_Gpu.dll don't take them out lest u should get one of those nasty unknown hard errors on an explorer tag right at the start and all the ms:settings-connections lost (and the significance is no immersive explorer window) I hope that is all, but u never know. As a matter of fact, there follows a bunch of them to leave alone as well: \Windows\SysWOW64\d2d1.dll \Windows\SysWOW64\d3d10warp.dll \windows\syswow64\dlcoer.dll \Windows\SysWOW64\dpapi.dll \Windows\SysWOW64\gpapi.dll \Windows\SysWOW64\ncryptsslp.dll \Windows\SysWOW64\NetSetupApi.dll \Windows\SysWOW64\NetSetupEngine.dll \Windows\SysWOW64\ntasn1.dll \Windows\SysWOW64\rasadhlp.dll \Windows\SysWOW64\rasapi32.dll \Windows\SysWOW64\twinapi.appcore.dll \Windows\System32\ws2help.dll lest u want to see netsetman.exe totally unable to run properly. well, see u in a bit for other leave-alone dlls here u go with \Windows\servicing \Windows\System32\winmetadata keep both of them subfolders lest winhance.ps1 should fail

left, right and center, I daresay

btw, I owe this one to jfx, and I apologize for not learning it any earlier than yesterday evening. I am alluding to the power of Sample.ini. In an era of constant quibbling as to whether it is better to reduce the windows iso a-priori by ChrisTitus' Microwin, by NTLite or by tiny10/11, I can guarantee you that JFX has always thought and acted ahead. Sample.ini contains all the a-priori deletions to do it more quickly and effectively - a radical dude like me has gone so far as to take out all of them, by deleting jfx's semicolons. Well, I have reduced all windowsapps to just 2 or 3 of them (the vclibs), which caused no hindrance to the system. what is more, the procedure can be carried out on an already minwinned system as well. the gain in recovered space is slightly less than 1gb. Attaboy jfx. btw2, I have just found out that u do not need the boot folder on c:\ if u boot thru the original bootmgr, whereas u can't do without it if u boot thru svbus, whether in filedisk or in ramdisk mode; of course u do need bootmgr inside ur c:\ no matter what (no doubt about that), as it will take over the process started by the bootmgr on d:\; also svbus, for that matter, takes over the process started by bootmgr on d:\.

everything ok if it does boot ok, which can be done even by simply assigning the desired drive letter (a posteriori, as it were). But if it does not boot ok, and it does not probably on account of that, how can I change the letter the way u suggested on an offline basis? Well, I'll be, I'm going to minwin the thing before adding ramdisk as z:.

Hi again, JFX, I need to set my temp-and-scrap ramdisk letter z:\, where I have juctioned stuff from c:\; my problem is that if and when I do get to reboot the system after minwin, the ramdisk defaults to i:\ instead of the desired z:\. what can I do to sort that out? Most of the time it does not eve comp0lete the boot process to the desktop, probably as a result of wrong temp location (it cannot find the z:\ drive indicated by z:\temp in the environment variables). this last concept also applies to whatever needs temps on z:\ even after it does get to boot to the desktop. what can I do to force the minwin version to assign z:\ on the ramdisk?

another caveat reminder - I do not remember exactly if I have already told u, but I can state and/or confirm that \windows\L2schemas must not be deleted if u want wifi. Let me see if it can be alternatively moved on some other drive and juctioned back to c:\ I will come back 2u in a minute or so. And yes, I can confirm that it can as well be on another drive and work just the same as long as it is junctioned back to c:\windows (its original location), which is particularly handy when u want one folder to serve various windows os's.

whatever is missing, u can retrieve it from the previous version, i guess. this is also true of ur settings that cannot be memorized for each and everyone of us across generalized upgrades. I guess it is up for each of us to do that too. For instance, when it comes to the remove dir inside minwin, jfx said to leave everything as it is, and add some mysoftware.txt file which should contain the info on what else to keep (!\...) and what else to delete (\...), so if anything goes wrong, we can limit our search for the error(s) inside this file, without the hustle and bustle of searching around.