Antonino

do u mean I should name the topic? I thought it could be considered a follow-up from the miniwinning process, as further and wider deletions to make the vhd smaller. to this end, I did discover a glitch, apparently due to taking out so much stuff in the end. At least one subfolder (do not yet know which one) should not be deleted, inasmuch as it is responsible for letting, say, directx install. Now, until I find out which subfolder it is, I cannot install directx if need be, the error being "the log on user does not enjoy the necessary privileges to run this executable, or things like that. it is not much of a problem, as one should have installed directx and the like before, but just in case one has forgotten to do it, why not let him do it now. I will see u in a bit to tell u which directory I should not have taken out. Well, I have to admit that, no subfolder of the above list is the culprit of the above problem, which must entirely rest upon mysoftware.txt. I have just tried deleting each of the subfolders one by one on a freshly-made vhd and ... no issues whatsoever. All this means that I have always had a final miniwinned vhd that has never worked on certain exe files. I didn't realize it any earlier than these days because I had never gotten around to trying to install anything after miniwinning. However, for clarity's sake, I will take good care to check mysoftware.txt for any line that could have caused the issue. for the time being, I am happy to learn that all my suggested deletions have caused no issues so far. My point was only that a great many subfolders (of course not all of them) are without basis for want when it comes to normal miniwin "unmixedreality" win7-like operations. the system seems to be fundamentally based on system32 dll's (and a tiny bit on syswow64 dll's as well). But of course I welcome anybody who begs to differ not to hesitate to do so.

Sorry Jfx, what I took for granted was keeping a copy of the newly/recently configured/customized windows install to one's own needs before miniwinning and deleting all the stuff I listed. Supposing u have a new nvidia or ati driver to install, u can resort to your latest wim or esd that u will have saved soon after the customization and install the new driver from there before reminiwinning and redeleting all. it takes about 15 minutes for newbies if u keep it all together. That is exactly why I recommended keeping an "original" wim or esd to restart from. it is about a couple of clicks if u have it all there. If I were to try and install a new nvidia driver on the miniwinned version online, I would have trouble even without having deleted downlevel (but this is probably not applicable to my scenario, as the driver transfer would be from win10 to win10/11, not from win7/8). that is why at every nvidia update i go wim/esd --> vhd --> nvidia install --> miniwinning --> final retrimming with the above, and so on and so forth. and to tell u the truth one does not even need to keep all nvidia content (all it takes is try deleting the whole nv_blablabla driverstore filerepository subfolder while a game or something is on and leave the undeleted files alone, which are the crucial ones) - the procedure spares/clears a good 1.7gb. as for wbem, what are the applications that use wmi? what are code tags?

well, ultimate \Programdata, \Windows, \windows\system32 and \windows\syswow64 subfolder purge. the following subfolders might as well not be present in your win10 and/or win11 miniwin, without any prejudice to ordinary functionality (unless otherwise proven or informed): \programdata\Dbz33C09 \programdata\Dbz717CC \programdata\ProductData.BackupByPortableAppC \windows\BrowserCore \windows\CbsTemp \windows\CSC \windows\IdentityCRL \windows\L2Schemas \windows\LastGood.Tmp \windows\Migration \windows\Pbr \windows\PLA \windows\schemas \windows\SecureBootUpdates \windows\security \windows\SKB \windows\System \windows\addins \windows\bcastdvr \windows\System32\Hydrogen \windows\System32\ias \windows\System32\icsxml \windows\System32\inetsrv \windows\System32\Ipmi \windows\System32\Licenses \windows\System32\MSDRM \windows\System32\MUI \windows\System32\NDF \windows\System32\networklist \windows\System32\PerceptionSimulation \windows\System32\ProximityToast \windows\System32\ras \windows\System32\RasToast \windows\System32\Sgrm \windows\System32\SystemResetPlatform \windows\System32\wbem \windows\System32\WCN \windows\System32\0409 \windows\System32\AdvancedInstallers \windows\System32\AppLocker \windows\System32\appraiser \windows\System32\AppV \windows\System32\Bthprops \windows\System32\ContainerSettingsProviders \windows\System32\DAX2 \windows\System32\DAX3 \windows\System32\DDFs \windows\System32\downlevel \windows\System32\DriverState \windows\System32\dsc \windows\System32\FxsTmp \windows\System32\GroupPolicy \windows\System32\GroupPolicyUsers and all \windows\syswow64 subfolders except downlevel and the language folder ??-?? (en-US or the like). I have been running my miniwin for a couple of days and I have not seen any different behavior from when the above was there. In any case, I recommend finishing off the customization of your OS before deleting the above subfolders.

is there any way to avoid such creation on next editions for those like me who r still in legacy mode? I simply do not want to get confused with all those partitions.

