Hm, sorry for late reply. Extreme, maybe not I made Powershell Script its atm 700 lines. Im not pro in scripting started learning this like month maybe ago. It can enable/disable features, remove/add capabilities, add/remove packages/backup (thanks for SxSExtract Script works well for backup). I made iso like u did MSMG Toolkit(First Updates and stuff i want to integrate, then removal) and NTLite, its probably the best way to do it at this moment. Dont Know why(Yet). Dism tool sometimes just throw errors when removing packages ??? Anyone have any ideas why ??? Thats only problem with removal on offline image. Used to remove some more packages online, all works so far. Thats list of packages im on ltsc 2019 thats (353) Packages excluding laguage: Spoiler: Packages Atm Microsoft-Media-Foundation-Package Microsoft-Media-Foundation-WOW64-Package Microsoft-OneCore-EventLogAPI-Package Microsoft-OneCore-Http-Package Microsoft-OneCore-IsolatedUserMode-minkernel-Package Microsoft-OneCore-IsolatedUserMode-onecore-Package Microsoft-OneCore-IsolatedUserMode-Package Microsoft-OneCore-Multimedia-MFPMP-Package Microsoft-OneCore-Multimedia-MFPMP-WOW64-Package Microsoft-OneCore-VirtualizationBasedSecurity-Package Microsoft-Windows-AppManagement-AppV-Package Microsoft-Windows-AppManagement-AppV-WOW64-Package Microsoft-Windows-AppManagement-Common-Package Microsoft-Windows-AppManagement-Common-WOW64-Package Microsoft-Windows-AppManagement-UEV-Package Microsoft-Windows-AppManagement-UEV-WOW64-Package Microsoft-Windows-Basic-Http-Minio-Package Microsoft-Windows-Branding-EnterpriseS-Package Microsoft-Windows-Client-Desktop-Required-Package0010 Microsoft-Windows-Client-Desktop-Required-Package00 Microsoft-Windows-Client-Desktop-Required-Package01 Microsoft-Windows-Client-Desktop-Required-Package02 Microsoft-Windows-Client-Desktop-Required-Package031020 Microsoft-Windows-Client-Desktop-Required-Package031021 Microsoft-Windows-Client-Desktop-Required-Package0310 Microsoft-Windows-Client-Desktop-Required-Package03110 Microsoft-Windows-Client-Desktop-Required-Package03111 Microsoft-Windows-Client-Desktop-Required-Package0311220 Microsoft-Windows-Client-Desktop-Required-Package03112 Microsoft-Windows-Client-Desktop-Required-Package03113 Microsoft-Windows-Client-Desktop-Required-Package03114 Microsoft-Windows-Client-Desktop-Required-Package03115 Microsoft-Windows-Client-Desktop-Required-Package0311 Microsoft-Windows-Client-Desktop-Required-Package0312 Microsoft-Windows-Client-Desktop-Required-Package0313 Microsoft-Windows-Client-Desktop-Required-Package0314 Microsoft-Windows-Client-Desktop-Required-Package0315 Microsoft-Windows-Client-Desktop-Required-Package0316 Microsoft-Windows-Client-Desktop-Required-Package0317 Microsoft-Windows-Client-Desktop-Required-Package0318 Microsoft-Windows-Client-Desktop-Required-Package0319 Microsoft-Windows-Client-Desktop-Required-Package03 Microsoft-Windows-Client-Desktop-Required-Package Microsoft-Windows-Client-Desktop-Required-WOW64-Package001020 Microsoft-Windows-Client-Desktop-Required-WOW64-Package0010 Microsoft-Windows-Client-Desktop-Required-WOW64-Package0011 Microsoft-Windows-Client-Desktop-Required-WOW64-Package0012 Microsoft-Windows-Client-Desktop-Required-WOW64-Package0013 Microsoft-Windows-Client-Desktop-Required-WOW64-Package0014 Microsoft-Windows-Client-Desktop-Required-WOW64-Package0015 Microsoft-Windows-Client-Desktop-Required-WOW64-Package00 Microsoft-Windows-Client-Desktop-Required-WOW64-Package Microsoft-Windows-Client-Features-Package00 Microsoft-Windows-Client-Features-Package0110 Microsoft-Windows-Client-Features-Package0111 Microsoft-Windows-Client-Features-Package0112 Microsoft-Windows-Client-Features-Package0113 Microsoft-Windows-Client-Features-Package0114 Microsoft-Windows-Client-Features-Package0115 Microsoft-Windows-Client-Features-Package0116 Microsoft-Windows-Client-Features-Package01 Microsoft-Windows-Client-Features-Package02 Microsoft-Windows-Client-Features-Package03 Microsoft-Windows-Client-Features-Package04 Microsoft-Windows-Client-Features-Package05 Microsoft-Windows-Client-Features-Package Microsoft-Windows-Client-Features-WOW64-Package0010 Microsoft-Windows-Client-Features-WOW64-Package0011 Microsoft-Windows-Client-Features-WOW64-Package0012 Microsoft-Windows-Client-Features-WOW64-Package00 Microsoft-Windows-Client-Features-WOW64-Package01 Microsoft-Windows-Client-Features-WOW64-Package02 Microsoft-Windows-Client-Features-WOW64-Package Microsoft-Windows-Client-Optional-Features-Package Microsoft-Windows-Common-Foundation-Package Microsoft-Windows-Common-RegulatedPackages-Package Microsoft-Windows-Common-RegulatedPackages-WOW64-Package Microsoft-Windows-ConfigCI-Onecore-Package Microsoft-Windows-ConfigCI-Onecore-WOW64-Package Microsoft-Windows-ConfigCI-Package Microsoft-Windows-CoreSystem-DISM-Package Microsoft-Windows-DeviceGuard-GPEXT-base-Package Microsoft-Windows-DeviceGuard-GPEXT-onecore-Package Microsoft-Windows-DeviceGuard-GPEXT-Package Microsoft-Windows-EditionPack-Professional-Package Microsoft-Windows-EditionPack-Professional-WOW64-Package Microsoft-Windows-Editions-EnterpriseS-Package Microsoft-Windows-EditionSpecific-EnterpriseS-Package Microsoft-Windows-Enterprise-Desktop-Shared-Package Microsoft-Windows-Enterprise-Desktop-Shared-WOW64-Package Microsoft-Windows-EnterpriseS-SPP-Components-Package Microsoft-Windows-EnterpriseSEdition Microsoft-Windows-FCI-Client-Package Microsoft-Windows-FodMetadata-Package Microsoft-Windows-Foundation-Package Microsoft-Windows-GroupPolicy-ClientExtensions-admin-Package Microsoft-Windows-GroupPolicy-ClientExtensions-ds-Package Microsoft-Windows-GroupPolicy-ClientExtensions-Package Microsoft-Windows-GroupPolicy-ClientExtensions-WOW64-admin-Package Microsoft-Windows-GroupPolicy-ClientExtensions-WOW64-ds-Package Microsoft-Windows-GroupPolicy-ClientExtensions-WOW64-Package Microsoft-Windows-GroupPolicy-ClientTools-admin-Package Microsoft-Windows-GroupPolicy-ClientTools-base-Package Microsoft-Windows-GroupPolicy-ClientTools-com-Package Microsoft-Windows-GroupPolicy-ClientTools-drivers-Package Microsoft-Windows-GroupPolicy-ClientTools-ds-Package Microsoft-Windows-GroupPolicy-ClientTools-enduser-Package Microsoft-Windows-GroupPolicy-ClientTools-inetcore-Package Microsoft-Windows-GroupPolicy-ClientTools-inetsrv-Package Microsoft-Windows-GroupPolicy-ClientTools-minio-Package Microsoft-Windows-GroupPolicy-ClientTools-minkernel-Package Microsoft-Windows-GroupPolicy-ClientTools-multimedia-Package Microsoft-Windows-GroupPolicy-ClientTools-net-Package Microsoft-Windows-GroupPolicy-ClientTools-onecore-Package Microsoft-Windows-GroupPolicy-ClientTools-onecoreuap-Package Microsoft-Windows-GroupPolicy-ClientTools-Package Microsoft-Windows-GroupPolicy-ClientTools-printscan-Package Microsoft-Windows-GroupPolicy-ClientTools-servercommon-Package Microsoft-Windows-GroupPolicy-ClientTools-shell-Package Microsoft-Windows-GroupPolicy-ClientTools-termsrv-Package Microsoft-Windows-GroupPolicy-ClientTools-windows-Package Microsoft-Windows-GroupPolicy-ClientTools-WOW64-admin-Package Microsoft-Windows-GroupPolicy-ClientTools-WOW64-ds-Package Microsoft-Windows-GroupPolicy-ClientTools-WOW64-Package Microsoft-Windows-Help-ClientUA-Enterprise-Package Microsoft-Windows-Hyphenation-Dictionaries-pl-Package Microsoft-Windows-LanguageFeatures-OCR-pl-pl-Package Microsoft-Windows-Media-Format-multimedia-Package Microsoft-Windows-Media-Format-Package Microsoft-Windows-Media-Format-windows-Package Microsoft-Windows-Media-Format-WOW64-multimedia-Package Microsoft-Windows-Media-Format-WOW64-Package Microsoft-Windows-Media-Format-WOW64-windows-Package Microsoft-Windows-MediaPlayback-OC-Package Microsoft-Windows-MediaPlayer-Package Microsoft-Windows-MediaPlayer-Payload-Package Microsoft-Windows-Multimedia-MF-avcore-Package Microsoft-Windows-Multimedia-MF-multimedia-Package Microsoft-Windows-Multimedia-MF-Package Microsoft-Windows-Multimedia-MF-WOW64-avcore-Package Microsoft-Windows-Multimedia-MF-WOW64-Package Microsoft-Windows-Multimedia-RestrictedCodecs-avcore-Package Microsoft-Windows-Multimedia-RestrictedCodecs-multimedia-Package Microsoft-Windows-Multimedia-RestrictedCodecs-Package Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-avcore-Package Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-multimedia-Package Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-Package Microsoft-Windows-NetFx-AutoNgenEnable.3.5 Microsoft-Windows-NetFx-NgenAssemblyExclusionClient Microsoft-Windows-NetFx-Shared-Misc Microsoft-Windows-NetFx-Shared-MOF-Client Microsoft-Windows-NetFx-Shared-MOF-Extended Microsoft-Windows-NetFx-Shared-Package Microsoft-Windows-NetFx-Shared-Perfcounters-Client Microsoft-Windows-NetFx-Shared-Perfcounters-Extended Microsoft-Windows-NetFx-Shared-Typelibs Microsoft-Windows-NetFx-Shared-WCF-HttpNamespace Microsoft-Windows-NetFx-Shared-WPF-Package Microsoft-Windows-NetFx-Windows-Built-Package Microsoft-Windows-NetFx2-OC-Package Microsoft-Windows-NetFx3-OC-Package Microsoft-Windows-NetFx3-OnDemand-Package Microsoft-Windows-NetFx4-US-OC-Package Microsoft-Windows-NetworkDiagnostics-DirectAccessEntry-Package Microsoft-Windows-Portable-Devices-multimedia-Package Microsoft-Windows-Portable-Devices-Package Microsoft-Windows-Portable-Devices-windows-Package Microsoft-Windows-Portable-Devices-WOW64-Package Microsoft-Windows-Portable-Devices-WOW64-windows-Package Microsoft-Windows-PowerShell-V2-Client-Package Microsoft-Windows-Presentation-Package Microsoft-Windows-SecConfig-Package Microsoft-Windows-SecureStartup-Package Microsoft-Windows-SecureStartup-Subsystem-base-Package Microsoft-Windows-SecureStartup-Subsystem-onecore-Package Microsoft-Windows-SecureStartup-Subsystem-Package Microsoft-Windows-SecureStartup-Subsystem-WOW64-base-Package Microsoft-Windows-SecureStartup-Subsystem-WOW64-onecore-Package Microsoft-Windows-SecureStartup-Subsystem-WOW64-Package Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package Microsoft-Windows-Spelling-Dictionaries-pl-Package Microsoft-Windows-SQL-Lite-Package Microsoft-Windows-SQL-Lite-WOW64-Package Microsoft-Windows-TerminalServices-WMIProvider-Package Microsoft-Windows-TextPrediction-Dictionaries-pl-Package Microsoft-Windows-win32calc-Package Microsoft-Windows-WindowsMediaPlayer-Troubleshooters-Package Microsoft-Windows-WPD-LegacyWmdmFeature-Feature-Package Microsoft-Windows-WPD-LegacyWmdmFeature-Feature-WOW64-Package Microsoft-Windows-WPD-UltimatePortableDeviceFeature-Feature-Package Microsoft-Windows-WPD-UltimatePortableDeviceFeature-Feature-WOW64-Package Multimedia-MFCore-Package Multimedia-MFCore-WOW64-Package Multimedia-RestrictedCodecsCore-Full-Package Multimedia-RestrictedCodecsCore-Full-WOW64-Package Multimedia-RestrictedCodecsCore-Package Multimedia-RestrictedCodecsCore-WOW64-Package Multimedia-RestrictedCodecsExt-Package Multimedia-RestrictedCodecsExt-WOW64-Package Networking-MPSSVC-Rules-EnterpriseEdition-net-Package Networking-MPSSVC-Rules-EnterpriseEdition-onecore-Package Networking-MPSSVC-Rules-EnterpriseEdition-Package Server-Help-Package.ClientEnterprise Not Sure What Next
Was maintained as X:\. So I was wrong. And, I was confused... I did not understand anything about this logic in this integration process of win32calc, because it is the only process that is peculiar, that does not follow the pattern I see at that time. @MSMG, can you explain a little more detailed why this particularity in the integration of Win32Calc? I confused the meanings of Dynamic path with Relative path and with Direct Path? X:\ would not it be considered a direct path?
Actually the custom packs I do create from a live system already have the path set to C:\ so the reg files will contain C:\ instead of X:\ , suppose if the user integrates the packs like NET6, PowerShell7 and installs the OS to some other drive other than the C:\ then it will have issues and here comes the dynamic paths to rescue. The dynamic paths will use the %SystemDrive% for getting the OS installation drive and then the C:\ becomes %SystemDrive%\ X:\ path is used by the Windows setup installer during the Windows installation.
So it is. That's how I understand. But then, all the reg files from the other Custom Packs, should be modified from C: to X:? In order to obey this scheme of the Windows setup installer during the Windows installation be X:? And, on the NET5 for W7 and W81, the Toolkit still keeps the support? Or will there be NET6 for both?
No don't change it to X:\ just use the dynamic paths like the games pack. You need to import the key into registry, change the path to use the dynamic path and then export back the reg to file and add the new entries to the packs registry files.
Yes I have replaced the .NET 5 pack with .NET 6. Do you want the .NET 5 pack to be updated? if yes then will do create the packs or will share the steps to make it.
Until I understand logic I'll leave it as it is. I'm still confused. For when we do not understand, it seems that we are taking meaningless steps. When I understand I continue. Will there be NET6 for W7 and W81? If there is no, I will keep the NET5 options for both.
Thanks for the new version @MSMG I think I´ve found a "bug": In this menu 3 give me 5 give me also Source OS is Win11 .258 german Or does the new version don´t work with .258? Only with .1 and .318?
For example - Import this key to registry Code: [HKEY_LOCAL_MACHINE\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedhost] "Path"="C:\Program Files\dotnet\" - Open the registry editor and navigate to the above key. - Double click on Path sub value. - Change C:\Program Files to %Program Files% and click Ok. - Right click on sharedhost key in the left pane and choose export to file - Now this becomes the new reg settings. Code: [HKEY_LOCAL_MACHINE\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedhost] "Path"="\"%Program Files%\\dotnet\\\"" Here Path is of type REG_SZ, suppose if it's REG_EXPAND_SZ then the exported reg will show like this Code: [HKEY_LOCAL_MACHINE\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedhost] "Path"=hex(2):22,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,20,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,64,00,6f,00,74,00,6e,00,65,00,\ 74,00,5c,00,22,00,00,00 Yes there will be updated NET6 and PowerShell 7 packs for W7 and W81, just need some time to create it as I need to prepare the ISO with prerequisite updates for it to install and create the packs.
Yes, this I know the path between "\ ..."\. If a command is not fully added with the path and flags between "\ ..."\, this gives many problems. Importing some paths of this type to run through the context menu with the git was where I suffered to learn. I had never noticed this difference. I did not know that REG_EXPAND_SZ could be a path between "\ ..."\ in hex.
MSMG,Can you please tell me what caused the OOBEKEYBOARD OOBEREGION error when installing Windows 11 22000.258 RU? I removed all components except InternetExplorer WindowsMediaPlayer WindowsFirewall AADBrokerPlugin AccountsControl XboxIdentityProvider XboxGameCallableUI StorePurchaseApp WindowsStoreApp WindowsStoreClient There components were no errors when deleting Toolkit 11.9 is located at C:/Toolkit
I had not even thought of the personalized packs, I thought that official development and compatibility had been ceased with W7 and W81, that's why I had asked. So at the moment, provisionally, I will only put the NET5 packs for W7 and W81 inside the NET6 folder, so that the script runs.
You have to keep all the needed for oobe. You can see this in the components descriptions in the all Categorys of the Remove menus.
Done testing and I don't think the Win32Calc is being integrated into x86 images. Does not show in Start menu or when I press the Calculator key on my keyboard. Shall rebuild with ToolKit again to ensure this is not just user error on my part.