[DISCUSSION] Windows 10 Final Build 19041/2/3 (PC) [20H1/2 / 21H1 vb_release]

Discussion in 'Windows 10' started by Enthousiast, Dec 10, 2019.

  1. WindowsGeek

    WindowsGeek MDL Expert

    Joined:
    Jun 30, 2015
    Messages:
    1,082
    Likes Received:
    239
    Trophy Points:
    60
    Hopefully 21H1 will be in the beta channel soon.
     
  2. cuteee

    cuteee MDL Guru

    Joined:
    Oct 13, 2012
    Messages:
    5,013
    Likes Received:
    775
    Trophy Points:
    180
    20H2 and Edge canary have the same number :
    19042.782
    90.0.782
     
  3. luzea

    luzea MDL Expert

    Joined:
    Apr 25, 2019
    Messages:
    1,003
    Likes Received:
    1,776
    Trophy Points:
    60
  4. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,638
    Trophy Points:
    450
  5. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,638
    Trophy Points:
    450
    #6165 Enthousiast, Feb 2, 2021
    Last edited: Feb 2, 2021
    (OP)
  6. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,638
    Trophy Points:
    450
  7. SM03

    SM03 MDL Expert

    Joined:
    Dec 16, 2012
    Messages:
    1,067
    Likes Received:
    527
    Trophy Points:
    60
    tried updating from v19041.782 to this latest v19041.789 in two systems, both failed after 30% (in post) with error 0x80070005

    After that, also tried the same with the official MSU package, same result

    did anyone face this same?
     
  8. cuteee

    cuteee MDL Guru

    Joined:
    Oct 13, 2012
    Messages:
    5,013
    Likes Received:
    775
    Trophy Points:
    180
  9. vip3371

    vip3371 MDL Novice

    Joined:
    May 22, 2018
    Messages:
    15
    Likes Received:
    7
    Trophy Points:
    0
    There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800705b4)
     
  10. WindowsGeek

    WindowsGeek MDL Expert

    Joined:
    Jun 30, 2015
    Messages:
    1,082
    Likes Received:
    239
    Trophy Points:
    60
    Updated to .789 with out any issues.
     
  11. erpsterm35

    erpsterm35 MDL Expert

    Joined:
    May 27, 2013
    Messages:
    1,153
    Likes Received:
    761
    Trophy Points:
    60
    no problems on my end.
    I ended up removing .782 and then updating to .789 on one of my PCs running v2004 with the official msu package
     
  12. Mišulda

    Mišulda MDL Novice

    Joined:
    Jul 1, 2014
    Messages:
    31
    Likes Received:
    11
    Trophy Points:
    0
    #6172 Mišulda, Feb 3, 2021
    Last edited: Feb 3, 2021
    [ATTACH = plný] 54033 [/ ATTACH]
     

    Attached Files:

  13. SM03

    SM03 MDL Expert

    Joined:
    Dec 16, 2012
    Messages:
    1,067
    Likes Received:
    527
    Trophy Points:
    60
    you removed 782, so you updated from 746 to 789?
     
  14. ohenry

    ohenry MDL Member

    Joined:
    Aug 10, 2009
    Messages:
    133
    Likes Received:
    63
    Trophy Points:
    10
    I just updated from 746 to 789, using the regular Windows update function. Everything went very smoothly except ...(you knew there was going to be a "but", right? (smile)

    Immediately after installing and rebooting, I ran WinVer and verified 789. While looking at that, I got the little popup in the bottom right corner saying I needed to reboot to install updates. So I did, and it appeared to be doing something. Didn't take long, still says 789, all is good. At least I hope it is!
     
  15. baguettez

    baguettez MDL Novice

    Joined:
    Dec 13, 2016
    Messages:
    23
    Likes Received:
    3
    Trophy Points:
    0
  16. nosirrahx

    nosirrahx MDL Addicted

    Joined:
    Nov 7, 2017
    Messages:
    873
    Likes Received:
    396
    Trophy Points:
    30
  17. baguettez

    baguettez MDL Novice

    Joined:
    Dec 13, 2016
    Messages:
    23
    Likes Received:
    3
    Trophy Points:
    0
    #6177 baguettez, Feb 4, 2021
    Last edited: Feb 5, 2021
    Guess I'll just wait. I've checked for component store corruption but didn't find any. First time that I ran into this error.

    Unless there's something else I can try to "fix it"
     
  18. donmiller

    donmiller MDL Addicted

    Joined:
    Jun 4, 2016
    Messages:
    518
    Likes Received:
    323
    Trophy Points:
    30
    Did you have KB4598299 installed BEFORE you transitioned from 746 to 789? If not, Windows Update may have been updating to KB4598299 (.Net Framework) after the 746 to 789 update.
     
  19. donmiller

    donmiller MDL Addicted

    Joined:
    Jun 4, 2016
    Messages:
    518
    Likes Received:
    323
    Trophy Points:
    30
    If you were on 746 before trying to update to 789, you shouldn't need a new SSU. The 746 SSU works fine with the 789 LCU. It sounds like something else is broken. Perhaps a problem with Windows Update. Have you tried using DISM to manually apply the 789 LCU?
     
  20. SAM-R

    SAM-R MDL Guru

    Joined:
    Mar 21, 2015
    Messages:
    4,836
    Likes Received:
    4,443
    Trophy Points:
    150
    rcstar6696
    Is there any update as to when Insiders will start getting 21H1 Builds ?