Right now v1809 (x86+x64) and v1903 (x86) components removal have been tested and are working properly. Couldn't install v1903 (x64) image, don't know whether it's the VM problem or the component removal, needs to be further tested. And, also the Toolkit Pack files SHA-1 hashing has to be done and uploaded.
Yes it's v19H1 and not RS6, I was just replying to some user who was confused with the old pack file names. The new pack structure doesn't use TH1, TH2, RS1, RS2, RS3, RS4, RS5, RS6 anymore. When an update is added to the base image some files, registry keys, Tasks GUID do change which wont be removed by the Toolkit and this may give more errors when further updating.
so you saying that apps can be removed on toolkit. but finished 1903 x64 image wont install.? if it cant be used. where ca i get 1809 isos straight from MS.?
Hi everyone. I am using Windows 10 LTSC 2019 x86 in VMWare so that I can connect to a free Wifi Hotspot using multiple USB Wifi adaptors. The problem is the hotspot employs a SMS OTP-based login page and I must have removed some component(s) that is necessary for it to work as msftconnect.com/redirect no longer leads to the Wifi login page. It just brings up MSN.com. Untouched LTSC works fine. Is there any specific component that needs to be preserved? Thanks.
Hello, I got a error toolkit cant find boot.win file. Windows RS5 1809 ISO downloaded from Techbench , Toolkit version 8.8 . The ISO has the Boot.wim and Install.wim. Didnt have to convert it from ESD to WIm
I extracted the contents of the ISO to DVD folder, and I can find the files manually but Toolkit cannot find them
Still need to find out whether the issue is due to the component removal or the VM since even before with v1809 x64 builds I had issues with the installation in VM and lately it got solved.
IIRC I had removed IE as I thought Chrome/FF should be enough. I will try again and post the list of components I had removed later. I am not visiting the hotspot for over a week anyway. Thanks for your work.
@MSMG will there be custom .reg file importing ? I ask because currently it can be done via .tpk in Packs folder, but as i inspected for example Games pack, it had its registry paths altered to accomodate toolkit's mounting process (ie it had TK_DEFAULT, TK_SOFTWARE etc...). Will there be a feature to add plain .reg files whose keys toolkit will try to resolve to its internal format (ie HKEY_CURRENT_USER to TK_DEFAULT, HKEY_LOCAL_MACHINE\Software to TK_SOFTWARE etc). I ofcourse do not expect it to resolve ALL cases, just these carefully preprocessed files, it is IMHO responsibility of the .reg creator to convert all "HKEY_USERS\S-1-5-xxxx" to proper "HKEY_CURRENT_USER" or "HKEY_USERS\.DEFAULT" format. I figured out how toolkit performs these actions and i could "hack" into wim myself while toolkit is running so it commits my custom .reg into .wim, but i'd rather have this in clean and organized fashion.
You can simply do changes to the registry file reg hive mount paths to reflect the Toolkit's registry mount paths and then use the : - Toolkit's Tools->Options->Mount Image Registry Menu to mount the image registry - Double Click on Registry file to import the settings - Toolkit's Tools->Options->UnMount Image Registry Menuto un-mount the image registry Before I had thought of adding the option to Import the registry settings within the Toolkit but had issues with modifying the Registry mount paths in the registry file using the limited dos bath scripting. Will write a small tool in c# to automate renaming the Registry mount paths and use the tool within the Toolkit to import custom registry settings.
Earlier problem with W10 v1903 (x64) install on VMware was due to a bug which made the W10 v1903 (x64) install get hung at the Windows Logo and the solution was to either integrate an update issued by the MS or to disable the Virtualize IOMMU inside VMWare. I disabled Virtualize IOMMU inside VMWare and the W10 v1903 (x64) got installed properly, Now the component removal for v1809 (x86+x64) and v1903 (x86+x64) is working as expected.
Tried Version 9.3.2 and 8.8, Both versions of toolkit cannot find Boot.wim file in sources DVD, but I could manually locate them in toolkit>Sources> DVD. Tried running toolkit as adminstrator but dint work.
