I previously used NLite back in windows 8, as that os was problematic I opted to stay back with win 7 for many years till some programs working with it became too clunky. After much testing with win 10 I changed to this a few years ago & hacked the hell outta it until it was to my liking. If I chose to start using Nlite with Win 11 along with SlimDown what is the best order of application? This may be help full to newbies too? Perhaps a short guide on this please guys?
If I understand correctly, you are asking about the order of the operation. 1. "24H2_Integrator_10.2\CreateSlim.cmd" 2.NTLite 3.Pc
Have read the 10.2 readme doc. Following processing of the SD script I then open the image in NLite what further can be removed to de bloat the wim?
First, set it up according to your needs. "Win11_26100_NTLite_Ayar.txt" make it "Win11_26100_NTLite_Ayar.xml" and use it in ''NTLite''
I don't know if it has been spoken before, but the iso file I created with 24H2_INTEGATOR_10.2 is a smooth installation on the virtual machine and great result. But when installing it in the real system, it does not see the discs during the first installation phase. I was only able to install by throwing the install.wim file into 23H2 iso.
Sorun olmamalı. Gelecekte yine sorun olduğunda, 23h2'deki boot.wim dosyasını alıp 24h2'deki boot.wim dosyasıyla değiştirin. There should be no problem. In the future when the problem occurs again, take the boot.wim file from 23h2 and replace it with the boot.wim file from 24h2.
I have already written about it, I will write again, for those who read only the last page of this topic. The whole point is that you modify the boot.wim file with this script. Well, you don't need to do it, it's not a necessary action. Leave it alone and you will be happy. If you are so itching to modify the boot.wim file, it would be much more interesting to write a script that would remove the little needed index 1 from the boot.wim image and leave only boot index 2 in it ! Besides, such actions would reduce the size of the boot.wim file at least twofold. But so far I don't see anyone willing to raise this very interesting topic ...
==================== 24H2_Integrator_10.4 ==================== Updated to version 26100.3775 https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-120#post-1872013
How good it is that there are such enthusiasts as you, SunLion! You spare neither your efforts nor your time to develop such masterpieces as the Integrator. With all my heart - God bless you with health and all the best!!!
Question for the audience: Can anyone tell me how to open this registry branch? - HKEY_CLASSES_ROOT To add it here in - Mount Image Registry ??? Spoiler Code: echo. echo. echo. ECHO ============================================================ ECHO Mount Image Registry ECHO ============================================================ reg load HKLM\TK_DEFAULT "%~dp0mount\Windows\System32\config\DEFAULT" reg load HKLM\TK_NTUSER "%~dp0mount\Users\Default\NTUSER.DAT" reg load HKLM\TK_SOFTWARE "%~dp0mount\Windows\System32\config\SOFTWARE" reg load HKLM\TK_SYSTEM "%~dp0mount\Windows\System32\config\SYSTEM"
If HKCR doesn't work, remember that it is only a shortcut of the following key: Code: HKEY_LOCAL_MACHINE\SOFTWARE\Classes So, you can always use HKLM\SOFTWARE\Classes to address it.
Got it, thanks a lot for the hint! If I understood you correctly, then the code I'm interested in should look something like this: Spoiler Code: ::Removing the Indexing Options applet "%~dp0tools\%HostArchitecture%\NSudo.exe" -U:T -P:E -UseCurrentConsole -Wait reg delete "HKLM\TK_SOFTWARE\Classes\CLSID\{87D66A43-7B11-4A28-9811-C86EE395ACF7}" /f "%~dp0tools\%HostArchitecture%\NSudo.exe" -U:T -P:E -UseCurrentConsole -Wait reg delete "HKLM\TK_SOFTWARE\Classes\Wow6432Node\CLSID\{87D66A43-7B11-4A28-9811-C86EE395ACF7}" /f "%~dp0tools\%HostArchitecture%\NSudo.exe" -U:T -P:E -UseCurrentConsole -Wait reg delete "HKLM\TK_SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{87D66A43-7B11-4A28-9811-C86EE395ACF7}" /f "%~dp0tools\%HostArchitecture%\NSudo.exe" -U:T -P:E -UseCurrentConsole -Wait reg delete "HKLM\TK_SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{87D66A43-7B11-4A28-9811-C86EE395ACF7}" /f That is, we do not substitute the ROOT value in our code ? Frankly speaking, I am not very good at programming. That is why I have questions that may seem funny to some.