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

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

  1. UndertakerBen

    UndertakerBen MDL Member

    Mar 3, 2016
    150
    520
    10
    I can' t boot from 19041.21 ISO for a clean install. There is only the Windows Boot logo with the continuous spinning ring.

    I used "Windows 10 Insider Preview 10.0.19041.21 (vb_release) amd64" in German language
     
  2. er557

    er557 MDL Member

    Apr 20, 2013
    136
    28
    10
    seems we need to maybe rollback to 19h1, and start from square one, maybe going thru some 20h1 insider first. one option is use easeus todo pctrans to migrate to a clean install with all apps intact.
    however, some people have hardware issues even with clean install, like @UndertakerBen
     
  3. 80x86

    80x86 MDL Novice

    Oct 10, 2018
    11
    5
    0
    Same here but another language. Tried both ESD and WIM convertion but no success. Also UEFI/Non-UEFI modes doesn't pass Windows Boot logo.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,299
    450
    x86 19041.21 boots fine but x64 doesn't, tested and reported it last night to @abbodi1406

    x64 19041.1 boot.wim in the same 19041.21 ISO and all boots fine again.

    Tested with en-US and nl-NL.
     
  5. armond

    armond MDL Addicted

    Jun 16, 2008
    736
    235
    30
    So it seams people are having this issues with some Non-EN-US updated ISOs only?
    Updated EN-US X64 ISO works fine for me.
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,299
    450
    I am answering this in 2 different threads, check the other thread.

    Can you show the script settings of W10UI 7.7?
     
  7. armond

    armond MDL Addicted

    Jun 16, 2008
    736
    235
    30
    Sure,
    [W10UI-Configuration]
    target =G:\10ProISO
    repo =
    dismroot =dism.exe

    net35 =1
    net35source =

    cleanup =0
    resetbase =0

    winre =1

    _cabdir =G:\00
    mountdir =G:\11
    winremount =G:\22

    wim2esd =0
    iso =0
    isodir =
    delete_source =0

    autostart =1
    Going to install now.
     
  8. yomoma2

    yomoma2 MDL Senior Member

    Feb 27, 2010
    365
    124
    10
    #350 yomoma2, Jan 15, 2020
    Last edited: Jan 16, 2020
    ̶C̶U̶ ̶.̶2̶1̶ ̶s̶e̶e̶m̶s̶ ̶t̶o̶ ̶h̶a̶v̶e̶ ̶s̶o̶l̶v̶e̶d̶ ̶t̶h̶e̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶l̶y̶ ̶r̶e̶p̶o̶r̶t̶e̶d̶ ̶r̶a̶n̶d̶o̶m̶ ̶B̶S̶O̶D̶s̶ ̶o̶n̶ ̶b̶o̶o̶t̶ ̶I̶ ̶w̶a̶s̶ ̶h̶a̶v̶i̶n̶g̶ ̶o̶n̶ ̶a̶ ̶V̶M̶w̶a̶r̶e̶ ̶V̶M̶ ̶r̶u̶n̶n̶i̶n̶g̶ ̶u̶n̶d̶e̶r̶ ̶a̶ ̶h̶a̶s̶w̶e̶l̶l̶ ̶l̶a̶p̶t̶o̶p̶ ̶h̶o̶s̶t̶.̶
    Bleh, still present.

    Update: And now the VM on the other machine that "was stable" on .1 started to suffer from the same BSOD on boot occasionally after .21 was delivered via WU. Don't know if by coincidence or CU related.
    After uninstalling the update, the problem still seems to remain. Meh.
     
  9. SM03

    SM03 MDL Expert

    Dec 16, 2012
    1,522
    634
    60
    I didn't face any issue with x64 ISO of 19041.1 En-UK in a clean installation. Might be a language-specific issue?
     
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,299
    450
    Yeah, we know it's the cab breaking winre/boot.wim, we'll probably see a new update soon :)
     
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,299
    450
    We are talking about 19041.21 x64.
     
  12. SM03

    SM03 MDL Expert

    Dec 16, 2012
    1,522
    634
    60
    oh ok.
     
  13. MS_User

    MS_User MDL Guru

    Nov 30, 2014
    4,655
    1,361
    150
    no issues for me on .21
     
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,647
    103,299
    450
    Boots fine but at the preparing stage with the logo and the circling circles, it's hangs on it.

    .21 is a no go on x64 ISO :(
     
  15. boyonthebus

    boyonthebus MDL Expert

    Sep 16, 2018
    1,168
    753
    60
    I noticed that when I updated an install.wim from EnterpriseG, but I thought it was just due to it being G.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...