I believe that you should take a look at what I did with the app suggestions. [10] (+)Custom Disable Automatically Installation for PreSuggested 3RD Party Apps [11] (+)Set CloudContent for 3RD Party Apps and DataCollection - Policies Try to do a test by applying these settings, do a test ISO. I encourage you to test by applying the personal selection that I have made available "[P] PreSet Custom Tweaks Selection", it will apply these details. Look for this within the CustomToolkit script: if "!T_CustomDisableAutomaticallyInstallationforPreSuggested3RDPartyApps!" equ "+" To see what the changes are. You know that sometimes the translations seem a little harsh, hehehe. Sorry if any expression seemed a little stiff.
I thought @MSMG fixed a keyboard/mouse issue with losting log-info from the screens after pressing anykey. After all those UI changes he made... Important logs were losted again just after simple mouse Right-Click. If it's an MS-DOS environment issue, then it would be reasonable to write log-files on every important stage, not only for Update scenario. I.e. for "Disable Windows Features", "Remove Windows Components", etc.
1) UPD: "Setup Media" *.cab integration is OK 2) DisableFeaturesList - Errors | UPD: Tested 2 times on LTSC build 316 Spoiler: Error: 0x800f080c Code: Deployment Image Servicing and Management tool Version: 10.0.20279.1 Image Version: 10.0.17763.1823 Error: 0x800f080c Feature name <...> is unknown. A Windows feature name was not recognized. Use the /Get-Features option to find the name of the feature in the image and try the command again. The DISM log file can be found at D:\MSMG\Logs\Dism.txt Error affects on some apps, I don't know why only these particular components are affected: Spoiler: Affected Features Windows-Defender-Default-Definitions WCF-Services45 WCF-HTTP-Activation45 WCF-TCP-Activation45 WCF-Pipe-Activation45 WCF-MSMQ-Activation45 WCF-TCP-PortSharing45 WCF-HTTP-Activation WCF-NonHTTP-Activation NetFx3 MediaPlayback WindowsMediaPlayer Client-DeviceLockdown Client-EmbeddedShellLauncher Client-EmbeddedBootExp Client-EmbeddedLogon Client-KeyboardFilter Client-UnifiedWriteFilter Windows-Defender-ApplicationGuard MultiPoint-Connector MultiPoint-Connector-Services MultiPoint-Tools AppServerClient Internet-Explorer-Optional-amd64 -------------- Windows 10 Enterprise LTSC 2019 (1809) build 17763.316 (March 2019) ru_windows_10_enterprise_ltsc_2019_x64_dvd_78e7853a.iso SHA-1 : 5acb51472bb4380614c9c32ff354f0cc697c03f8 MD5 : FDBBC0AFD2952010C2A05C87298021E8
UPD: "Setup Media" *.cab integration is OK DU for sources (Setup Media) - Path for *.cab : ...\WHD\w10\x64\10.0.17763\ Spoiler: DU for sources - Integration Log Code: =============================================================================== MSMG ToolKit - Update Windows Setup Media =============================================================================== ------------------------------------------------------------------------------- ####Starting Updating Windows Setup Media###################################### ------------------------------------------------------------------------------- Getting Windows Setup Media Language Settings... Found Windows Setup Media Language : [ru-RU] Copying Windows Setup Media Update files to <DVD> folder... ------------------------------------------------------------------------------- ####Finished Updating Windows Setup Media###################################### ------------------------------------------------------------------------------- =============================================================================== ------------- @MSMG : I'm still don't like "Setup Media" naming. This confusing name still alive (i.e. inside the menu)... See my previous post : My suggestions / questions, Chapter 1 "Dynamic Update for Sources" is a far better, isn't it?
Now Mail.ru Cloud closed access for TOR (Lie: "Your browser is obsolete"). From now I have no access to any MSMG repo. Great. Great corps world in real deal. UPD: GDrive start working for me in some case. The last one.
Does MSMG v11.4 support LTSC build 316 ? (March 2019) I can't understand where these DisableFeaturesList errors come from. Has anyone ever noticed such errors (0x800f080c) in v11.4?
It seems that you have already removed in the previous step the components whose functions you are now trying to disable , so you get an error because they were not found. For example, if you removed DeviceLockdown and now try to disable these individual functions of it: Client-DeviceLockdown Client-EmbeddedShellLauncher Client-EmbeddedBootExp Client-EmbeddedLogon Client-KeyboardFilter Client-UnifiedWriteFilter The same will happen if you removed WindowsDefender, in now try to disable Windows-Defender-Default-Definitions The same is true if you deleted the MultiPointConnector in the previous step, and you are now trying to disable it: MultiPoint-Connector MultiPoint-Connector-Services MultiPoint-Tools In the case of an attempt to disable "NetFx3" - For starters should be integrated .Net 3.5, and it will (if only) be integrated by you in the final stage. Etc..
@graver.x Probably you are right. But then it's a broken logic in the MSMG (menu order or more)... If so, the bundle should not show "ERROR", but smth. like: "The package is already deleted". Or even better show nothing (skip logging) in this case. In case the Disable Features List is a slow option itself to compute, the Toolkit processes the data twice (for removing + for disabling nonexistent data). That is not good for the performance. Do you agree? And scary ERROR is not what expect a user. And README don't have a description at which step you should really proceed with Disable Features List option. I'll try proceed with Disabling Features before Apps Removing. Let's see the changes... UPD: Errors still appeared (Remove Apps option even didn't touched). But list has become much shorter: Code: Client-EmbeddedBootExp Client-EmbeddedLogon Client-KeyboardFilter Client-UnifiedWriteFilter AppServerClient I'm really confused, what's goin on?
Hi I used v11.4 with this version after extract the ISO 19043.867.210305-1751.21h1_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_ar-sa_7B726B5D3CF791B7011AAFCD194E4B947F9E53FF.esd very stable and fast work thanks to you
Yes, of course. I also have a big unfinished project for live OS reconfiguration. It's a hard thing, I understand pretty well what are you talking about. 1) I want to say, I'm not focused on removing of Features, just disabling is completely enough for me (for now). This mean that disabled component is completely deactivated (non-existing like). The best example is IE. I think we have much more work with removing System Apps and a huge amount of unwanted things in live OS. 2) Most of Features to disable are represented inside Windows here : Control panel -> Programs -> Turn Windows features on or off There we have much more disabled components by default, then a "short list" I've got in the last test. So I can't tie "errors" and "disabled by default" together. Anyway I need: - only .NET 4.8 (to integrate/update), that's why I copy-paste the whole template and exclude only these two (.NET): Code: NetFx4-AdvSrvs Microsoft-Windows-NetFx4-US-OC-Package I've decided to do like this, because (IMO) integration of .NET 4.8 is like an "update" from built-in .NET 4.7 (LTSC). Or, I'm afraid, correct integration may fail. - be sure that everything else is disabled This required just before removing ( you are already match just after [4] Windows Updates ). The question is about source - whether build 316 is compatible with MSMG. LTSC build 316 - is the last official distributive version redone by M$ itself, isn't it? Please, correct me. P.S. Thanks a lot for your comprehensive answer, friend!
According to the order of action described in README, Customize the Image using the "Customize" menu, one of the options of which is to disable functions with the User List, is made after the integration of all updates and removal of components. Spoiler (G) - Select the Components to be removed using [Remove->Remove Windows Components->Select Windows Components] menu. Note: Only for Client Editions. Requires Cumulative Update specified in the changelog.txt to be integrated before the removal. (H) - Remove the selected Windows Components using [Remove->Remove Windows Components-> Start Removing Windows Components] menu. Note: Only for Client Editions. Requires Cumulative Update specified in the changelog.txt to be integrated before the removal. (I)- <Optional> Integrate the required Windows Custom Features using [Integrate->Windows Custom Features] menu. (J) - <Optional> Customize the Image using [Customize] menu. On this basis, I believe that support for the original image 17763.316 should not be considered as a priority issue. I believe disabling functions should be performed after the removal of components, and this will already build 17763.1817 And if we discuss the choice of source for the subsequent integration of updates, I think it is better to choose for this purpose the starting number of the service package for a specific release win10, in this case - 17763.1 I think this should be done at least because after the integration of the last CU, there will be fewer versions of the superseded components in your image. If I am wrong, let MSMG and our experienced colleagues correct me.
@graver.x I beleive, the suggested answers by @MSMG will be close to the next: - You can ignore these error log-messages - The order of disabling Features (before vs after App removing) does not affect the health of the final image. Let's see. But I don't like these confusing messages anyway
It also seems to me that nothing terrible will happen as a result of these errors. And this is the most important thing in our business. Hopefully, MSMG will soon resolve our perplexities.
hey all, so I am trying to get a list of all components from toolkit_helper.exe I have typed in the folowing, c:\t\bin\ToolKitHelper.exe c:\mount\ component_list.txt that should dump a list of components to the file, the file has nuthing in it, I used c:\mount\ as the location of the mounted image. could someone tell me what I need to correct to have a complete list from toolkit helper? note, I am blind so no images. Majid
Hello, well I only use the Toolkit v10.1 with the W10 LTSC from its release and never had the slightest problem I can say with absolute certainty ...
@Tiger-1 In older versions I didn't noticed critical messages also. Well, that's why it's so strange. And I beleive in progress done by @MSMG. I beleive in progress in future versions (when SysApps removal will become available). Despite of some roughness.