Hi, I had the same “Error 13” trying to update with DISM from 19042.630 to 19042.661, I solved with this: 1.- Uninstall the KB4562830 (Enablement Package) update and restart windows. The system will back to Build 2004. 2.- You need the ISO 20H2 19042.508 or the latest 19042.630 3.- Now deploy the ISO and start the setup.exe and perform an Inplace Upgrade repair as usual. (Obviously keeping personal files and apps) 4.- After the Inplace Update, go through Windows Update once. 5.- OPTIONAL: After that, the KB4577586 must be reinstalled to remove the Adobe Flash Player. 6.- Now you can install the cab updates normally without the Error 13. I hope It helps.
Successfull online update from 19042.630 to 19042.631 on X86 and X64 Windows 20H2 Enterprise when applying the cab files mentioned by @abbodi1406.
Same, no resetbase, I tried cleanups, reset windows update, etc and no luck, I restored an image from a month ago and the update still failed, so I restored an image from 2 months ago and it finally installed. This happens like once/twice a year.
With a 19042.661 ISO you can simply do an inplace upgrade to get a pre-pre-pre-preview update from the internal channels, not even release preview, update installed.
I'm not sure you needed to go through all those steps to solve the "Error 13" issue. I think that taking ownership of the EditionVersion key and modifying the sub-keys to reflect 19041.488 would have been sufficient to enable an in-place repair with a 19042.508 or 19042.572 ISO. Once the repair is done, you can run an SFS /SCANNOW and then do your Windows Update to get to 630. After that, you could manually apply one of the 661 Updates. I did this a couple of days ago.
Bizarre Uninstall of 661: There are two 661 updates: 19041.661.1.7 and 19041.661.1.8. I applied both updates v7 and then v8 in succession. Then I decided to uninstall 661 to prepare for patch Tuesday. The uninstall was interesting because there was only one entry in the Windows Update uninstall list for KB4586853 (661). I uninstalled that entry, it didn't demand a reboot, but I rebooted anyway. I ran winver and it still reported version 19042.661. So I looked at the Windows Update uninstall list again and, to my astonishment, there it was again: KB4586853! So it occurred to me that there was one entry, but two installs of 661. I had only rolled back from v8 to v7. So I uninstalled KB4586853 again. This time it took longer and demanded a reboot. After the reboot, winver reported 19042.630 and KB4586853 was gone from the Windows Update uninstall list. 19042.630 is copacetic now.
If when creating an image I choose to remove boot.wim 1. Microsoft Windows PE (x64) should I still integrate the SafeOS DU?
So you are puzzled that you see one entry for KB4586853, and not puzzled for not seeing KB4586781 beforehand? all Cumulative Updates are chained by CBS name "Package_for_RollupFix" therefore, they all are versions of the same package/update (regardless of multiple versions for same KB), and you will always see one of them, the latest/higher version think of it like Win7 Appraiser KB2952664, which got nearly 32 versions try to uninstall those one by one
I do not recall if KB4586781 was visible or not prior to uninstall of KB4586853. I was not paying attention to that. But I was suspicious of KB4586853 being used twice due to the way WinVer reported the version number. As for Win7 Appraiser KB2952664, I found this update suspect and blocked it's install everytime. MSFT can manage updates however they want. But using the same KB for multiple updates seems like it could be misleading, especially if one is not aware of how the KB numbers are being used. In your case, you appear to be aware, and I appreciate you sharing that information with me.
In fact, at first I thought I would do it, but I couldn't find ISO 19042.661. Thanks, the problem is solved anyway.
That would be up to you to create. To get back at this, after a cleanup , the uninstall option is no longer available, that's why i created the fix.
Patch released on the Update Catalogue for 1809. It just fixes Kerberos authentication issues caused by the November security update.
Out-of-band means an emergency fix, released out of the usual cadence. MS doesn't want to do this unless they have to. PR nightmare.