@MSMG I removed everything except for Windows Defender on the 10.0.19042 image version (from MCT) and I got this. Is there anything else in specific that I need to avoid removing in addition to AADBrokerPlugin?
I'm still getting sfc errors, here is my procedure: Used Win10 installation media creation tool to make 20H2 iso Converted to Wim format Select source > dvd folder > Win10 Pro, mount both Remove using RemovePkgsList.txt (3 > 3 > Y > 2) Unpin all Start menu icons (4 > 6) Stop 3rd Party Apps (4 > 8 > D) Integrate Microsoft .NET Framework 3.5 (2 > 3 > A) Apply changes to image (don't clean) (5 > 2 > N) Make ISO (6 > 1) My removepakgslist is attached. Any ideas what is preventing it coming up clean?
Apply changes to image (5 > 2 > Y) Rebuild (5 > 1) Currently this part should be described like this, Apply and Save changes to image. Then, Optimize (Auto Rebuild) image (5 > 2 > Y)
You're right - updated my method in the above post and have the removed the below: Apply SSU and CU updates (2 > 4 > 2 > 1 > 4) Apply setup media update (2 > 4 > 2 > 2) Rebuild (5 > 1)
Windows Apps are not updated through CU, only Windows Store and Xbox back-end files will be updated but not the App. Rest of the components it shouldn't restore, you can try it.
That's the only one related to Microsoft Account, for testing you can skip the Privacy and Remoting component removal and see if it has anything to do with your problem.
You need specify the CU included with the image? Both MCT/Store ESD images have been sysprep by Microsoft due to which the SFC will show up ghost error. Running the SFC for second time it comes clean.
Skip the PowerShell7 pack and tryout since it was updated recently. Will try with your removal list and report back.
The Toolkit doesn't allow you do the clean if pending.xml is present then how you are getting the error? Source image used ESD/ISO ? If used 19041.1 + updates then did you skipped integrating Edge Chromium?
I can't use cleanup since 19042, but in 19041 everything was fine. This is probably due to the new EdgeChromium. Used 19042.685.201202-1959.20H2_RELEASE_SVC_PROD1_CLIENTMULTI_X64FRE_RU-RU Actions: 1. [7]Tools-[1]WIM Manager[C]-Delete (Removed all editions except Pro) 2. [1]Source-[1]Select Source from <DVD> Folder Do you want to mount Windows Setup Boot Image ? ['Y'es/'N'o] : N Do you want to mount Windows Recovery Image ? ['Y'es/'N'o] : N 3. [2]Integrate-[3]Windows Features-[J]Microsoft Default Metro Apps-[H]Extensions-HEIF, HEVC, MPEG2, VP9, Web, Webp Extensions 4. [2]Integrate-[3]Windows Features-[N]Microsoft Games-[A]All Games 5. [2]Integrate-[4]Windows Updates-[1]Integrate Windows Updates (windows10.0-kb4586876-x64-ndp48) 6. [3]Remove-[3]Remove Windows Components Using Package List-[2]Remove Windows Components Using Package List (ToolKitHelper Method) Spoiler EdgeChromium SecurityCenter StepsRecorder EdgeDevToolsClient Edge OneDrive SmartScreen WindowsDefender WindowsReaderPDF 3DViewer AdvertisingXaml Alarms BingWeather Camera CommunicationsApps Cortana FeedbackHub GetHelp Getstarted Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes WalletService XboxApp XboxIdentityProvider YourPhone 7. [4]Customize-[2]Disable Windows Features using Features List Spoiler MSRDC-Infrastructure WindowsMediaPlayer SmbDirect Internet-Explorer-Optional-amd64 WorkFolders-Client SMB1Protocol-Deprecation 8. [4]Customize-[8]Apply Tweaks-[D]Disable Automatic Downloading and Installing 3rd Party Apps 9. [5]Apply-[1]Cleanup Source Images (No cleaning occurs. If you remove EdgeChromium from the list to be removed, then there is no error, but a notification aboutpending.xml appears and no cleanup occurs) If you skip cleaning and do not use it, then everything works out and there is no damage to the image.
Yes the Edge Chromium package added through the enablement package will trigger the pending.xml and the cleanup is not allowed. Although the Toolkit allows to remove the Edge Chromium package but it won't remove the entire pending.xml file as only the entries related to Edge Chromium are removed. The question is using a 19042 with Edge Chromium and then with or without removing the Edge Chromium with Toolkit should allow the cleanup image operation as with both the conditions the pending.xml is still present. But in your case it is entering the cleanup process then gives the error. Will check what's causing it to allow the cleanup process though it shouldn't have.
Is it possible to clean through CMD? Dism /Image:C:\Toolkit\Mount\Install\1 /Cleanup-Image /StartComponentCleanup /ResetBase
I didn't add any CU. Is there a non-sysprep image I should use instead, or is running SFC twice sufficient to keep it clean?
This will create the same problems. Then no. To put it roughly, a Batch Script is a package that executes commands linearly or not, its commands through CMD. Only this. That is, if it doesn't work by Script, it doesn't work manually. Unless there are typo errors in a command, but only for this purpose, the manual method is used instead of the script. If you test and everything goes well, it is a sign that there is something wrong in the Script. But in this part we believe that there are no errors in the Script. Whenever you have an activity that repeats the same commands, you can create a script for you to avoid these repetitions. It is something complex but after it becomes functional it is pleasant.