@MSMG, how's it going with the GUI version you talked about long time ago? Would be nice to have a freeware (with donation option) alternative to ntlite.
You can't confirm this, but - the practice of applying MSMG Toolkit confirms this. In addition, your list of removed components is small compared to what is needed. So, I am now making some changes to the MSMG 6.9. Desirable algorithm for eliminating errors: 1 - Removing components from an image without using any tweaks during this process (For components "Biometrics" and "Parental Controls" - "spy packages neutralization" only) 2 - Clearing the image from the remnants of the removed components (... Cleanup-Image /StartComponentCleanup /ResetBase) 3 - Search and delete empty folders in the Windows\SystemApps directory 4 - Search and delete from the context menu of the item "3D printing with 3D Builder", if available 5 - Add a registry value that fixes the "defaultuser0" problem 6 - .NET Framework 3.5 integration 7 - The updates integration 8 - Clean the "Windows\WinSxS\Backup" folder from the garbage, to reduce the size of the .wim file 9 - Unmounting and exporting an image (Importantly - no big wim file size!) Constructive criticism is welcome.
MSGM, thank you for this precious tool! testing 6.9 and i'm getting some dism errors removing (some) of the Hyper-V packx, had to remove then via wim_tweak maybe its just me but no big of a deal! i don't know if this is the right site to ask some of you gurus but since msgm has the option to do it here it goes: i know its possible to integrate unsigned drivers in an offline image, my question is: is there any way to integrate +install the unsigned inf in the first boot? thank you all guys, i'm quite a noob but a great enthusiast and thank god i found this forum! edit: Processing 1 of 1 - An error occurred - Microsoft-OneCore-HyperV-Hypervisor-Package Error: 0x80070005 Error: 5
Anyone else getting wait xx minutes for download to begin or give us money from Mega? Another one bites the dust, now just another sell out piece of crap. P.S. thanks for the other links. Thanks for the update, keep up the gr8 work. Regards
The Development of ToolKit GUI version is going fine with almost all functions of current command-line ToolKit have been implemented and also tested fine. The current GUI version can do : - List Source Images and Select and Load a Image for Servicing. - Enable/Disable Features - Integrate Drivers for Windows, Windows Boot, Windows Recovery Images. - Import HOST Drivers and Integrate the same to Windows, Windows Boot, Windows Recovery Images. - Integrate ToolKit Feature Packs. - Integrate Windows and Windows PE Language Packs provided by ToolKit Packs to Windows, Windows Boot, Windows Recovery Images. - Integrate Updates for Windows, Windows Boot, Windows Recovery Images (.MSU, .CAB, .EXE, .MLC). - Removes Microsoft Default Metro Apps. - Apply and Save Changes Made to Source Image with Export/Rebuild Image Option. - Apply and Disacrd Changes Made to Source Image with Debug Option Enabled. - Discard Changes Made to Source Image. - Make/Burn ISO Image. - Copy Source to USB. - Extract ISO Image. Only, few things like Settings, About, EULA, Custom Message Boxs are to be implemented and also need to fix few issues like : - When Enabling/Disabling Features in Features Tab, it Auto selects some Features under Windows 7 Source OS but for Windows 8.1/Windows 10 it's not having any issues. - ToolKit Status and Log Text strings needs to be corrected. Wait One/two days I will post a few updated screenshots of the ToolKit GUI version. The GUI version of ToolKit will be a freeware and not a paid one.
For, Windows 10 64-bit Source Os, If you had Integrated .NET Framework 3.5 prior to Components Removal then you get this errors, So do, Integrate .NET Framework 3.5 at last. The ToolKit does by default Integrates the drivers with force unsinged drivers switch but some but some drivers fails to install on first boot. Disabling the Driver Signature checking with the below command will do the job but you need to add the command to RunOnce registry entry. bcdedit /set testsigning on
The DISM method to remove Windows components will not remove all the associated files/entries from OS Image, even when /Cleanup-Image /StartComponentCleanup /ResetBase switch is used. We need to manually the remove left-out junk files from WinSxS folder and the Registry and it requires proper and careful method to remove the files/entries without breaking the OS. I have left it as it is, until a proper method is worked out and so the sfc /scanow will report for file corruption and restores the files from WinSXS.
Ok, now the start menu won't functioning with left mouse button. Right mouse works. And before the sfc method I saw the logon screen really short. Now it's hanging around there 20seconds. The kb4015438 (14393.969) try to install but after the reset windows is telling me that the update can't applied and the update will be undone. I started the sfc /scannow again but in my opinion it shows the same as before. After all I can try the new 6.9 toolkit @ MSMG Thanks for your answer. So I should just leave sfc and do nothing till you/we found a working method? And the same applies to: Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore Dism.exe /online /Cleanup-Image /StartComponentCleanup ?
Thank you I'll try it . But I think it is still strange that this problem occured after the sfc command.
Is there a way to keep search functionality but remove Cortana? Whenever I remove Cortana it prevents me from searching as well.
Actually it's only the Start Menu Search that is bundled with Cortana and therefor will be lost, Explorer Search should still work (at least it does for me and i have removed Cortana and Search Components).
I've just noticed that - thanks! Last question: anyone know if doing Windows Updates is alright after removing all the components? I'm on LTSB which supposedly gets no feature updates, so I wasn't certain. Mainly just hoping Windows Updates doesn't "bring back" components over time.
Hi All! I have no image at boot time. windows 10 x64 with the latest updates, and removed metro applications. Whats wrong?
You can update as you wish. Removed stuff doesn't come back. Only the OneDrive setup wants to run, by means of a reg key in wow6432 node. As the onedrive is removed it won't run, but after a new CU it will. As of now, I haven't found a way to stop onedrive completely. Cheers. Edit: Toolkit 6.9 works flawless on w10 x64 LTSB. No issues at all.