Ok lads, maybe not needed but I've just baked myself two LTSB images (x86 and x64) with the latest updates and some stuff removed. Toolkit 8.6 works fine, no issues at all. Cheers.
I have separated the Smartscreen and WindowsDefender component removal in ToolKit, the WindowsDefender doesn't remove anything related to Smartscreen instead it only removes the defender components where all it is used like Hyper-V May be something else have gone wrong, will checkout.
MSMG ToolKit v8.6 Great tool! Thanks to MDL Member Phoenix for the video tutorial. Now I got a nice slimmed down Windows 10 64 for my new i5 gaming rig. Good stuff guys!
Problem is next. After saving the install.wim content: [DELETED] <--? size 640.814.907 byte Program Files ProgramFiles (x86) ProgramData etc..... And DVD\sources\boot.wim content 74.111 byte [DELETED] 1 2 1.xml Install.wim: File size before saving: 2,97 GB I just removed it File size after saving: 3,44 GB logs file.. ... .. None Pass (Administrator Rights) The image: 1803.17134.1 hu_HU and, or: 1803.17134.48 hu_HU
Hi MSMG I'm curious about what the word ASIMOV means inside the M $ Telemetry item after CEIP and I have yet to inform you that after doing my work with Toolkit V8.6 it is wrapped using 17134.1.180410-1804.RS4_Release_ClientEnterprise_vol_x64fre to ISO result has obtained a size of only 2.9GB just removing unnecessary applications and in the end I always check the log and to my surprise there is NO log to check what characterizes that there were no errors; this way I just have to thank you for your excellent work one more time, really thank you for allowing us Windows users to have a better OS
Fix for cannot change feedback frequency - is greyout Windows 10 v1803 regedit HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate "ManagePreviewBuilds" = dword:00000001 "ManagePreviewBuildsPolicyValue" = dword:00000001 and after that you can disable feedback frequency
Another question: the program always prompts for the boot.wim file if it is not in the "DVD\sources folder" is it important?
Pretty much what I expected. I have run into issues with RS3 + CU + all drivers from a system sending the WIM over the FAT32 limit so I started using ESD in all cases a while back.
yeah i hope they delete the requirement of boot.wim being present it's not need unless you add a language pack i always put it there in sources folder just for the toolkit to work but i ignore it afterwards i only replace install.wim in the iso file another thing so i removed hyper-v packages but still i can create and attach VHD in computer management; so what's all this hyper-v is about, i thought it's for virtualisation only i hope it's not required for anything crucial for windows or any programs