@f0ness, Spoiler: Toolkit Disable and Enable Features: Code: ::------------------------------------------------------------------------------------------- :: Function to enable a feature inside a Image :: Input Parameters [ %~1 : Image Mount Path, %~2 : Feature Name ] ::------------------------------------------------------------------------------------------- :EnableFeature %DISM% /Image:%~1 /Enable-Feature /FeatureName:%~2 echo. goto :eof ::------------------------------------------------------------------------------------------- ::------------------------------------------------------------------------------------------- :: Function to disable a feature inside a Image :: Input Parameters [ %~1 : Image Mount Path, %~2 : Feature Name ] ::------------------------------------------------------------------------------------------- :DisableFeature %DISM% /Image:%~1 /Disable-Feature /FeatureName:%~2 echo. goto :eof ::------------------------------------------------------------------------------------------- Spoiler: With the Changes Disable and Enable Features will be like this: Code: ::------------------------------------------------------------------------------------------- :: Function to disable a feature inside a Image :: Input Parameters [ %~1 : Image Mount Path, %~2 : Feature Name ] ::------------------------------------------------------------------------------------------- :DisableFeature %DISM% /Image:"%~1" /Get-FeatureInfo /FeatureName:%~2 | findstr /c:"State : Disabled" >nul if "!ErrorLevel!" equ "0" ( echo.------------------------------------------------------------------------------- echo.Windows Feature - [%~2] is already disabled. echo.------------------------------------------------------------------------------- ) else ( echo.------------------------------------------------------------------------------- echo.Disabling Windows Feature - [%~2]... echo.------------------------------------------------------------------------------- %DISM% /Image:"%~1" /Disable-Feature /FeatureName:%~2 ) echo. echo. goto :EOF ::------------------------------------------------------------------------------------------- ::------------------------------------------------------------------------------------------- :: Function to enable a feature inside a Image :: Input Parameters [ %~1 : Image Mount Path, %~2 : Feature Name ] ::------------------------------------------------------------------------------------------- :EnableFeature %DISM% /Image:"%~1" /Get-FeatureInfo /FeatureName:%~2 | findstr /c:"State : Enabled" >nul if "!ErrorLevel!" equ "0" ( echo.------------------------------------------------------------------------------- echo.Windows Feature - [%~2] is already enabled. echo.------------------------------------------------------------------------------- ) else ( echo.------------------------------------------------------------------------------- echo.Enabling Windows Feature - [%~2]... echo.------------------------------------------------------------------------------- %DISM% /Image:"%~1" /Enable-Feature /FeatureName:%~2 if "!ErrorLevel!" equ "50" ( echo.------------------------------------------------------------------------------- echo.Enabling Windows Feature - [%~2] with "/All" arg... echo.------------------------------------------------------------------------------- %DISM% /Image:"%~1" /Enable-Feature /FeatureName:%~2 /All ) ) echo. echo. goto :EOF ::------------------------------------------------------------------------------------------- I have placed the condition to handle the "Error: 50". This error will only be returned if there is a first attempt to enable the Feature. Then the operation will be performed once, with the default command present in Toolkit.cmd: Code: %DISM% /Image:"%~1" /Enable-Feature /FeatureName:%~2 If the error occurs it will be repeated with this other command: Code: %DISM% /Image:"%~1" /Enable-Feature /FeatureName:%~2 /All However, I don't know if applying the command with the argument "/All" to enable any of the components available in the list can do any harm. If it doesn't cause any other problems, to solve this "Error: 50", we can simply replace one command with the other. from: Code: %DISM% /Image:%~1 /Enable-Feature /FeatureName:%~2 to: Code: %DISM% /Image:"%~1" /Enable-Feature /FeatureName:%~2 /All Spoiler: So, the code for Enabling Features looks like this: Code: ::------------------------------------------------------------------------------------------- :: Function to enable a feature inside a Image :: Input Parameters [ %~1 : Image Mount Path, %~2 : Feature Name ] ::------------------------------------------------------------------------------------------- :EnableFeature %DISM% /Image:"%~1" /Get-FeatureInfo /FeatureName:%~2 | findstr /c:"State : Enabled" >nul if "!ErrorLevel!" equ "0" ( echo.------------------------------------------------------------------------------- echo.Windows Feature - [%~2] is already enabled. echo.------------------------------------------------------------------------------- ) else ( echo.------------------------------------------------------------------------------- echo.Enabling Windows Feature - [%~2]... echo.------------------------------------------------------------------------------- %DISM% /Image:"%~1" /Enable-Feature /FeatureName:%~2 /All ) echo. echo. goto :EOF ::------------------------------------------------------------------------------------------- And, the "Error: 32" will no longer occur because there is a check in the Feature, whether it is already Enabled or Disabled. EDIT: For those who use the Custom Toolkit, this should be changed as well. I have not yet uploaded a file with this part fixed. Probably a few days after the next UUPdump releases!
Complementing the Features Qualification Scheme: Identified all components that present Error: 50 and their deposits for Builds from 19041. Spoiler: error: 50 and depedencies Code: ClientForNFS-Infrastructure depends on: ServicesForNFS-ClientOnly DirectPlay depends on: LegacyComponents HostGuardian depends on: Microsoft-Hyper-V, Microsoft-Hyper-V-All, Microsoft-Hyper-V-Hypervisor, Microsoft-Hyper-V-Services IIS-ApplicationDevelopment depends on: IIS-WebServer, IIS-WebServerRole IIS-ApplicationInit depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole IIS-ASP depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole, IIS-RequestFiltering, IIS-Security, IIS-ISAPIExtensions IIS-ASPNET depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole, IIS-DefaultDocument, IIS-CommonHttpFeatures, IIS-ISAPIFilter, IIS-ISAPIExtensions, IIS-NetFxExtensibility, IIS-RequestFiltering, IIS-Security, NetFx3, NetFx4Extended-ASPNET45, NetFx4-AdvSrvs IIS-ASPNET45 depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole, NetFx4Extended-ASPNET45, NetFx4-AdvSrvs, IIS-DefaultDocument, IIS-CommonHttpFeatures, IIS-ISAPIFilter, IIS-ISAPIExtensions, IIS-NetFxExtensibility45, IIS-RequestFiltering, IIS-Security IIS-BasicAuthentication depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-CertProvider depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-CGI depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole IIS-ClientCertificateMappingAuthentication depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-CommonHttpFeatures depends on: IIS-WebServer, IIS-WebServerRole IIS-CustomLogging depends on: IIS-HealthAndDiagnostics, IIS-WebServer, IIS-WebServerRole IIS-DefaultDocument depends on: IIS-CommonHttpFeatures, IIS-WebServer, IIS-WebServerRole IIS-DigestAuthentication depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-DirectoryBrowsing depends on: IIS-CommonHttpFeatures, IIS-WebServer, IIS-WebServerRole IIS-FTPExtensibility depends on: IIS-FTPServer, IIS-WebServerRole, IIS-FTPSvc IIS-FTPServer depends on: IIS-WebServerRole IIS-FTPSvc depends on: IIS-FTPServer, IIS-WebServerRole IIS-HealthAndDiagnostics depends on: IIS-WebServer, IIS-WebServerRole IIS-HttpCompressionDynamic depends on: IIS-Performance, IIS-WebServer, IIS-WebServerRole IIS-HttpCompressionStatic depends on: IIS-Performance, IIS-WebServer, IIS-WebServerRole IIS-HttpErrors depends on: IIS-CommonHttpFeatures, IIS-WebServer, IIS-WebServerRole IIS-HttpLogging depends on: IIS-HealthAndDiagnostics, IIS-WebServer, IIS-WebServerRole IIS-HttpRedirect depends on: IIS-CommonHttpFeatures, IIS-WebServer, IIS-WebServerRole IIS-HttpTracing depends on: IIS-HealthAndDiagnostics, IIS-WebServer, IIS-WebServerRole IIS-IIS6ManagementCompatibility depends on: IIS-WebServerManagementTools, IIS-WebServerRole IIS-IISCertificateMappingAuthentication depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-IPSecurity depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-ISAPIExtensions depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole IIS-ISAPIFilter depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole IIS-LegacyScripts depends on: IIS-IIS6ManagementCompatibility, IIS-WebServerManagementTools, IIS-WebServerRole, IIS-Metabase, IIS-WMICompatibility IIS-LegacySnapIn depends on: IIS-IIS6ManagementCompatibility, IIS-WebServerManagementTools, IIS-WebServerRole, IIS-Metabase IIS-LoggingLibraries depends on: IIS-HealthAndDiagnostics, IIS-WebServer, IIS-WebServerRole IIS-ManagementConsole depends on: IIS-WebServerManagementTools, IIS-WebServerRole IIS-ManagementScriptingTools depends on: IIS-WebServerManagementTools, IIS-WebServerRole IIS-ManagementService depends on: IIS-WebServerManagementTools, IIS-WebServerRole, NetFx4Extended-ASPNET45, NetFx4-AdvSrvs IIS-Metabase depends on: IIS-IIS6ManagementCompatibility, IIS-WebServerManagementTools, IIS-WebServerRole IIS-NetFxExtensibility depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole, IIS-RequestFiltering, IIS-Security, NetFx3, NetFx4Extended-ASPNET45, NetFx4-AdvSrvs IIS-NetFxExtensibility45 depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole, NetFx4Extended-ASPNET45, NetFx4-AdvSrvs, IIS-RequestFiltering, IIS-Security IIS-ODBCLogging depends on: IIS-HealthAndDiagnostics, IIS-WebServer, IIS-WebServerRole IIS-Performance depends on: IIS-WebServer, IIS-WebServerRole IIS-RequestFiltering depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-RequestMonitor depends on: IIS-HealthAndDiagnostics, IIS-WebServer, IIS-WebServerRole IIS-Security depends on: IIS-WebServer, IIS-WebServerRole IIS-ServerSideIncludes depends on: IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServerRole IIS-StaticContent depends on: IIS-CommonHttpFeatures, IIS-WebServer, IIS-WebServerRole IIS-URLAuthorization depends on: IIS-Security, IIS-WebServer, IIS-WebServerRole IIS-WebDAV depends on: IIS-CommonHttpFeatures, IIS-WebServer, IIS-WebServerRole, IIS-StaticContent, IIS-RequestFiltering, IIS-Security IIS-WebServer depends on: IIS-WebServerRole IIS-WebServerManagementTools depends on: IIS-WebServerRole IIS-WMICompatibility depends on: IIS-IIS6ManagementCompatibility, IIS-Metabase Microsoft-Hyper-V depends on: Microsoft-Hyper-V-All MicrosoftWindowsPowerShellV2 depends on: MicrosoftWindowsPowerShellV2Root MSMQ-ADIntegration depends on: MSMQ-Server, MSMQ-Container MSMQ-HTTP depends on: IIS-HttpRedirect, IIS-LoggingLibraries, IIS-RequestMonitor, IIS-HttpTracing, IIS-ISAPIExtensions, IIS-Metabase, IIS-IIS6ManagementCompatibility NFS-Administration depends on: ServicesForNFS-ClientOnly WAS-ConfigurationAPI depends on: WAS-WindowsActivationService WAS-NetFxEnvironment depends on: WAS-WindowsActivationService, NetFx3 WAS-ProcessModel depends on: WAS-WindowsActivationService WCF-HTTP-Activation depends on: NetFx3, IIS-NetFxExtensibility, WAS-NetFxEnvironment, WAS-ConfigurationAPI WCF-HTTP-Activation45 depends on: IIS-ASPNET45, IIS-ISAPIFilter, IIS-ISAPIExtensions, IIS-NetFxExtensibility45, WAS-ConfigurationAPI WCF-MSMQ-Activation45 depends on: WAS-ConfigurationAPI WCF-NonHTTP-Activation depends on: NetFx3, WAS-NetFxEnvironment, WAS-ConfigurationAPI WCF-Pipe-Activation45 depends on: WAS-ConfigurationAPI WCF-TCP-Activation45 depends on: WAS-ConfigurationAPI Windows-Defender-Default-Definitions Error: 50 depends on: ??? About the addition of / ALL in the command for Enable-Feature, for all components, does not cause any harm. So I will not even launch the modification with the check conditions for Error: 50. In the tests, I only obtained positive results, but if someone has, please leave me informed. Identified 80 of 141 Windows Features, which generate pending. Spoiler: 80 components list Code: AppServerClient Client-DeviceLockdown Client-EmbeddedBootExp Client-EmbeddedLogon Client-EmbeddedShellLauncher Client-KeyboardFilter Client-ProjFS Client-UnifiedWriteFilter ClientForNFS-Infrastructure Containers Containers-DisposableClientVM Containers-HNS Containers-SDN DataCenterBridging DirectoryServices-ADAM-Client DirectPlay HostGuardian HypervisorPlatform IIS-ApplicationDevelopment IIS-CommonHttpFeatures IIS-FTPServer IIS-HealthAndDiagnostics IIS-IIS6ManagementCompatibility IIS-Performance IIS-Security IIS-WebServer IIS-WebServerManagementTools IIS-WebServerRole LegacyComponents MediaPlayback Microsoft-Hyper-V Microsoft-Hyper-V-All Microsoft-Hyper-V-Hypervisor Microsoft-Hyper-V-Management-Clients Microsoft-Hyper-V-Management-PowerShell Microsoft-Hyper-V-Services Microsoft-Hyper-V-Tools-All Microsoft-Windows-Subsystem-Linux MicrosoftWindowsPowerShellV2Root MSMQ-ADIntegration MSMQ-Container MSMQ-DCOMProxy MSMQ-HTTP MSMQ-Multicast MSMQ-Server MSMQ-Triggers MSRDC-Infrastructure MultiPoint-Connector MultiPoint-Connector-Services MultiPoint-Tools NetFx3 NFS-Administration Printing-Foundation-Features Printing-Foundation-InternetPrinting-Client Printing-Foundation-LPDPrintService Printing-Foundation-LPRPortMonitor Printing-PrintToPDFServices-Features Printing-XPSServices-Features SearchEngine-Client-Package ServicesForNFS-ClientOnly SimpleTCP SMB1Protocol SMB1Protocol-Client SMB1Protocol-Deprecation SMB1Protocol-Server SmbDirect TelnetClient TFTP TIFFIFilter VirtualMachinePlatform WAS-WindowsActivationService WCF-HTTP-Activation45 WCF-MSMQ-Activation45 WCF-Pipe-Activation45 WCF-Services45 WCF-TCP-Activation45 WCF-TCP-PortSharing45 Windows-Defender-ApplicationGuard Windows-Identity-Foundation WorkFolders-Client Cleanup Sources, if you want, should be applied before enabling features. And, I modified the code so that this question is displayed as soon as it starts the application of "Enable Features". According to these tests and checks, and knowing that NetFX3 is a prerequisite for some other components. I also learned that this should be installed first. Then it was also established, in the code that if it is present in the list, then after decided by the user whether or not to do the CleanPsource, this will be the first to be installed and enabled, followed by the rest of the components in the list. If you do not want to enable NetFX3, be sure to remove the components that depend on this. Spoiler: Lista de Dependentes do NetFX3 Code: IIS-ASPNET IIS-NetFxExtensibility WAS-NetFxEnvironment WCF-HTTP-Activation WCF-NonHTTP-Activation The only thing that will happen if these components are in the list is the "Error: 50" due to NetFX3 can not be installed by mere Enable-Feature dism command, as there is a need to integrate a cab package. Spoiler: about Ghost SFC Error Just to make it clear to the people who do not like to see the "Ghost SFC Error" Me too, I did not like it. But I will put some of my experience, so that you can take your considerations. Even customizing to integrate the most current icons, you do not escape it. I add themes and replace the Dark.Theme file ... SFC Error. Replaces a blue official wallpaper for a Black ... SFC Error. Because changed the hash of the files, the problem of Ghost SFC Error will occur. Not to mention the absence of files, hehehehe. The business is boring, because these are details that were not even accused, since they do not cause problems. So I believe, in my ignorance.
Add /SkipLicense at the end of the command. Code: DISM.exe /Image:"C:\ToolKit\Mount\Install\2" /Add-ProvisionedAppxPackage /PackagePath:Microsoft.WindowsdVDPlayer2_2019.17091.10381.0_neutral_ ~ _8wekyb3d8bbwe.appxbundle /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.30035.0_x64__8wekyb3d8bbwe.appx /SkipLicense Code: DISM.exe /OnLine /Add-ProvisionedAppxPackage /PackagePath:Microsoft.WindowsdVDPlayer2_2019.17091.10381.0_neutral_ ~ _8wekyb3d8bbwe.appxbundle /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.30035.0_x64__8wekyb3d8bbwe.appx /SkipLicense
But in Tookit MSMG uses examples with /SkipLicense. Check in the code. The Example tha will serv you is: Code: if "%%j" equ "I_RawImageExtension" ( echo.------------------------------------------------------------------------------- echo.Integrating Raw Image Extension Provisioned Appx Package... echo.------------------------------------------------------------------------------- if "%SelectedSourceOS%" equ "w10" %DISM% /Image:"%InstallMount%\%%i" /Add-ProvisionedAppxPackage /PackagePath:%RawImageExtension_Appx% %VCLibs14_Appx% /SkipLicense if "%SelectedSourceOS%" equ "w11" %DISM% /Image:"%InstallMount%\%%i" /Add-ProvisionedAppxPackage /PackagePath:%RawImageExtension_Appx% /SkipLicense echo. ) change it and add one look like this, but like this one below. Code: if "%%j" equ "I_WindowsDVDPlayer2" ( echo.------------------------------------------------------------------------------- echo.Integrating Windows DVD Player 2 Provisioned Appx Package... echo.------------------------------------------------------------------------------- %DISM% /Image:"%InstallMount%\%%i" /Add-ProvisionedAppxPackage /PackagePath:%WindowsDVDPlayer2_Appx% %VCLibs14_Appx% /SkipLicense echo. ) You have to add the paths in the variables, add it on the menu, etc.
Toolkit does not see this file, it is not related to the license file. Toolkit does not even have the option to integrate this UWP APP. Or you integrate by the outside for every path to each mountpoint folder or you modifies the menus to be offered the option to integrate. Or you simply rename your APPX file to "RawimageExtension.AppXBundle" that Toolkit will install WindowsDVD instead of RawImageExtension.
It's difficult for me Found the license files in the folder with the program \ Toolkit \ Bin \ applicense I installed the player to the operating system and it does not start After startup writes your account is not supported Probably need to buy And that MSMG Toolkit does not support integration I did not know Well, then he does not need You can consider the question closed Thank you for tips
Yes the License is there. But Wasn't Work? To put the license with your image in service (with mounted indexes) you can open the CMD as admin and put the earlier commands. Just put the correct paths to the files. Replace the /SkipLicese for /LicensePath:C:\PathToToolkit\Bin\AppLicense\Microsoft.WindowsDVDPlayer_8wekyb3d8bbwe.xml
No, it was not. I installed on the workman and the player does not start. It makes no sense to integrate. It requires an account or purchase ...
Not that it does not support. But the option to integrate is not available at the moment. I do not believe it's a paid app, no. Because RG-Adguard does not allow downloading UWP paid applications. EDIT: I just got into the store and the value is there. It's really, a UWP paid.
@MSMG Is this version safe to use on the latest Windows 10 (19044.1645) and Windows 11 (22000.613) images?
@Feartamixg you could at least read the changelog MSMG posted before asking the question. Nobody can really tell you "yes it's safe"/"no it's not safe". If you're modifying a supported build, it should be "safe". If you're modifying a newer build - trial and error.
I am familiar with the changelog, but thanks for pointing it out for me. I wondered if perhaps others had tested with the latest builds of Windows. No amount of reading changelogs can answer that.
Doing that right now, the x64 Windows 10 build 1645. Give me an hour and I'll update with my findings. Edit: Source x64 1645 iso retrieved from UUP dump, modded with MSMG toolkit, added some stuff and removed some stuff, deployed the resulting ESD, no errors, all fine. Cheers.
I went to test Windows 11 here with the Start Scheme Custom Menu. And it did not work. I should be coding something, and I had to go back and a small part of the code for the path of the folder with the Start menu templates, was undone with the Ctrl + Z of life. In "CustomToolkit.cmd" look for this line: Code: set "XMLs=%Bin%\XMLs" and below it add: Code: set "StartMenuLayoutBIN=%Bin%\StartMenuLayoutBIN" Tomorrow, I have already posted a corrected version of Custom Toolkit. With some details reorganized in the ISO saving step with or without use of Virtual Create Editions. Nothing very noticeable, but also to rearrange so that Single Language issues are positioned as the first option, as in the original ISOs.