@MSMG one question: after I removed all Windows components desired and more some "things" script also clean C:\Windows\sxs folder? thanks in advance
Now that we are approaching rs2 final.. with regards to unattended installs, how different is RS1 from RS2... I always remove all metro apps including store, as well as remove all basic components. Do the removals have any impact in RS2?
Hi there. The current version of MSMG 6.8 was used to process the image of the Windows 10 Enterprise 14393.0 x64 (July 2016). Not integrated updates, .Net 3.5, nothing at all. The components were removed: all Tiles, Biometrics, Connect, OneDrive, Telemetry, Skype, Xbox, Contact, Delivery, Cortana, Geo, Parental Controls, (no Retail Demo in Enterprise edition), Take Test, Quick Assist, Edge, Defender and Store. More or less a "standard" set. After installing the resulting image, the command "sfc / scannow" is executed with an error. This is checked several times. If I delete such components: Connect, Telemetry, Contact, Take Test, Quick Assist, Defender and Store with the use of the MSMG utility, and the remaining components from the list - with the use of another utility, then everything is fine. But I don’t like the use of two utilities. I suspect that the cause of the error is the use of some tweaks (for example, the registry) during image processing. If there is still no cause for concern, I ask you to dispel my doubts. Thank you all in advance.
@username122 I don't have an answer, but regarding "I delete such components...with the use of another utility", what other utility do you use for image editing? ------------ And This is the basic order of operations to avoid errors right? integrate langpacks->integrate updates/feat->remove stuff->integrate .netfx
Hey MSMG, I noticed there's no combination of ""%WimIndexVersion:~5,5%" gtr "10586"" and " Microsoft .NET Framework 4.6.2" Why u do dat?
Hi Guys , since a few versions back I got problems with dism wenn I'm using Dism.exe /online /Cleanup-Image /StartComponentCleanup . Than it happens what you can see on the screenshot. The error means, it can't find the specified file. I used to "kill" all apps, cortana and search, except the store with the Toolkit. I'm not using other tools. If anyone could PN me in german that would be great. I'm not well trained in writin' the english language . Greetings FLCL
@FLCL Hi well first thing I see that you are working with Powershell but here is Thread about MSMG Toolkit, so see in first page then you can understand how to this tool works is very different than Powershell
@ FLCL Had that likewise lately, a second run passed without any errors. Your screenshot shows that the component store was actually cleaned. Did you try to run the cleanup again?
Thank you guys for the fast reply . @ Tiger-1 Sure you're right. But my problem is that the dism error always happend wenn i'm using an ISO which is "tuned" by the Toolkit. @ s1ave77 Well yes, the error continues to occur. Mhh... acutally google won't help me to find the right english discription: sometimes I get the response from dism that everything's gone well, somtimes not.
Check your system with: Code: sfc /scannow If it finds corruptions, use next command to write errors to sfc.txt on desktop: Code: (findstr /i /c:"[SR]" "%windir%\Logs\CBS\CBS.log" | findstr /i /v /c:"verify" > "%userprofile%\desktop\sfc.txt") >nul 2>&1
I'm always getting error message "The specified package is not applicable to this image.". I'm trying to integrate Windows 10 1607 March 2017 updates. The iso I'm using a Windows 10 1607 x64 & x86 combined in one. Also another error message "An error occurred trying to open - windows10.0-kb4013420-x86_ce25d31d34689149aa4a09e4eed06c58bab8e731.cab Error: 0x80070002". Now I found out the toolkit only integrated x86 updates except windows10.0-kb4013420-x86_ce25d31d34689149aa4a09e4eed06c58bab8e731.cab and didn't integrate x64 updates. I had updates in the correct folder.
... Delta Update for Windows 10 Version 1607 (KB4013429).This kb is also not applicable in an image of line by dism too.