Windows 10 Hotfix Repository

Discussion in 'Windows 10' started by Tito, Oct 1, 2014.

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    32,269
    51,214
    450
    Resetbase never was a good solution for this problem, most likely these errors are caused by cleanups of any kind.

    As you can see, msft did "release" 2 updates with the same name/kb, those are never good to use if you want to stay safe, just wait till next week, when the quality only updates normally are released.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. bonesz

    bonesz MDL Senior Member

    Jun 30, 2013
    406
    221
    10
    Will do and thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. paco77

    paco77 MDL Novice

    Nov 25, 2009
    49
    159
    0
    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.
     
  4. wpuser

    wpuser MDL Novice

    Sep 18, 2014
    15
    10
    0
    Me too. I never did a resetbase :(
     
  5. rpo

    rpo MDL Expert

    Jan 3, 2010
    1,138
    947
    60
    Successfull online update from 19042.630 to 19042.631 on X86 and X64 Windows 20H2 Enterprise when applying the cab files mentioned by @abbodi1406.
     
  6. TairikuOkami

    TairikuOkami MDL Expert

    Mar 15, 2014
    1,005
    867
    60
    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.
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    32,269
    51,214
    450
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. donmiller

    donmiller MDL Senior Member

    Jun 4, 2016
    290
    165
    10
    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.
     
  9. donmiller

    donmiller MDL Senior Member

    Jun 4, 2016
    290
    165
    10
    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! :wha:

    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.
     
  10. Windows 10 User

    Windows 10 User MDL Expert

    Feb 2, 2017
    1,189
    72
    60
    If when creating an image I choose to remove boot.wim 1. Microsoft Windows PE (x64) should I still integrate the SafeOS DU?
     
  11. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    11,259
    48,604
    340
    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 :)
     
  12. donmiller

    donmiller MDL Senior Member

    Jun 4, 2016
    290
    165
    10
    #11193 donmiller, Nov 14, 2020
    Last edited: Nov 14, 2020
    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.
     
  13. paco77

    paco77 MDL Novice

    Nov 25, 2009
    49
    159
    0
    In fact, at first I thought I would do it, but I couldn't find ISO 19042.661. Thanks, the problem is solved anyway.
     
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    32,269
    51,214
    450
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. oilernut

    oilernut MDL Senior Member

    Jul 8, 2007
    340
    276
    10
    Patch released on the Update Catalogue for 1809. It just fixes Kerberos authentication issues caused by the November security update.
     
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    32,269
    51,214
    450
    #11197 Enthousiast, Nov 17, 2020
    Last edited: Nov 17, 2020
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. spedia

    spedia MDL Senior Member

    Jul 13, 2009
    271
    96
    10
    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.
     
  18. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    32,269
    51,214
    450
    #11200 Enthousiast, Nov 19, 2020
    Last edited: Nov 19, 2020
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...