MSMG, is it possible in the Toolkit to manually adjust the compression ratio at your own discretion when converting WIM to ESD? It would be good for me to reduce it a little, since I do this work on a not too powerful PC. I tried it a long time ago, it loads the processor a lot, and it's a very long process. I usually did this in NTLite at the final stage, there in settings.xml the default value is set to: <WimCompression>2</WimCompression>, this is optimal for my PC. ____________________ The reason for many failures in the past... I can't help but thank you for your foresight! Spoiler: ConvertReg "[HKEY_LOCAL_MACHINE\SOFTWARE" = "[HKEY_LOCAL_MACHINE\TK_SOFTWARE"; "[-HKEY_LOCAL_MACHINE\SOFTWARE" = "[-HKEY_LOCAL_MACHINE\TK_SOFTWARE"; "[HKEY_CLASSES_ROOT" = "[HKEY_LOCAL_MACHINE\TK_SOFTWARE\Classes"; "[-HKEY_CLASSES_ROOT" = "[-HKEY_LOCAL_MACHINE\TK_SOFTWARE\Classes"; "[HKEY_LOCAL_MACHINE\SYSTEM" = "[HKEY_LOCAL_MACHINE\TK_SYSTEM"; "[-HKEY_LOCAL_MACHINE\SYSTEM" = "[-HKEY_LOCAL_MACHINE\TK_SYSTEM"; "[HKEY_LOCAL_MACHINE\TK_SYSTEM\CurrentControlSet\" = "[HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001\"; "[-HKEY_LOCAL_MACHINE\TK_SYSTEM\CurrentControlSet\" = "[-HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001\"; "[HKEY_CURRENT_USER" = "[HKEY_LOCAL_MACHINE\TK_NTUSER"; "[-HKEY_CURRENT_USER" = "[-HKEY_LOCAL_MACHINE\TK_NTUSER"; "[HKEY_USERS\.Default" = "[HKEY_LOCAL_MACHINE\TK_DEFAULT"; "[-HKEY_USERS\.Default" = "[-HKEY_LOCAL_MACHINE\TK_DEFAULT"}
The toolkit uses DISM for WIM<->ESD conversions and the available switches are fast max none recovery For WIM I do use the max and for ESD do use the recovery. I don't know what the NTLite uses internally, does it uses the DISM or the Wimlib-imagex for exporting the indexes.
@MSMG I have one question. It's safe to remove Registry hive leftovers? Files like this: Code: : For ntuser.dat Hive C:\Users\bou7a\NTUSER.DAT.LOG1 C:\Users\bou7a\NTUSER.DAT.LOG2 C:\Users\bou7a\NTUSER.DAT{53b39e88-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Users\bou7a\NTUSER.DAT{53b39e88-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Users\bou7a\NTUSER.DAT{53b39e88-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms : For BBI Hive C:\Windows\System32\config\BBI.LOG1 C:\Windows\System32\config\BBI.LOG2 C:\Windows\System32\config\BBI{53b39ea0-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\BBI{53b39ea0-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\BBI{53b39ea0-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms : For COMPONENTS Hive C:\Windows\System32\config\COMPONENTS.LOG1 C:\Windows\System32\config\COMPONENTS.LOG2 C:\Windows\System32\config\COMPONENTS{53b39e63-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\COMPONENTS{53b39e63-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\COMPONENTS{53b39e63-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms : For DEFAULT Hive C:\Windows\System32\config\DEFAULT.LOG1 C:\Windows\System32\config\DEFAULT.LOG2 C:\Windows\System32\config\DEFAULT{53b39e7c-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\DEFAULT{53b39e7c-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\DEFAULT{53b39e7c-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms :For DRIVERS Hive C:\Windows\System32\config\DRIVERS.LOG1 C:\Windows\System32\config\DRIVERS.LOG2 C:\Windows\System32\config\DRIVERS{53b39e70-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\DRIVERS{53b39e70-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\DRIVERS{53b39e70-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms : For ELAM Hive C:\Windows\System32\config\ELAM.LOG1 C:\Windows\System32\config\ELAM.LOG2 : For SAM Hive C:\Windows\System32\config\SAM.LOG1 C:\Windows\System32\config\SAM.LOG2 C:\Windows\System32\config\SAM{53b39e57-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\SAM{53b39e57-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\SAM{53b39e57-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms : For SECURITY Hive C:\Windows\System32\config\SECURITY.LOG1 C:\Windows\System32\config\SECURITY.LOG2 C:\Windows\System32\config\SECURITY{53b39e4b-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\SECURITY{53b39e4b-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\SECURITY{53b39e4b-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms : For SOFTWARE Hive C:\Windows\System32\config\SOFTWARE.LOG1 C:\Windows\System32\config\SOFTWARE.LOG2 C:\Windows\System32\config\SOFTWARE{53b39e2f-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\SOFTWARE{53b39e2f-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\SOFTWARE{53b39e2f-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms : For SYSTEM Hive C:\Windows\System32\config\SYSTEM.LOG1 C:\Windows\System32\config\SYSTEM.LOG2 C:\Windows\System32\config\SYSTEM{53b39e3e-18c4-11ea-a811-000d3aa4692b}.TM.blf C:\Windows\System32\config\SYSTEM{53b39e3e-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000001.regtrans-ms C:\Windows\System32\config\SYSTEM{53b39e3e-18c4-11ea-a811-000d3aa4692b}.TMContainer00000000000000000002.regtrans-ms It's possible to remove these files or it's danger in remove. Thanks Advance. sorry for my bad English, I'm using google translate
Hello, @MSMG Here some mistakes typo: In line 11357 : Code: goto :IntDaRTBoot This labeled section is not found in Toolkit.cmd In line 18770 : Code: Code: if exist "%BootMount%\%%i\Windows\WinSxS\Backup\*.*" del /f /q "%InstallMount%\Windows\WinSxS\Backup\*.*" >nul 2>&1 Should be: Code: if exist "%BootMount%\%%i\Windows\WinSxS\Backup\*.*" del /f /q "%BootMount%\%%i\Windows\WinSxS\Backup\*.*" >nul 2>&1 In line 21166 : Code: Code: ImageIndexNo=Enter the WIM Image Index # ['Q'uit] : Should be: Code: set /p ImageIndexNo=Enter the WIM Image Index # ['Q'uit] : sorry for my bad English, I'm using google translate
By updates, do you mean any updates under the Windows Update section (like definition updates, .NET updates, monthly cumulative updates etc.) or only the major feature updates (like 1809, 2004, 2009)?
May be is not a bad idea include this into the cleanup scenario as a additional (hidden) step(s) that help to produce an image more clean? I beleive all such cleanings should help to reduce "user fingerprint" and improve privacy a little bit (do not save such data on disk forever for M$). I like every smallest step that help us to survive in the era of privacy leaks.
I was thinking we could make a separate open script that deals with empty folders and obsolete files for cleanup
Well, why not? But I thought about non-urgent collecting of the most sensitive cleanups with time flow inside the bundle (as a solid/approved/safe part of the bundle). 1. The most important thing for me is that all such initiatives must be approved by our own expert - @MSMG. Here I trust his decision: is it a good idea to make such edits for the image or not. Do not brake things - is a priority. Also I don't want to bother @MSMG unnecessarily, because he busy within much more important things (I'm expecting a new cool things in the near future). 2. I have my own CMD (still W.I.P.) for cleaning AFTER Windows installation. But I'm not an expert in prepearing of images. So, here I fully rely on our favorite bundle and his creator.
With Windows v1903 and above the Microsoft introduced a new update package format which will restore the removed components upon updating the system. Almost all components do get restored either in full or part, only Windows Apps are not affected since it gets updated through store. Window Store and Xbox which have backend files do get restored by Cumulative update.
