The test image I used contained en-US and zh-CN, will check with your package list to see what's breaking with Solitaire Collection. Spoiler OneDrive WindowsMixedReality 3DViewer AdvertisingXaml Alarms BingWeather Camera CommunicationsApps Cortana DesktopAppInstaller FeedbackHub GetHelp Getstarted Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People Photos ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes XboxApp XboxIdentityProvider YourPhone ZuneMusic Spoiler CEIP_SQM UnifiedTelemetryClient WindowsInsiderHub OneDrive WindowsMixedReality 3DViewer AdvertisingXaml Alarms BingWeather Camera CommunicationsApps Cortana DesktopAppInstaller FeedbackHub GetHelp Getstarted Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People Photos ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes XboxApp XboxIdentityProvider YourPhone ZuneMusic ZuneVideo Note: The Solitaire Collection depends on Xbox Game Callable UI
Ok here is what i got with the image 19041.1.191206-1406.VB_RELEASE_CLIENTPRO_OEMRET_X64FRE well the english powershell also happens in the untouch iso, so maybe it has to be that way, but as i recall it doesnt is that way on rtm windows, there also use to be and language experience pack, this does not exsist on this image.
Once the DISM /Online /Cleanup-Image /StartComponentCleanup is run then the SFC error will show up. Language Pack is included both in UUP and MSDN ISO, Language Interface Pack and Local Experience Pack is provided as additional packs to be installed on top of this image.
OK unless the image is sysprepped using DISM /Online /Cleanup-Image /StartComponentCleanup or DISM /Online /Cleanup-Image /StartComponentCleanup Resetbase will work after oobe with no sfc scan errors Just tested powershell on rtm 19041.264, it has to be that way, after using it. so my bad If dism is showing 19041.572 on image 19042.630 why is that, should it not be 19041.630 ? so far all is good, i will test the image on bare metal tonight thanks MSMG
The DISM showing 19042.XXX as 19041.XXXX is a bug and MS has acknowledge that and has said will be soon offering a fix for it.
Have uploaded a newer version of ToolKitHelper.exe for user testing, do check with 19042.572/630 and report back the results. Code: Name: ToolKitHelper.exe Size: 15963648 bytes (15 MB) SHA1: 74311A582D40530FD0497DAF284B4635B108134A From next version will support only the Patch Tuesday's Stable CU.
Great news to support stable Patch Tuesday's I have done the test with newer ToolKitHelper.exe, the issue still exsist on 19042.572/630 MSMG is it possible to only install 2012 C++ from packs, instead of them all, i only need 2012, because of poor MS support on older ati radeon graphics card, whitout C++ 2012 sometimes it is not installed via windows update, depending on ati gfx version, the worst case senario is BSOD why is 19041.1 different from 19041.264 rtm in bootup installing startscreen with the white text, instead of grey, its also is missing the org blue bootup background at startup, is it because of beta or esd ?, i dont see that on other esd, msdn or rtm builds from Ms
New update works so far with 19042.630. Before it would fail to completely mount all .wim files. Gonna update this post as I continue working on removing things. Also I can confirm that freaking Windows Security is being a PITA as I hadn't noticed that it had been brought back via updates. Here is the error I got.
I've used a couple ESD. But that ESD there was the one from MS. But all had the same issue. SO nothing is really wrong? everything is fine?
HI thumper1 All Ms images at the moment, has sfc scannow errors except 19041.1 ESD UUPDump and MSDN 19041.264
@MSMG, That suggestion: For Trimm Unwanted Image Indexes, it is very interesting because it allows the indexes to be in the order you selected earlier. I sent you PMs.
Hey, have a question. I'm using Toolkit 10.8 to integrate DirectX, VCRuntimes & DaRT. I start with a 1909 image that has 5 indexes and a size of 3768MB (added editions using NTLite) When the toolkit has finished its work, the image increases in size by 2,5GB (6265MB) What can I do to reduce the size of the wim image?
So the problem is with the removing the Solitaire App and not after removing it. This occurs only when the Toolkit folder path length is too long or have spaces and when the Toolkit.cmd is directly run instead of Start.cmd Will test with your Package list to see if any other reason the Solitaire is not getting removed properly. I have just recreated the Pack for Toolkit, the original author is @abbodi1406, you can check his VC runtime pack executable here and open the installer with 7-zip and extract the 2021 installer folder and get the details of the files included. Then mount the VC Pack provided in Toolkit to a folder and then only keep the files or folders noted earlier and then delete the rest of the things and unmount the image with committing the changes. Then use the new wim and the VC2012 registry file to integrate it to install.wim
Here the multi-index mounting, servicing and un-mounting is working properly. Waht error are you getting while mounting it. The Solitaire Collection App removal error this occurs only when the Toolkit folder path length is too long or have spaces and when the Toolkit.cmd is directly run instead of Start.cmd Give you source details will check it. Removed components except Windows Apps will be restored once the system updated with WU or manual updates installation, this applies to only W10 v1903 and above versions.
Adding packs or updates will increase the size and did you run the [5]->[1] Rebuild Source Images to reduce the overall image size.