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

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

  1. nosirrahx

    nosirrahx MDL Expert

    Nov 7, 2017
    1,232
    591
    60
    I literally just ran into this. This was an 11th gen laptop that had it enabled without the client knowing. A BIOS update bricked their system since the keys were reset. It blows mind that A) the BIOS does not auto-backup the key or B) the BIOS doesn't refuse to update if bitlocker is enabled.

    Thank god they had a MS account and were able to retrieve the key. Ripped bitlocker right out once back to their desktop.
     
  2. sonic9

    sonic9 MDL Member

    Aug 4, 2009
    151
    54
    10
    #9042 sonic9, Jan 13, 2022
    Last edited: Jan 13, 2022
    same here,
    if i copy from .1466
    \boot
    \efi
    \sources\boot.wim
    \sources\install.wim
    \bootmgr
    \bootmgr.efi
    onto buid .1 iso
    UEFI boot ok in VmWare.
    perhaps W10UI.cmd bug ?

    edit: W10ui with DU Updates excluded , same problem , no uefi boot
     
  3. McLovin

    McLovin MDL Junior Member

    Aug 7, 2009
    95
    27
    0
    can confirm...

    win10 .1466 and win11 .434 (from uupdump)
    will not boot in vmware or ventoy on real hardware.

    Win11 22533 no problems. boots in vmware and ventoy on real hardware

    win10 .1466 and win11 .434 some efi files got other hash as on older builds.
    but a replace from old one to new iso does not solve the problem.

    win10 .1466 and win11 .434 boot/install.wim into .1415 or .376 does boot but does not find
    any harddisk.

    so for me it is only working: win10 .1466 and win11 .434 install.wim into .1415 or .376 and it boots and can be installed
     
  4. TS2008

    TS2008 MDL Junior Member

    Mar 24, 2015
    63
    67
    0
    #9044 TS2008, Jan 13, 2022
    Last edited: Jan 13, 2022
    The UEFI boot problem with the ISO is caused by the ~ \ efi \ microsoft \ boot \ efisys.bin. After the updates have been integrated using the uup dump script, the file appears to be damaged or Microsoft has generally changed something. Without updates, it works as expected.

    To solve the problem, you have to recreate the ISO with efisys.bin (perhaps efisys_noprompt.bin too, if you use it) from the 1415 using cdimage.exe. Then the ISO with the 1466 will boot as expected in UEFI mode.

    BIOS Mode ist not affected.
     
  5. McLovin

    McLovin MDL Junior Member

    Aug 7, 2009
    95
    27
    0
    this method does not work with Windows 11

    if I replace efisys.bin and efisys_noprompt.bin from .376 in .434 I got the same error... ISO does not boot
     
  6. sonic9

    sonic9 MDL Member

    Aug 4, 2009
    151
    54
    10
    #9046 sonic9, Jan 13, 2022
    Last edited: Jan 13, 2022
    @ts21796354 replaced efisys.bin from build .1415 or .1 doesn't work for me on Vmware.
    edit: iso need to be rewriten with cdimage with efi bootdata from efisys.bin

    Works with replace boot.wim + install.wim from build .1466 onto .1 iso build.
     
  7. SM03

    SM03 MDL Expert

    Dec 16, 2012
    1,402
    604
    60
    I faced the same issue yesterday, not running from ventoy, tried updating ventoy plus changing pen drive as well as tested on different machines. Ended up using Rufus to boot the latest v1466 UUPD iso.
     
  8. TS2008

    TS2008 MDL Junior Member

    Mar 24, 2015
    63
    67
    0
    #9048 TS2008, Jan 13, 2022
    Last edited: Jan 13, 2022
    It also works with Windows 11 (22000.434). But after replacing the files you must recreat the ISO with cdimage in order to write the older EFI bootdata in the boot sector of the DVD;

    Code:
    cdimage.exe -bootdata:2#p0,e,b"<path>\boot\etfsboot.com"#pEF,e,b"<path>\efi\Microsoft\boot\efisys.bin" -o -m -u2 -udfver102 -lCPRA_X64FRE_DE-DE_DV5 <path> d:\new.iso
    <path> is the location of the ISO root folder. You must replace it. I testet it with windows 11 (22000.434) and Windows 10 (19044.1466) with efisys.bin from last patch day and with revison 1. Both works finde.

    Alternativ you can use a tool like PowerISO and replace all files from the 1415 ISO with the files from the 1466 ISO (same with Windows 11). Since the older ISO uses the older efisys.bin for the boot sector it works fine.
     
  9. sonic9

    sonic9 MDL Member

    Aug 4, 2009
    151
    54
    10
    works with previous efisys.bin AND cdimage bootdata
    thanks @TS2008
     
  10. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,662
    2,217
    60
    I performed an integration with the Jan 2022 updates overview and the serviced image loads fine on legacy/efi virtualbox and on a real physical machine in legacy/uefi mode(asrock H61 motherboard). With the Dec 2021 updates I had an issue seeing storage drives at the partitioning step in uefi mode(legacy mode had no such issues).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,020
    93,846
    450
  12. sonic9

    sonic9 MDL Member

    Aug 4, 2009
    151
    54
    10
    which method of integration ?
    w10ui ?
     
  13. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,662
    2,217
    60
    w10ui like always. It always worked flawlessly and I had no issues with the iso files. Just the December updates gave me a headache. Now, on 10 21H2 at least, everything works like before.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,020
    93,846
    450
    There were UEFI boot problems with 22000.434 and 19044.1466.
    skipping updating them fixed it.
     
  15. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,662
    2,217
    60
    Ye but that's the thing, I used w10ui and updated everything as before December 2021 - iso boots fine under UEFI and Legacy AND the installer sees all storage drives at partitioning step, whereas before, integrating Dec 2021 updates resulted in iso booting fine in both modes but under UEFI the installer would not see any drives. So, as of now, even without abbodi's mod for skipping updating boot files, everything works fine(for me at least).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,020
    93,846
    450
    Many reported that UEFI boot on vbox and vmware didn't work, on real systems there were mixed results, some had success using rufus but ventoy failed, these are my documented experiences:
    I've used the same always working FAT32 formatted USB as always for testing.
     
  17. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,662
    2,217
    60
    Well, for me: W10UI v10.15 + Jan 2022 updates + latest Ventoy = booting with no issues

    Could there be an issue with half the updates still being Nov 2021? Some mismatching going on?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,020
    93,846
    450
    We'll see when the next release preview updates are released, already announced by @abbodi1406

    as said mixed results on real hardware, on vmware and vbox all couldn't boot 22000.434 ot 19044.1466 when setup as UEFI.

    Not updating the ISO boot files bootx64.efi and efisys.bin seems to have solved it for now.

    22533.1001 doesn't show this behavior so it probably is a glitch with the .434 and .1466 set of updates.