There will be one on/before New Year, Right now I have fixed issues with LP integration, added Braille + Open SSH + Windows Portable Devices Integration, Will be fixing issues related to Apps + updates integration and components removal.
Why do you want it when it's present within the OS, did you by chance removed it? You can get it from FOD or extract it from the image/live system using SxSExpander.
Sir, do i need to follow the aforesaid procedure for Windows 8.1 also ? And please let me know the functionality of the Re-build Source images option. So far this option has escaped my attention and i have been creating the ISO directly after apply & save changes to source images option. And if i want to convert the install.wim to install.esd, i should do it after performing Re-build source images function or before that ? Thanx
would say you should do that after applying and rebuilding! @jinvidia i'm qiet confident i did it at least best so far.. latest toolkithelper worked with zero errors. kicked off with nsudo TI full privileged as you suggested. i have an image of octobre update now only 3.8GB in size (wim - not esd). even if i had to realize what i got after destroying the old intel motherboard because of vpro, me crap blabla - an amd board with a broadcom wlan device hidden in it's platform security processor. great deal!.. will install the iso in a SVM right now. hopefully this is the golden one for next months ;-)
No it's only for Windows 10 RS5, for W81 follow the steps specified in Readme.txt. Re-Build Source Image : When you modify the image, the DISM keeps the removed items in a separate temporary folder or image container and thus the size of the image gets increased, Rebuilding the source images will export the source image to a new image which will remove these temporary thing and thus reduces the overall image size. WIM->ESD should be done after rebuilding the image.
i removed everything exept ceip, wer, putin, cortana (just disabled), photoviewer, compat, diagtrackrunner.. appraiser installed without error. for remaining continues i will remove sysrestore function also whenever possible so it can't be abused by microslop. it is perfectly missing in the menu where it has been so far. defender is the most annoying crapware in winblows for me, i accept some try and errors for getting rid of it. thanks again for working on your project!! the slight difficulty to use tools like nsudo and follow steps precisely and risk of next try after hours is worth it! removing the crap before using is the best option to make the junkware winblows partially usable i think. how many weeks of time have you invested in it so far?!
Thank you very much sir. Actually i have some images sitting in my pc without doing the rebuild part but I have converted their install.wim to install.esd and they have been working fine till now. Anyway I will re-create them with your method. I have created 2 esd isos, one without applying the rebuild option and the other applying the rebuild option and I dont see any size difference except a few bytes. Is the rebuild option mandatory even if I am opting for the esd format ? By the way I have applied the aforesaid procedure for a win8.1 image and created a customized iso. Will there be any issue if I use this iso to install win 8.1 ?
I have a toolkit related question. Has anyone here upgraded a highly MSMG toolkit modified RS4 install to RS5? If so, did anything break? Did stuff you removed come back to life? Did new RS5 additions show up?
Sorry, is there any support for other languages in the next version or is there still a problem with that?
Apparently Integrating this regfile into wim via NTLite prevents WU from downloading Adobe Flash updates on "SW_DVD5_WIN_ENT_LTSC_2019_64-bit_English_MLF_X21-96425.iso". Therefore no flash reinstall on updates. Captured on LTSB'16 where DISM removal of flash prevents updates from popping up. Keys are different on different versions. Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_adobe-flash-for-windows_31bf3856ad364e35_none_be6c45d34d324e9a] @=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_adobe-flash-for-windows_31bf3856ad364e35_none_be6c45d34d324e9a\10.0] "10.0.17763.1"=- @=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_adobe-flash-for-windows_31bf3856ad364e35_none_b4179b8118d18c9f] @=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_adobe-flash-for-windows_31bf3856ad364e35_none_b4179b8118d18c9f\10.0] "10.0.17763.1"=- @=-
wow. i installed winblows with the new iso and it works absolutely fantastic. winblows don't let me copy the image to usb.. everytime an unexpected error appears ^^ YEAEE! (of course i hashed and burned the image immediately after creating) eat this microslop! i will beat every best_of's in fastbooting ;-) also i created a complete image of the system in just 30 seconds (15GB/s) with my favourite tool, it was never faster! i'm confident it is thegolden one now! thank you again! i'm happy!