I need another help guys! Please help me! I looking for a NetFX472_W10.7z (.cab files) for LTSB to integrate via MSMG Toolkit! I found only NetFX 35 and 48 repository! Can someone send a link please. Thank in advance
Thank you very much! I found. To many content here! I checked mega but not mirrors! My head almost exploded! Thanks, you saved my time!
@MSMG Please add to the new version of the program the ability to disable Windows Insider Program Page.
MSMG: sorry to waste your time, my issue was more with the SSD it seems a new ssd got killed when i used an m.2 adapter. something i least expected to happen. updated: if anyone cares, i cant get into windows (tested with rs4 & 1903) on adata sx8200pro 512gb, 1gb. wondering if its a driver issue. testing further... update2: turns out its one of the integrated drivers causing the infinite circle and only on this ssd for some reason its either: amd chipset ; intel chipset ; intel sata ; amd sata ; amd nvme i didnt include any of them this time,. this has me hating microsoft more than ever now. theres no use for a spinning circle, it tells nothing. in linux i'd immediately know whats up. update3: so to finalize, adata sx8200pro + integrated amd|nvme drivers on an intel machine dont play well. its not clear why amd nvme drivers were even used instead of intel ones. always microsoft things.
how to add language pack in windows 10 19h1, i cant see download link?? or can other method to add language pack??
Hi, I'm trying to remove components (mainly Defender) in LTSC 17763.104 (earliest ISO I can find) however MSMG is telling me that the only build it supports is 17763.1. Does this mean, like the 1903 build, if I remove components from LTSC 17763.1 they will return when Windows updates are installed?
The pack folder has been temporarily moved due to re-structuring of the pack files and once the process is completed it will be restored back. Will try to release a small update to support the new pack folder structure.
No it's only for v1903 the removed components gets restored and so far for 17763.1 no one has reported anything about any component getting restored.
Using Toolkit with images with updates for integration/customization should not be problem, If you are integrating the CU to the boot.wim then you need to also use the Integrate Windows Setup Media Updates which will copy the updated setup files from boot.wim index 2 to source DVD folder. The process goes like this: Integrating Windows WHD General Updates to Boot Image will integrate the files present in from ServicingStack, Cumulative and any updates present inside WinPE and SetupMedia folders. Though the Standalone update file copied to SetupMedia folder does contain the updated setup files for the sources folder but it may not always or won't have a updated setup.exe matching the one integrated to the boot.wim index 2 and due to this the Load driver error dialog appears during the setup. To fix this you need to use the Integrate Windows Setup Media Updates which will copy the updated setup files from boot.wim index 2 to source DVD folder. Will checkout the image with latest update before releasing the next version to see if it needs any fix.
Thank you again, @MSMG - I won't pretend to fully understand what you have said, but integrating setup media updates does indeed seem to resolve my problem.
I did address that issue after enthousiast pointed out what was going on, you probably didn't see that. The toolkit works and worked as designed and creates a working iso IF you use integrate windows setup media updates and you had mounted the boot.wim. Cheers.