I normally don't integrate games or the games explorer, as I have a separate package I downloaded from WinAero years ago and I've just stuck with that. But just for the sake of testing, I integrated it and you're right. The problem I have with Win23Calc is that, even though I select it for install it still doesn't install. This behavior stated in toolkit v133. The .exe is completely missing after Windows is installed. So I just downloaded the program (probably from WinAero again), and install it via my postinstall script. I don't think I've ever installed that component. Cant stand ads, and as it stands now I have never seen a single ad on Windows 10. Damn I forgot to check with my latest build whether the inbox apps were present after the install. I was more focused on trying to get the console working Ok, update on what's been happening; Built image with 13.5. I wanted to have the latest CU integrated and IIRC, 13.4 only supports 2965. Kept the following packages (If it's not on the list it was removed); Spoiler: Integrated ALL *experiencehost packages Windows Update Windows Firewall .Net 4.8.1 .Net 6 .Net 3.5 Notepad Sound themes Manual Set up Windows Photo Viewer Win32 Calculator Capture picker ClientCBS Inbox apps - VP9, HEIF, HEVC, MPEG-2, Webp and WebMedia extensions. I found that integrating the Realtek Audio console was pointless. The console will not install if the USB Audio Drivers are not installed. And since the image I'm using is for PCs that go as far back as 8th Gen CPUs which don't have USB audio it was pointless. So I installed the USB Audio and other motherboard drivers and installed the console using DISM, which completes successfully. However, when I try to start it the console crashes with this error in event log; Spoiler: Audio Console Crash Unable to start a DCOM Server: RealtekSemiconductorCorp.RealtekAudioControl_1.44.302.0_x64__dt26b99r8h8gj!App as Unavailable/Unavailable. The error: "3236560897" Happened while starting this command: "C:\Program Files\WindowsApps\RealtekSemiconductorCorp.RealtekAudioControl_1.44.302.0_x64__dt26b99r8h8gj\RtkUWP.exe" -ServerName:App.AppX2vzv616czv2j97f46vn25b5ksjvhr8z1.mca This is before I do any tweaking to Windows 10. It's just install from Image, install drivers, then Realtek Audio Console. My build process is; Spoiler: Image build 1. Extract ISO to DVD Folder 2. Toolkit, select source from DVD Folder 3. Integrate all desired components except .net 3.5 4. Install update windows10.0-kb5012599-x64_bc0efec7eb2782ac45b1749fb902a80e16832c4a.msu 5. Install latest CU, in this case windows10.0-kb5028166-x64_fe3aa2fef685c0e76e1f5d34d529624294273f41.msu 6. Do removals 7. Do some tweaks 8 Integrate .net 3.5 9. Apply and save changes 10. Build ISO I've never used the WHD option. I have no idea how that works. I have a vague recollection that I created an image with 13.4 and the console worked, but I'll have to retest it. The only issue with that is that the CU supported is 2965 from May 2023.
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1289#post-1794617 Use an UUP dump 19041.1 iso (just dont add updates there, then you will get this .1). Download the updates to WHD\w10\10.0.19041.1\x64 folder. integrate, update, remove, customize and save. Simple like that. For updating follow the options sequence in the link above.
Sorry if this is a dumb question, but "why?" Are you saying that downloading the patches (CUs), from MUC is not the right way to do it? Is it broken? Do they not get integrated properly? All my installed systems seem to reflect the updates that I applied when I created the image. My source image is per the changelog. LTSC 2021 19044.1288. I integrate the latest SSU then the latest CU that the toolkit supports. Is this process faulty? . That's the order I'm doing it. It seems all we are talking about is a different source for updates. I also have no knowledge of UUPDUMP. From what I've read many people have had issues (perhaps because like me they don't understand it). Spoiler: From Changelog.txt + Updated the Feature "Remove Windows Component" to support Windows 10 Client Enterprise LTSC 2021 (v10.0.19044.1288/v10.0.19044.3208 [KB5028166]) Source OS. Anyway, I've created a new image and retained the ContentDelivery component.That didn't work either. I'm over this. I've created several images with exactly the same components. The first one worked. All others didn't.
would there be any possibility of sending those copies to a more reasonable uploader like Google Disk or MEGA or Gofile? downloading through Terabox while the bandwidth is limited + it needs an 3rd party app running to even download((and I dont plan on buying the payable version), is kind of - throwing Away. No offense
No. I just didn't remember which version you used. I merely suggested WHD to apply the updates and as you said you didn't use it I pointed out the method by the link. But my suggestion to use 19041.1 was just an example. What a thing? I'm out of more ideas. It's bad that none of the test possibilities worked out. About win32calc in LTSC. The Calculador component is available for removing in System menu for LTSC Editions. Check if it is present in your RemovePkgsList. If yes, then it is removing the recently integrated Win32Calc. For Calculator UWP app the name in the list is CalculatorApp. This should not remove the recently integrated Win32Calc. But if you start the service on a supported image 19044.1288 and integrate the latest updates removing the components is supported. So, the fact that 2965 is supported doesn't prevent it from integrating more recent updates. What complicates it is only if you save the image (commit) and then try to remove components, at that point the support is lost. I know this because (in the past) I prepared an image with the updates applied with several steps already completed so, in theory, I only needed to mount, remove components and apply tweaks. WRONG... So MSMG explained this to me in another way... So I understood that I lost the support for removal in this case because this pre-prepared image had already become an out-of-support build.
Please check all links available in the first thread post. There are a pastebin with links provided by users like the kindly provided by @zero cool root .
Only for components from Removal Menus 1 to 7. I leave windows update disabled via tweaks. Whenever I can, I do an in-place update (update on top, with a new customized ISO). Eventually you will have to do a clean install (from scratch). Everyone needs it at one time or another a year. And I'm not saying it's related to that update method. I mean it's a necessity in general. It's been 4 years since I've only done in-place updates. (Clean installations only on client computers and one for testing here.) Last month I put w11 22621 into daily use which I did a clean install.
checked the pastebin links that were inside. as you mentioned. Kind of sad, they are not 'updated' as intended hope more options to download, will be available in future
Thank you for your reply. I am entering a phase of maximum security, due to the absurd increase in cyber attacks. Many Windows components contain huge vulnerabilities, for example: Internet Explorer, outdated Edge, old PowerShell (pre-7), SMB (WannaCry is concrete proof of this), Telnet, Windows Media Player.... I believe that creating the customized ISO with the cumulative update for 1 time per month and doing the installation from scratch is the best option in my case (only a few hours of work with MSMG Toolkit, Windows installation, LibreOffice, LibreWolf, Mullvad Browser... and cloning with Clonezilla). For someone who has done thousands of manual installations since Windows 98 SE, only 12 times a year is a low number (especially if I use Sysprep and Chocolatey, for several machines).
Remove native powershell will ensure that you have a lot of difficulties. PowerShell 7 is not ripe for replacement. This is complementary to native 5.1. IMAO, you can even create new control policies, removing it is not an option. It's up to you to decide what to do, but on the machine you use to make the custom ISOs you'll need native powershell. Because the scripts use cmd and powershell resources.
Ah, ok. All good. Ok, have completed more tests. 1. Integrating Content Delivery does not solve the issue 2. I did find out one thing - the version of the driver, 11.0.6000.290 must match the version of the console app. I had downloaded 1.44.302, i needed 1.41.290. 3. Installing matching driver and app versions did not solve the problem either 4. Have tried now with my image I created some time ago with 2965 and also the latest image with 3208. Neither work. At all times opening the console results in a DCOM crash. I seem to be going backwards. I have one other thing to try, which is an even older image. If that doesn't work I will give up. This used to be so simple, then Microsoft got in the way and now it's a nightmare. I use the manual method of removal; Select each component from the removal sub menus. I select all to remove (-), then add back the ones I want to keep. IIRC, Win32Calc is [G], which I definitely set to + Anyway, this is the least of my problems ATM. I have a workaround for that. I just thought of another test - a completely vanilla Windows 21H2 install from the base ISO I have. My assumption would be that if that works then it's got to be something that I'm removing with toolkit that needs to be kept? ...Several hours later... I can get the app to work on an unmodified Windows 21H2 19044-1288. The app wants to connect to the internet so since all installs are done offline the app crashes immediately with no errors. I'm guessing it wants to do a data dump on first run. I couldn't see any registry keys that might prevent this (like "firstrun"), but once I let it online it works fine. So, it seems something that I'm removing with the toolkit is killing it. Is there a way to track that down without having to build 80 separate images adding 1 removed component at a time? I will do one more test tomorrow to see if the DCOM error occurs if I let it on the Internet with the 19044.3208 image. My guess is it will still crash, but you never know.
Thanks for the advice. You are right. It is possible and recommended to disable Windows PowerShell 2.0, in Windows 10 (I disable it via Turn Windows features on or off). After doing a lot of research, I realized that it is not possible to upgrade the native 5.1 version directly to 7.x, as I imagined before, but rather to block some scripts for non-admins (which I need).
Yes, I disable this at all times. You can use DisableFeatures.txt I just dont remove the native PowerShell 5.1.
@MSMG, cortana for above 19041 remains blocked for removal. Is that right? Should it be changed from: Code: if "%CC_ShellSearch%" equ "+" ( set "CC_ShellSearch=-" if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" set "C_Cortana=+" ) else ( set "CC_ShellSearch=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" set "C_Cortana=*" ) ) to: Code: if "%CC_ShellSearch%" equ "+" ( set "CC_ShellSearch=-" set "C_Cortana=+" ) else ( set "CC_ShellSearch=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" set "C_Cortana=*" ) ) C_NETNativeFramework17 is available for 22621, but not available in the menu. from: Code: if "!ImageBuild!" geq "17763" if "!ImageBuild!" leq "19045" ( echo. [20] ^(!C_NETNativeFramework17!^) [106m[30m .NET Native Framework Package 1.7 ^(Microsoft.NET.Native.Framework.1.7^) [44m[97m to: Code: if "!ImageBuild!" geq "17763" if "!ImageBuild!" leq "22631" ( echo. [20] ^(!C_NETNativeFramework17!^) [106m[30m .NET Native Framework Package 1.7 ^(Microsoft.NET.Native.Framework.1.7^) [44m[97m or just: Code: if "!ImageBuild!" geq "17763" ( echo. [20] ^(!C_NETNativeFramework17!^) [106m[30m .NET Native Framework Package 1.7 ^(Microsoft.NET.Native.Framework.1.7^) [44m[97m optimizing from: Code: if /I "%%~#" equ "40" if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" ( if "%C_ZuneVideo%" equ "+" ( set "C_ZuneVideo=-" ) else ( if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+" set "C_ZuneVideo=+" ) ) if /I "%%~#" equ "40" if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22640" ( if "%C_ZuneVideo%" equ "+" ( set "C_ZuneVideo=-" ) else ( if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22640" if "%C_UIXaml27%" neq "*" set "C_UIXaml27=+" if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+" set "C_ZuneVideo=+" ) ) to: Code: if /I "%%~#" equ "40" ( if "%C_ZuneVideo%" equ "+" ( set "C_ZuneVideo=-" ) else ( if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22640" if "%C_UIXaml27%" neq "*" set "C_UIXaml27=+" if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+" set "C_ZuneVideo=+" ) ) typo from: Code: if "%C_XboxIdentityProvide%" neq "*" to: Code: if "%C_XboxIdentityProvider%" neq "*" from: Code: if /I "%%~#" equ "27" ( if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "22000" if "%C_QuickAssist%" equ "+" ( set "C_QuickAssist=-" ) else ( set "C_QuickAssist=+" ) ) to: Code: if /I "%%~#" equ "27" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "22000" (if "%C_QuickAssist%" equ "+" ( set "C_QuickAssist=-" ) else ( set "C_QuickAssist=+" ) ) Aestethical from: Code: if /I "%%~#" equ "21" if "%C_WindowsStoreCore%" neq "*" ( if "%C_WindowsStoreCore%" equ "+" ( if "%SelectedSourceOS%" equ "w10" set "C_ServicesStoreEngagement=-" if "%ImageBuild%" equ "17763" set "C_SolitaireCollection=-" if "%ImageBuild%" leq "22640" set "C_StickyNotes=-" set "C_StorePurchaseApp=-" if "%C_WindowsStore%" neq "*" set "C_WindowsStore=-" set "C_WindowsStoreCore=-" ) else ( set "C_WindowsStoreCore=+" ) ) to: Code: if /I "%%~#" equ "21" if "%C_WindowsStoreCore%" neq "*" ( if "%C_WindowsStoreCore%" equ "+" ( if "%SelectedSourceOS%" equ "w10" set "C_ServicesStoreEngagement=-" if "%ImageBuild%" equ "17763" set "C_SolitaireCollection=-" if "%ImageBuild%" leq "22640" set "C_StickyNotes=-" set "C_StorePurchaseApp=-" if "%C_WindowsStore%" neq "*" set "C_WindowsStore=-" set "C_WindowsStoreCore=-" ) else ( set "C_WindowsStoreCore=+" ) ) and several elses with double spaces. from: Code: ) else ( to: Code: ) else ( Finished
Why in the download folder of version 13.5 - 2 different files "Toolkit.cmd" (1 in folder and 1 in the archive)?
No the code is correct, these three packages are the missing base packages required for source boot or recovery images created using UUP source. The location for these three packages is <LanguagePacks\%SelectedSourceOS%\%PackageVersion%\%ImageArchitecture%>