Just performed some tests on my system, as I ran into the same issue when trying to update from .145 to .175 on an online system. Base ISO 18362.1 -> W10UI update to .145 with Reset Image Base = YES -> mount .145 and integrate .175 offline -> error 0x800f0988 Base ISO 18362.1 -> W10UI update to .145 with Reset Image Base =NO -> mount .145 and integrate .175 offline -> update successful! Perhaps I missed something, but are we not allowed to use "/ResetBase" anymore?
I do not have problem. Code: F:\temp>DISM /mount-wim /wimfile:install.wim /index:1 /mountdir:mount Deployment Image Servicing and Management tool Version: 10.0.18362.1 Mounting image [==========================100.0%==========================] The operation completed successfully. F:\temp>dism /Image:"mount" /Add-Package /PackagePath:"windows10.0-kb4498523-x64.cab" Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package Package_for_KB4498523~31bf3856ad364e35~amd64~~18362.144.1.1 [==========================100.0%==========================] The operation completed successfully. F:\temp>dism /Image:"mount" /Add-Package /PackagePath:"Windows10.0-KB4497935-x64.cab" Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.30 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.145.1.6 [==========================100.0%==========================] The operation completed successfully. F:\temp>dism /Image:"mount" /Cleanup-Image /StartComponentCleanup /ResetBase Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.145 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. F:\temp>dism /Image:"mount" /Add-Package /PackagePath:"Windows10.0-KB4503293-x64.cab" Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.145 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.175.1.6 [==========================100.0%==========================] The operation completed successfully. F:\temp>dism /Image:"mount" /Cleanup-Image /StartComponentCleanup /ResetBase Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.175 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. F:\temp>DISM /unmount-wim /mountdir:mount /commit Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image File : F:\temp\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. F:\temp>pause Press any key to continue . . .
@Krakatoa did you enable resetbase in the registry first? If i understand correctly, he is using W10UI and it has a workaround for performing a full resetbase, when selected.
OK. I thought by error message (PSFX_E_INVALID_DELTA_COMBINATION) that he used DELTA compression (not deleting old files) and I use /ResetBase also on DELTA compression. With full resetbase (deleting files) I had problem sometime last year and I prefer not to use "full" resetbase.
I think it's because in 1903, only the CU packages is changed, but rest(SSU,.net,flash) are still using same structure as before, so like previous versions they still need resetbase to get cleaned up.
Since you wrote the W10UI script ;-) Do you have an idea what's causing the issue with error 0x800f0988, when using the script option 'Reset Base'? It must be something in the script, because Krakatoa could not reproduce it when manually stacking updates with resetbase. Steps for reproducing (on clean ISO): Base ISO 18362.1 -> W10UI update to .145 with Reset Image Base = YES -> mount .145 and integrate .175 offline -> error 0x800f0988 Base ISO 18362.1 -> W10UI update to .145 with Reset Image Base = NO -> mount .145 and integrate .175 offline -> update successful!
Krakatoa did a manual resetbase, when he didn't enable resetbase in the registry, he only actually performed a standard /startcomponentcleanup and not the resetbase. MSFT disabled resetbase for a reason, before it was that it broke resetpc, now it causes more problems, just use cleanup system image.
Ah, right. Thanks for clearing that up! Now I just need to make sure I never accidentally perform a resetbase again
When using W10UI to integrate updates on a clean 1809 LTSC iso, should I integrate all SSU's or just the latest + all CU? Does the latest SSU include all the fixes from previous?
You only need these updates for 1809: https://forums.mydigitallife.net/th...16-379-437-pc-rs5.77945/page-216#post-1490183
Thank you! I didn't realise they were on that page So when I do an update from clean 1809, I only need to integrate those updates listed in your post and prior SSU/CU are included in the latest? I've been updating my clean iso image with all the CU's... no wonder its been taking so long!