[DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release]

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

  1. Candido

    Candido MDL Novice

    Feb 28, 2020
    19
    9
    0
    #4161 Candido, Aug 27, 2020
    Last edited: Aug 27, 2020
    Wow...has the defrag bug finally been fixed in .487! Am I seeing things?

    • We fixed an issue that causes the Optimize Drives dialog to incorrectly report that previously optimized drives need to be optimized again.

    Seems fixed on my machine.
     
  2. paco77

    paco77 MDL Junior Member

    Nov 25, 2009
    72
    169
    0
    Apparently yep. I just run the defrag tool, rebooted my PC and now seem working ok. It shows the info of last defragmentation
     
  3. SM03

    SM03 MDL Expert

    Dec 16, 2012
    1,405
    605
    60
    Finally, the long-awaited bugfix
    1.png
     
  4. nealcaffrey

    nealcaffrey MDL Novice

    Jun 19, 2015
    16
    6
    0
    #4164 nealcaffrey, Aug 27, 2020
    Last edited: Aug 27, 2020
    Quindi, in sintesi: 19041.450 è l'ultimo ESD rilasciato; 19042.450 è l'ultimo ESD "rilasciato" ma in anteprima (quindi è nel canale Pre-release). Ero tornato nel 1909 all'inizio del 2004 per alcuni problemi qua e là che avevo visto risolti. Se decido di formattare mi consigliate 19041.450 o 19042.450? Grazie ;-)

    Grazie, fa lo stesso :-(
     
  5. TairikuOkami

    TairikuOkami MDL Expert

    Mar 15, 2014
    1,172
    1,055
    60
    Indeed, it looks almost as if MS actually started to care about the user's feedback. :huh:
     
  6. MS_User

    MS_User MDL Guru

    Nov 30, 2014
    4,629
    1,343
    150
    it was about time took then long enough :rolleyes:
     
  7. jcc2

    jcc2 MDL Member

    Mar 23, 2010
    119
    38
    10
    Good day to all and greetings from Lima, Peru....!!!

    Could some of the brilliant minds in the Forum give me a hand on a probably simple thing as follows:

    - Original PC running build 19042.450
    - Downloaded and installed CU kb4571744-x64.cab using DISM and installation was successful, build was now 19042.487 as expected after reboot
    - Downloaded and installed EP kb4562830-x64.cab also using DISM and installation was successful and I was expecting build to be 19042.497after reboot but it stayed at 19042.487

    Could someone give me an idea of what went wrong and how I could try to fix it?

    Many thanks in advance!!!!

    JCC2
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,274
    94,765
    450
    The EP is .479 and the CU is .487. all is ok.

    ps, if you were already on 19042.450 why would you install the 20H2 EP again?
     
  9. jcc2

    jcc2 MDL Member

    Mar 23, 2010
    119
    38
    10
    Many thanks for the prompt reply Enthousiast... I assumed the EP kb4562830-x64.cab also had to be installed as it was new and had a different hash, and it would move the build to 497. As mentioned, DISM installation was succesful but build stayed at 487

    Guess my assumptions wrong. Would I need to do the build change in the registry as with the previous EP?

    JCC2
     
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,274
    94,765
    450
    #4170 Enthousiast, Aug 27, 2020
    Last edited: Aug 27, 2020
    (OP)
    The new EP = .479 not .497 (and is not needed when the old one is already installed)

    And no, only .388 was problematic.
     
  11. jcc2

    jcc2 MDL Member

    Mar 23, 2010
    119
    38
    10
    Sorry for the typo.... Could it be I am becoming dyslexic with age? ;-) ;-) ;-) Guess I was reading 479 and my brain received 497... I do need a drink!!!!

    Many thanks once again and keep up the good job !!!

    JCC2
     
  12. AzimsTech

    AzimsTech MDL Novice

    Mar 17, 2017
    17
    6
    0
    ESENT Event ID 642 warning is still here.
     
  13. moglai

    moglai MDL Junior Member

    Jul 2, 2015
    56
    29
    0
    Is only fixed in the dev. So far
     
  14. cuteee

    cuteee MDL Guru

    Oct 13, 2012
    5,730
    982
    180
  15. erpsterm35

    erpsterm35 MDL Expert

    May 27, 2013
    1,875
    1,749
    60
    and for people who are wondering which files that "fix" the defrag bug, the KB4571744 update includes version 10.0.19041.487 of the defragproxy.dll, defragres.dll & defragsvc.dll files (and I'm one of the very few that actually checked which files were updated by KB4571744)
     
  16. steven4554

    steven4554 MDL Expert

    Jul 12, 2009
    1,429
    2,610
    60
    English Please, and translation below:-
    So in summary: 19041.450 is the last released ESD; 19042.450 is the last ESD "released" but in preview (so it is in the Pre-release channel). I was back in 1909 early 2004 for some problems here and there that I had seen solved. If I decide to format do you recommend 19041.450 or 19042.450? Thanks ;-) Thanks, it's the same
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,274
    94,765
    450
    19042.450 is only IP in name (no auto slow ring enrollment, nor watermark nor an expiration date), but it doesn't get the latest .net cu offered, 19041.450 should.
     
  18. Super Spartan

    Super Spartan MDL Expert

    May 30, 2014
    1,709
    990
    60
    @Enthousiast

    Will my build get updates to the latest official once it's officially out or would I need to format? I installed the 2020-08 Feature Update to Windows 10 Version 20H2 via Enablement Package (KB4562830) followed by KB4571744

    2020-08-28_002332.png
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. EaglePC

    EaglePC MDL Expert

    Feb 13, 2012
    1,147
    471
    60
    Not going to update .487 been reading around the net this update can get your ssd
     
  20. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,274
    94,765
    450
    What is it this time?