Indeed, it is better to have a pending flag than an SFC error. The pending flag is nothing to worry about, it just won't let you clean the image, and the final ISO size will be slightly larger, it's not critical when .wim is converted to .esd I am very grateful to you for this hint, which will save me from wasting time looking for solutions, since I myself have encountered exactly the same problem at the present time. I usually integrate only a few files to customize the appearance of the OS, and this did not cause any problems. But I needed to disable the automatic start of some Services, I integrated a few tweaks with CurrentControlSet using NTLite, and got an error during the installation phase that looked something like this: "Your PC was rebooted...."
Actually technically the 19042.685 MVS ISO would be best to use for being able to cleanup the image, the latest 20H2 ESDs and TB/MVS ISOs are made from a sysprepped 19042.572 install (iirc) and those won't have the 20H2 EP on "pending install" but "installed". But MSFT forgot to do some cleaning themselves, causing leftover installed drivers and other stuff. The UUP dump or manually updated image will have the 20H2 EP with "pending install", which prevents cleaning up. The cleanup, on the other hand, causes the ghost sfc errors (found errors and repaired by sfc /scannow but no record of it in cbs.log.
Thanks for your reply, one more question: Should I download the newer version that ends in .eappx or ignore the .eappx files? I'm thinking I should download both, for example: "Microsoft.DesktopAppInstaller_2020.1111.2238.0_neutral_~_8wekyb3d8bbwe.BlockMap 12.99 KB Microsoft.DesktopAppInstaller_2020.1111.2238.0_neutral_~_8wekyb3d8bbwe.appxbundle 9.55 MB Microsoft.DesktopAppInstaller_2020.1111.2238.70_neutral_~_8wekyb3d8bbwe.BlockMap 36.52 KB Microsoft.DesktopAppInstaller_2020.1111.2238.70_neutral_~_8wekyb3d8bbwe.eappxbundle 28.03 MB " I couldn't find any information regarding .eappxbundle, are these newer versions dependent on the standard .appxbundle? Can I safely ignore the standard older version ending in .appxbundle if a newer version is an .eappxbundle?, I read that these eappxbundles are encrypted, which is why I ask and I don't know if I need the older version when the newer one uses eappxbundle as part of a dependency. (Since you said I can safely ignore the older versions.) Thanks
bugs: -After selecting source i went to 7 -> 1 and now can't escape for there -When integrating WHD updates it doesn't check the respective folder, when need to move the subfolders out from 10.0.19041 (or similar) to the main folder (since builds don't change for non previews, the folder 10.0.19041 can be hardcoded into the path?)
Hi MSMG and Others Does anyone know what the difference is Old Feature Enablement Pack windows10.0-kb4562830-x64_816fd030691161bfc9f892f0e9e1259e23a56c82 New Feature Enablement Pack windows10.0-kb4562830-x64_93a5c65488affb6e73a0a48ad6a58d8bc1713fd7
@MSMG is there a way to remove edge (chrome version)completely? Also is there a reason powershell cannot be removed I've tried: Code: %DISMX64% /Image:%MOUNT% /Remove-Package /Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64~~10.0.19041.1 %DISMX64% /Image:%MOUNT% /Remove-Package /Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~wow64~~10.0.19041.1 %DISMX64% /Image:%MOUNT% /Remove-Package /Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64~en-GB~10.0.19041.1 %DISMX64% /Image:%MOUNT% /Remove-Package /Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~wow64~en-GB~10.0.19041.1
1) Fixed it, you can close the window and reopen it, the Toolkit will un-mount the mounted images. You can also do the correction to the script using notepad Code: :WIMManager cls echo.=============================================================================== echo. MSMG ToolKit - WIM Manager echo.=============================================================================== echo. :: Checking whether Source is Applied. if "%IsSourceSelected%" equ "Yes" ( echo.Can't use this feature when the Source OS is selected... echo. echo.=============================================================================== echo. pause goto :ToolsMenu ) 2) It's just the typo error in error message, it will be corrected. Code: =============================================================================== MSMG ToolKit - Integrate WHD General Updates to Windows Setup Install Image =============================================================================== WHD General Updates folder <WHD\w10\x64\10.0.19041\Cumulative> is empty... Please copy WHD General Updates to respective folder... =============================================================================== Press any key to continue . . .
You can, just use a 19041.1 image and add the updates using the Integrate WHD Updates menu and when asked "Do you want to skip integrating Edge Chromium", choose yes it will remove the Edge Chromium packages while integrating the Enablement package. You can remove PowerShell but I just don't do it.
Edge: so use 20H2 v1 and not v2? Or are you meaning 2004? Powershell: how do you remove powershell? I've tried with dism doesn't work. do you have removal already built in to toolkithelper?
No, the option Integrate .NET Framework 3.5 (Windows converter only) was not selected. Based on what you have said, it seems it is better to live with the Pending.xml bugs. I am frustrated at myself for not spotting this earlier.
Use 20H1 (2004) 19041.1 + latest SSU + CU + 19042 Enablement Package = 19042 (20H2) You need to use the Toolkit's WHD Update Pack integration menu and choose Skip integrating Edge Chromium when asked. I haven't removed but you can remove it, the below package just adds the PowerShell GUI Editor and not the PowerShell it self. Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35 These are the other packages related to PowerShell Code: HyperV-Host-Compute-PowerShell-Module-merged-Package~31bf3856ad364e35~ HyperV-Host-Compute-PowerShell-Module-Package~31bf3856ad364e35~ Microsoft-Windows-msmq-powershell-Opt-Package~31bf3856ad364e35~ Microsoft-Windows-msmq-powershell-Opt-WOW64-Package~31bf3856ad364e35~ Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~ Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~
It's not a bug but rather it is the way some Windows packages are staged to be installed at first boot. You can avoid this by using 19041.1 ISO + latest SSU + CU + 19042 Enablement Package = 19042 (20H2) You need to use the Toolkit's WHD Update Pack integration menu and choose Skip integrating Edge Chromium when asked. This will allow to do the cleanup and again doing it will cause the Ghost SFC error.