1) It's the Y/N Confirmation message have got interchanged, that's it. 2) I have tested the recent SSU and CU with a Live OS installed with the ToolKit Created Image and it didn't give issues but if you had used NTLite also to service the image then it will give errors. NTLite gives a different method to Install the Updates where you require the preset you had earlier used to create the Image and it will checks the preset for removed components and uses it own function to install only the required updates from the CU. will test with the Image and report back.
Yes the Toolkit works for the SSU and CU from long back, it check for the update in an order and if it is found it will integrate them and move to the next update.
The Standard order should be Integrate Update and then remove Components but starting with Windows 10 the order has been kept changing due to it's very nature of changes in update. There are three different of users : 1) Who create a Image with the updates integrated, Components Removed and Customization done, installs the OS and don't update the system at all, when they find any issues with the OS then they do start with a fresh Image creation with the new updates integrated. 2) Who create a Master Image without any updates integration, with Components Removed and Customization done, when they find any issues with the OS or want to refresh, they do restore the OS using the Master Image and then update the latest update. But this method will be feasible only if the update don't restore the removed components or doesn't break the OS. One advantage of this method is that it will reduce the Component ResetBase time as there are no previous update. 3) Who create a Image with the updates integrated, with Components Removed and Customization done, installs the OS and keep updating the system often. This method also will be feasible only if the update don't restore the removed components or doesn't break the OS. One Dis-advantage of this method is that it will increase the Component ResetBase time due to various updates. So there's no specific method it changes according to the user and also the updates.
I think the problems are these big half-yearly Updates. Than we have to expect that some of the removed components are back and/or some things will be reset.
In response to 6 and 7, at this post, I am messing around with my copy of windows 8.1 again, and for whatever reason now, the problem I had before is not happening; its running as it should, extracting the contents, but it just said extraction failed, so I tried extracting the contents of my iso file myself, but 7zip is giving me a "Warning, there are some data after the end of the payload data"; I think there might be an extraction problem since I got toolkit in the C:\ drive instead of my desktop (username is The G-Nerd; toolkit doesn't like my name apparently ) and my copy of windows 8.1; will get a fresh copy and use that instead; unless the content I can extract is fine and I can ignore this 7zip warning instead, can I? Also, I did have to rename my iso file, because I guess ToolKit didn't like the name "Windows 8.1 Pro (64-Bit)", so I changed it to "Windows" instead; any chance of add-on integration in future toolkit updates, or is that a "nope, never happening" thing?
So now what is the consensus for the latest Windows 10 build? integrate .NET 3.5 then updates then remove components?
For bad iso or best iso? For the best iso: 1. remove components (valid (no mum test and repair manual)) 2. updates 3. resetbase 4. rebuilding (optimize) wim or create esd and no integrate net35 (unnecessary).
I say do not update until you get into the actual OS because even if you updated with MSMG Toolkit, it is recommended to to integrate NET Framework 3.5 as the last step (AFTER the update), which means Windows Update will re-download NET Framework-related material from the latest Cumulative Update. My suggestion is to do the following: 1. Integrate whatever you want, including NET Framework 3.5 2. Do NOT update anything 3. Remove whatever you want 4. Apply w/ ResetBase + Rebuild 5. Install OS, get into Audit mode as soon as it lets you (press SHIFT+F3 when the first questions during install pops up, right after HW is configured and system is restarted) 6A. Update OS properly (Servicing Stack first + CleanUp w/ ResetBase, restart, Cumulative Update + CleanUp w/ ResetBase) 6B. Run SFC ScanNow and DISM Scan/Restore Health to make sure everything passes with flying colors, but it is likely some removed content will be re-created (Windows Defender entry) may re-appear in Start Menu, but following Step 6C will clean it all up without a chance of re-appearing after future updates. 6C. ***OPTIONAL*** Install DB Browser for SQLite, launch it as Trusted-Installer with NSudo 4.4, navigate to App Repostory database files, set everything except for ShellExperienceHost, Immersive Control Panel, CloudExperienceHost, and whatever else you want to keep to "IsInbox=0", run PowerShell Get/Remove AppX's commands to get rid of that poop, find InboxApplication locations in Regedit, clean them up, including Config sub-keys (except for ShellExperienceHost, Immersive Control Panel, CloudExperienceHost, and whatever you want to keep), restart, uninstall DB Browser for SQLite. 7. Clean the rest of the registry with CCleaner + CCEnhancer + JV16 PowerTools - I suggest running each twice - once as Admin and once as Trusted-Installer using NSudo. 8. SysPrep + Generalize + Shutdown 9. Capture image with whatever tool (WIMLib-ImageX is the fastest AFAIK) 10. Have a nice day with a clean OS! Note: You can actually edit the "InboxApplication" part registry ahead of installing the OS and SysPrepping it, but in my experience, some of the deleted Inbox App's re-appeared after SFC ScanNow.
Just a few things that don't add up: Code: My suggestion is to do the following: 1. Integrate whatever you want, including NET Framework 3.5 2. Do NOT update anything 3. Remove whatever you want 4. Apply w/ ResetBase + Rebuild [Offline Enabling NET Framework 3.5 will set the pending flag, when the pending flag is set /resetbase won't be performed] 5. Install OS, get into Audit mode as soon as it lets you (press SHIFT+F3 when the first questions during install pops up, right after HW is configured and system is restarted) [entering AUDIT mode is achieved by pressing CTRL+SHIFT+F3] 6A. Update OS properly (Servicing Stack first + CleanUp w/ ResetBase, restart, Cumulative Update + CleanUp w/ ResetBase) [Why doing this in separate processes?] 6B. Run SFC ScanNow and DISM Scan/Restore Health to make sure everything passes with flying colors, but it is likely some removed content will be re-created (Windows Defender entry) may re-appear in Start Menu, but following Step 6C will clean it all up without a chance of re-appearing after future updates. [in the past I've experienced, the repair actions won't be saved to the captured install.wim] 6C. ***OPTIONAL*** Install DB Browser for SQLite, launch it as Trusted-Installer with NSudo 4.4, navigate to App Repostory database files, set everything except for ShellExperienceHost, Immersive Control Panel, CloudExperienceHost, and whatever else you want to keep to "IsInbox=0", run PowerShell Get/Remove AppX's commands to get rid of that poop, find InboxApplication locations in Regedit, clean them up, including Config sub-keys (except for ShellExperienceHost, Immersive Control Panel, CloudExperienceHost, and whatever you want to keep), restart. 7. Clean the rest of the registry with CCleaner + CCEnhancer + JV16 PowerTools - I suggest running each twice - once as Admin and once as Trusted-Installer using NSudo. 8. SysPrep + Generalize + Shutdown [You forgot to add to select "Shutdown system" and "enter OOBE"] 9. Capture image with whatever tool (WIMLib-ImageX is the fastest AFAIK) [You forgot to mention to boot using a winpe with the wimlib imagex files onboard, when performed on a real system or install it in a virtual environment, a VHD or in a dual boot situation with your main install] 10. Have a nice day with a clean OS! This all can be done in a virtual environment like VMWare. The /resetbase command can also be done after capturing the install.wim (you have to mount it). For more detailed information about AUDIT Mode/Sysprep/Capturing, go here: https://forums.mydigitallife.net/th...etupcomplete-firstlogon-silent-install.73131/ It also includes the capture exclusion lists by abbodi1406 plus the proper commands for using it with imagex, wimlib imagex and dism.
Thank you for correcting me! I actually integrate NET Framework 3.5 with NTLite at this point. I am not sure how the process of integrating it differs from the one MSMG Toolkit uses.
little mistake at 7.4 when you choice remove all apps it goes to remove all except store and viceversa. nothing serious
Windows 10 Pro x64 Version 1703 Build 15063.0 UPDATED TO Build 15063.413 Mount install.wim with ToolKit-v7.3, then it's PART 1 and then it's PART 2. Code: PART 1 ToolKit-v7.3 (commands i used). 4 - 1 - 2 4 - 1 - 3 4 - 2 4 - 3 - 1 4 - 3 - 2 - 1 4 - 3 - 2 - 2 4 - 3 - 2 - 3 4 - 3 - 2 - 4 4 - 3 - 2 - 5 4 - 3 - 2 - 6 4 - 3 - 2 - 7 4 - 3 - 2 - 8 4 - 3 - 2 - 9 PART 2 Command Prompt (commands i used). Dism /Image:D:\ToolKit-v7.3\Mount\Install /Remove-Package /PackageName:Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Dism /Image:D:\ToolKit-v7.3\Mount\Install /Remove-Package /PackageName:Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Dism /Image:D:\ToolKit-v7.3\Mount\Install /Remove-Package /PackageName:Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Dism /Image:D:\ToolKit-v7.3\Mount\Install /Cleanup-Image /StartComponentCleanup /ResetBase sfc /scannow /offbootdir=D:\ToolKit-v7.3\Mount\Install /offwindir=D:\ToolKit-v7.3\Mount\Install\windows Dism /Image:D:\ToolKit-v7.3\Mount\Install /Add-Package /PackagePath:D:\Microsoft-Windows-NetFx3-OnDemand-Package.cab Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:WCF-Services45 Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:MediaPlayback Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:Printing-PrintToPDFServices-Features Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:Printing-Foundation-Features Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:MSRDC-Infrastructure Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:SMB1Protocol Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:MicrosoftWindowsPowerShellV2Root Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:WorkFolders-Client Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:Printing-XPSServices-Features Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:Xps-Foundation-Xps-Viewer Dism /Image:D:\ToolKit-v7.3\Mount\Install /disable-feature /featurename:SearchEngine-Client-Package Dism /Image:D:\ToolKit-v7.3\Mount\Install /Add-Package /PackagePath:D:\windows10.0-kb4022405-x64_cb1286f2547dd21a06f1ec5b9a55769a7227b371.msu Dism /Image:D:\ToolKit-v7.3\Mount\Install /Add-Package /PackagePath:D:\windows10.0-kb4022725-x64_f4468667fb546204531ff9b88ef9b8b095a26786.msu Dism /Unmount-Wim /MountDir:D:\ToolKit-v7.3\Mount\Install /Commit Dism /Export-Image /SourceImageFile:D:\ToolKit-v7.3\DVD\sources\install.wim /SourceIndex:1 /DestinationImageFile:D:\install.wim /Compress:Max /CheckIntegrity Works for me.
so where do I get the other language packs for the creators update version of windows 10 if i want then integrated in? and this uxtheme integration option im seeing; I researched it and custom themes would be perfect for my custom install, but the possibility of future updates would be there to potentially break and FUBAR my installation, correct?
For Which Language do you need the LP? I had to remove the patched UxTheme files due to frequent changes in update but the option to Integrate the Patched is been provided, you need to copy the patched UxTheme files to the respective directories and then use the Integrate Custom UxTheme Patch Option. And, Yes if you update the system it will break the patch.