I wish I did, but no, I don't. All I know is that the site goes down once a month or so, and then it goes back up on Brito's or somebody else's factual initiative, if I am not mistaken. This time I think it has been down for a bit too long, relative to other times in the past, though. I can also add that, if it were a matter of money, Virgus and I would join in an albeit modest collection to have it back up.

earlier ones u didn't, correct?

which is...?

it will not complete the booting and a warning window says error with desktop.xml something and then I call the menu which stays unpopulated, if it completes the opening. Shall I run miniwin first time without mysoftware.txt and then with mysoftware.txt and see the difference? one different aspect is smaller size, mysoftware.txt might have taken out too much though. well, not really so. now that I have checked mysoftware.txt, I see that it entirely prevents certain files and folders from being deleted, therefore it cannot be the cause. I also have had to keep net.framework and assembly. do u want the txt's that take stuff out instead of those which keep stuff in and have a look? i can post them here if u like. I might as well post a list of the services we got left, as we have desabled some and then run device remover to eliminate all grey ones. that is all there is to the extra deletions I can think of. and of course no issue with windows 10. here I got a more detailed description of the error at bootup: DesktopWindowXamlSource: Explorer.exe - Fail Safe Exception, and then further down in the error window it says that all handlers will be immediately terminated.

My dear Jfx, u r surely correct, it is we who are running quite a bit behind. So, pls, tell us how we get around to regaining track of your fixes, so that at least we will be able to start somewhere. To give u a clue, we have applied almost the same scripts to win11 as we had done to win10. Pls also take into account that we have patched the explorer in order to have the taskbar on top, rather than at the bottom. Should we have done (and do) so after applying your fixes or was (is) that ok issue-wise?

thanx jfx, for a start, Happy New Year. Me, I am working with Virgus on the customization of miniwin scripts (we are the mysoftware.txt ones, remember?). Everything is fine with windows 10, though we are at pains trying to make it all work with windows 11 as well. no dice - it breaks in the last stages of the rebooting process, the issue probably being connected with taskbar structure and/or cosmetics. Is there anybody else improving scripts for win11? If not, or in any case, for that matter, do you think it is worthwhile putting any more efforts on win11 in view of the coming out of win12 in the hope that everything will work better?

looking forward to the fix, and Merry Xmas to all. I regret reboot.pro is down so I extend my wishes to all of u who are here and belong there too.

sorry about posting something a little off topic, but I am dying for an answer to the following: given the mac's ability to run windows for an os as well as the native mac, can one have rambooting, wimbooting, and what more and what not that we have normally done on the pc for years (ie, g4d menu, svbus loading, windows on vhd) from a mac machine?

well, I have just tried it and, ... what can I say, after some due personal adjustment, it works. the free-space gain is about a few hundred megs. I could not take full advantage of the shrinking, owing to my system's apparent need for systemapps, which forced me to place a ! in front of the string concerned. this may be due to the fact that it is a windows11, so I do not know if what I am saying applies to most other ppl's systems. those who know better, pls say anymore.

Attaboy!!! higher aims ahead!!! btw, have you modified any text files in the remove folder of this new edition? where do we get it from anyway? I do not see any link

so outside virtual or p2v scenarios, is one better off using ordinary vhd or is wimboot:wimcopy vhd any way faster?

1+ question for jfx, or anyone else, for that matter, to answer: what is the advantage of having the wimfile inside the vhd if one applies the wimboot:wimcopy way relative to plain wimboot mode (with wimfile outside, elsewhere)?

nossa! assim vc me mata! just kidding, huh

thank you ever so much for ur detailed reply, jfx. so, if i have understood correctly, winntsetup is already prepared to accept instructions from a file called MySoftware.txt if it finds it in the \Tools\MinWin\Default\Remove folder, right?

so will those files be removed from across the whole volume, regardless of where they are found? my second question was related to a group of system32 and syswow64 root files that I have to keep in order to let my favorite software still work after the miniwin deletions. so I was thinking of as many instances of !\windows\system32\filename.dll and !\windows\syswow64\filename.dll as my files to keep to be appended to system32-dll.txt and syswow.dll respectively. but just in case I place these strings elsewhere, in some other scripts, will they be effective, viz, will the files be kept where they are even if the instructions are not in the proper textfile? do u mean environment variables make the operation handier and more viable?

excuse me, I would like to know how to signal my intention to get rid of a certain filetype wherever it is found on the os disk/vhd, of course by a script string of this kind: \*.kyk\* or \*.scr\* are they correct? oh before I forget, is there any such thing as custom_command.txt, like in win_reduce_trusted, where one can place any string he/she sees fit? if there isn't one, can I append strings to any list I find, or do I have to use a specific script for them to be effective? tx in advance.