Antonino

can u boot vhd's as ramdisks as u show u do wim files above? we normally boot vhd's into ram with the following g4d script title vhd2.vhd (SuperRamDisk) map --mem (hd0,0)/vhd2.vhd (hd0) map --hook root (hd0,0) chainloader /bootmgr

thanx, click-click. so, would the keeping of data be guaranteed if one had a fresh disk, convert it to gpt, partition it as u said uefi requires, and copy all vhds from the old disk to this one that has just been made for the purpose? would the vhd's work in the new place work just the same without any further adjustment? how about booting thru svbus? how about rambooting?

what if one wants vhdOS's only? what if one wants to have in uefi the scenario it has had in bios so far? what does one have to do in detail to transform the physical disk (d:\ in bios, for that matter) in order to accomodate the new uefi scenario? the only future advantageous situation I see is having one boot environment for as many vhdOS's as one likes, probably along with shorter booting times.

wonderful question!!!! Me, I'd like to know that too

Do u have any options other than the 3 ones listed in options.ini that can be used together or alternatively?

Hi, JFx, long time no see. Well, I have so long forgotten to ask u about a problem I have always had with minwinned vhd's right after the minwinning process. Most often than not, the property box shows the indexing allowed (the box is ticked) and no users (authenticated, ordinary, administrators, system, trustedinstallers) box ticked at all. If I reboot to have the vhd restart, it won't complete the boot cycle to the desktop interface, but it stays stuck before the wheel stage that does not even show. so I hard-reboot back into some other vhd and populate the list of permits in the min-winned vhd, change the property to administrator or any other (as long as it is not trusted installer) and then it will reboot ok. I have done so after minwinning with all editions of winntsetup, Is there any way of "controlling" the permissions in security in order for them to be ok and boot ok? albeit working perfectly afterwards, my minwinned vhds have always completed the boot process only on 2nd instance, never at the outset (on first boot right after the minwin process). Is there any way to right this wrong? Thanx in advance

@sharicov in which case, I suggest u should check with all alternatives there are in almost every window of winntsetup.exe: when in doubt as to whether to choose "uefi" or "bios", use "all" and u should be good to go.

we should ask christoff shenanigan about this, I guess.

as for the above-mentioned boot failures and BSODs, I suggest that u should go as far as the 22621 series to install ok. I also recommend a microwin session in advance and a good autounattend.xml install, to avoid useless inconveniencies and redundancies.

do not brute-force delete or zerobyte \windows\wbem if u do not want to lose full powershell functionality. u can move it out of the vhd and junction it back into its original place, though, if u feel u need to - it'll work as long as powershell.exe finds it. just one more caveat - the wbem folder is better off being from windows 10 rather than from windows 11. it will work ok in either system, which is not the case with the win11 one. Well, forget about the above, PowerShell 7 will tell and I will update - well, we are better off keeping separate junctions for win10 and win11, just to be on the safe side. as for powershell, u can have either or both, and play around with various versions of wmiutils.dll, wbemprox.dll and wbemdisp.dll, depending on the win10 build. win11s all work spick&span. And... yet another caveat: do keep the defauut and public subfolders intact beside your username in the users folder - do not move them anyplace else if u want most of the software (espacially the windows native software) to work ok.

When wimb and jfx co-operate, that'll be the day!!!

Attaboy! And also for any further improvements; don't forget, higher aims ahead, no matter whose aims!

Can we know the reason why it should stop here and now? Aren't there any more margins for improvement?

well, I do not know exactly what I did, but a concoction of shenanigan's version and memstechtips' standard version led me to adopt the following autounattended.xml. should anyone be interested in pruning and/or optimizing it, to the benefit of os vhd smallness and functionality after an a-priori purge, pls be my guest. as my knowledge of xml is almost inexistent, it is hard to expect any better than this from me, but I am willing to learn, still to the benefit of os smallness and functionality. autounattend.xml

Eureka! this is a list of folders I have discovered to be necessary for wifi functionality: \Windows\AppReadiness \Windows\bcastdvr \Windows\DigitalLocker \Windows\Logs \Windows\Offline Web Pages \Windows\Panther \Windows\Panther\setuperr.log \Windows\IdentityCRL \Windows\LanguageOverlayCache \Windows\Installer \Windows\L2Schemas so, if u want to keep wifi functional, do not brute-force delete and/or zerobyte them.

U sure U can't install it with winntsetup?

Attaboy! Just what it takes. Why don't we customize it to the way(s) that most suit one's liking?

hello again, good ol'wimb! long time no c. now pls tell us how to achieve the above: Add Drivers and Tweaks, Disable Windows Defender on existing Windows Installation and Windows_To_Go in VHD. could these things not be accomplished in the same way with the previous version of winntsetup?

well, first install with new version, everything went spick&span. Attaboy, jfx!

thanx jfx, I will try it out and let u know how it went.

or wait for next version to roll out, for that matter.

ok, but I still don't know what I gotta do to make the latest version behave as it should

So, what are we supposed to do to right these wrongs?

for atari, thank you ever so much for your answer, I do not mind weird people's attitudes, so I will cope with what u said of them, ... but, btw, why can't we have the same here as well? as for the strange dialogue with wd, I have not had it installed for ages, so I am not the one to give proper advice there. for jfx, win11 has 128, win 10 2015 has 16, what is the optimal size for loading the vhd into ram thru svbus, if there is one?

It is great to know we publicize what we do, in an atmosphere of sharing digital wellbeing. Just out of curiosity, do they have a section or group devoted to making windows smaller and running it on ram in MDL?