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

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

  1. er557

    er557 MDL Member

    Apr 20, 2013
    136
    28
    10
    :roll1:
     
  2. whatever127

    whatever127 MDL PHP Wizard

    Nov 9, 2012
    1,050
    7,345
    60
    19041:
    - Standard 80x25 text mode
    - Standard BIOS font
    - Progress bar does not have shade

    Fixed:
    - 1024x768 resolution used
    - Segoe UI Mono font
    - Progress bar has dark gray shade

    If you boot 19041 without the fix you will get black screen until files are loaded into RAM and then you would get standard Windows flag when it starts booting. Previously the flag was immediately shown without the loading animation until files were loaded.

    If loading files fails in 19041 you will get black screen without any information that something failed. In pre-18990 you would get a blue screen with information.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. windows builder

    windows builder MDL Guru

    Sep 13, 2017
    2,210
    1,539
    90
    is it so important?! :facepalm:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,262
    94,712
    450
    @whatever127, is this only cosmetic, because it installs fine in UEFI non CSM mode?
     
  5. 3zero3

    3zero3 MDL Senior Member

    Apr 26, 2012
    421
    685
    10
    This is technical forum and I like it.
     
  6. whatever127

    whatever127 MDL PHP Wizard

    Nov 9, 2012
    1,050
    7,345
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. er557

    er557 MDL Member

    Apr 20, 2013
    136
    28
    10
    time to resolve uefi issues circa 2021, ms.
     
  8. zig11727

    zig11727 MDL Novice

    Mar 11, 2016
    8
    9
    0
    #608 zig11727, Feb 12, 2020
    Last edited: Feb 12, 2020
    I installed 19041.84 on a separate SSD drive but there are problems the boot problem is fixed with this update when using Dism with /StartComponentCleanup but I now have to re-install mixed reality portal and the .84 update again another problem is Aomei backupper can't restore a system image backup of build 19041.84 it boots to recovery partition when restored.

    After some research I found out the layout of disk is changed with .21 and .84 so most imaging software would restore a system image since the build is not a official release the backupper or true image wouldn't be patched also if this is the final build you can't rollback to 18363 due to the system disk layout is different.
     
  9. er557

    er557 MDL Member

    Apr 20, 2013
    136
    28
    10
    time to move on to macrium reflect
     
  10. Schroedinger2015

    Schroedinger2015 MDL Member

    Jul 16, 2015
    223
    150
    10
    I'm referring to the Motherboard Logo which doesn't appear with 19041 ISOs (I've always used Rufus in order to boot from my USB3 pendrive in a full uefi environment with CSM Disabled and Secure Boot ON),
    while this issue doesn't happen with 18363 ISOs.

    With 19041 Motherboard logo is always replaced by Windows 10 logo, thus it seems it loads like a non-UEFI system.

    Of course, if I upgrade 18363 to 19041 it always boots fine (and I can confirm M$ has fixed the no-boot loop issue with DISM cleanup task).
     
  11. Schroedinger2015

    Schroedinger2015 MDL Member

    Jul 16, 2015
    223
    150
    10
    No, I've used UUPdump script, but I can try with W10UI 8.0 and report feedback.
     
  12. Schroedinger2015

    Schroedinger2015 MDL Member

    Jul 16, 2015
    223
    150
    10
    Thanks mate, your fix makes 19041 install fine in full uefi environment. Now I can see again Motherboard Logo as well as correct text screen. ;)
     
  13. Olliw

    Olliw MDL Member

    Mar 17, 2010
    191
    186
    10
    #613 Olliw, Feb 12, 2020
    Last edited: Feb 13, 2020
    Start menu bugged out first boot after .21 -> .82. Killing the "Start" process fixed it though.
    Still not ready for prime time apperently.
     

    Attached Files:

  14. cuteee

    cuteee MDL Guru

    Oct 13, 2012
    5,730
    982
    180
    19041.41 ?
     
  15. damianfox

    damianfox MDL Senior Member

    Jan 23, 2011
    423
    308
    10
    How are people installing NET35 with this build. Can i just run the DISM online command with the 19H2 image?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,262
    94,712
    450
  17. damianfox

    damianfox MDL Senior Member

    Jan 23, 2011
    423
    308
    10
    Great! Thanks :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. GTK48

    GTK48 MDL Senior Member

    Jun 7, 2009
    306
    111
    10
    MS only fixed what they had to in this release. The Windows Explorer problem is still there.
     
  19. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,262
    94,712
    450