UX: Windows 11 legacy template for installation ...

%3CLINGO-SUB%20id%3D%22lingo-sub-2664051%22%20slang%3D%22en-US%22%3EUX%3A%20Windows%2011%20legacy%20template%20for%20installation%20...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2664051%22%20slang%3D%22en-US%22%3E%20%20%20%20%26nbsp%3B%20Windows%2011%20legacy%20template%20for%20installation%2C%20when%201st%20Phys%20storage%20is%20SDD128%20or%20256Gb%2C%20degrades%20rather%20quickly%20-%20ergo%20UE%20Solution%20to%20this%20to%20discuss%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CP%3EDear%20Reader%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20someone%20who%20installs%20Debian%20with%20all%20cross-compilers%20SDK's%20etc%20to%20aid%20development.%20I%20bought%20Windows%2010%20PRO%20for%20the%20advanced%20security%20protection%20and%20to%20have%20a%20full-blown%20UX%20with%20VM%20installed%20VS2022%20that%20has%20all%20the%20ju-ju%20from%20SDKs%20to%20Symbols%20to%20nuget%20completeness.%20HyperV%20allows%20this%20file%20drive%20to%20grow.%20What%20exponentially%20grows%20is%20the%20system%20disk%20that%20even%20MS%20products%20need%20a%20hard%20reference%20to%20the%20system(root%2C%20boot%2C%20recovery%2C%20UEFI)%2C%20We%2C%20the%20people%2C%20(users)%20are%20however%20asked%20to%20do%20disk%20management%20when%20the%201st%20drive%20also%20does%20paging%20is%20running%20exponentially%20full.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPeople%20that%20have%20multiple%20drives%20in%20raid%20array%20for%20speed%20are%20likely%20to%20use%20SATAN6gb%2Fs%20disks%2C%20not%20solid-state%20media.%20They%20would%20not%20be%20confronted%20with%20an%20app%20that%20allows%20for%20the%20movement%20of%20apps%20(to%20little%20use).%20Alright%20WSL-g%20can%20be%20exported%20and%20imported%20on%202nd%20media%20perhaps%20this%20is%20what%20Microsoft%20tries%20to%20prevent%20to%20keep%20all%20USERS%20files%20contained%20within%20that%20realm%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20needs%20to%20be%20done%20is%20canonize%20C%20as%20the%20central%20mount%20point%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eregardless%20of%20disk%2Fvolume%2F%20partitions%3A%20this%20is%20a%20proposal%20that%20has%20the%20least%20impact%3CBR%20%2F%3E%3CBR%20%2F%3EC%3A%20-%20system%20disk(OS-root%2C%20boot%2C%20recovery%20-UEFI%20)%20will%20be%20mounted%20as%20a%20member%20of%20%22C%22%20preferably%20the%20fastest%20storage%20media%2C%20such%20as%20solid-state%20ram.%20May%20ONLY%20be%20installed%20of%20the%20first%20%2F%20fastest%20storage%3C%2FP%3E%3CP%3EProgram%20data%2C%20Program%20Files%7BMachine_word%7D%2F%20will%20also%20be%20hard-mounted%20as%20'C%22%20BUT%2C%20should%20reside%20on%20different%20storage%2C%20not%20where%20C%3A%5CWINDOWS%20is%20happening%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EUSERS%2F%20will%20also%20be%20hard%20mapped%20to%20C.%20This%20directory%20may%20NEVER%20be%20installed%20on%20the%20same%20physical%20media%20that%20resides%20in%20the%20system%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20all%20boils%20down%20to%20what%20FS%2C%20disk%20(legacy%20reference)%20volume%2C%20the%20partition%20can%20be%20asserted%20to%20have%20this%20kind%20of%20setup%20headless%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20own%20an%20Asus%20Rog%20Strix%20with%20128Mb%20system%20en%201TB%20that%20now%20show%3C%2FP%3E%3CP%3EThis%20may%20not%20happen%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ED%3A%5CUSERS%5Cedwin%5Csource%5Crepos%3C%2FP%3E%3CP%3ED%3A%5CProgram%20Files(x86)%5CAMD64%5Csteinberg%5Cvanguard%2Cvst3%20(64%20bit)%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EDo%20Microsoft%20Developers%20and%20engineers%20agree%3F%20say%20yay%20or%20no%3C%2FP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Contributor

Windows 11 legacy template for installation, when 1st Phys storage is SDD128 or 256Gb, degrades rather quickly - ergo UE Solution to this to discuss:

Dear Reader,

 

I'm someone who installs Debian with all cross-compilers SDK's etc to aid development. I bought Windows 10 PRO for the advanced security protection and to have a full-blown UX with VM installed VS2022 that has all the ju-ju from SDKs to Symbols to nuget completeness. HyperV allows this file drive to grow. What exponentially grows is the system disk that even MS products need a hard reference to the system(root, boot, recovery, UEFI), We, the people, (users) are however asked to do disk management when the 1st drive also does paging is running exponentially full.

 

People that have multiple drives in raid array for speed are likely to use SATAN6gb/s disks, not solid-state media. They would not be confronted with an app that allows for the movement of apps (to little use). Alright WSL-g can be exported and imported on 2nd media perhaps this is what Microsoft tries to prevent to keep all USERS files contained within that realm

 

What needs to be done is canonize C as the central mount point,

 

regardless of disk/volume/ partitions: this is a proposal that has the least impact

C: - system disk(OS-root, boot, recovery -UEFI ) will be mounted as a member of "C" preferably the fastest storage media, such as solid-state ram. May ONLY be installed of the first / fastest storage

Program data, Program Files{Machine_word}/ will also be hard-mounted as 'C" BUT, should reside on different storage, not where C:\WINDOWS is happening


USERS/ will also be hard mapped to C. This directory may NEVER be installed on the same physical media that resides in the system

It all boils down to what FS, disk (legacy reference) volume, the partition can be asserted to have this kind of setup headless

 

I own an Asus Rog Strix with 128Mb system en 1TB that now show

This may not happen:

 

D:\USERS\edwin\source\repos

D:\Program Files(x86)\AMD64\steinberg\vanguard,vst3 (64 bit)


Do Microsoft Developers and engineers agree? say yay or no



0 Replies