Win 11 Boot And Upgrade FiX KiT

Discussion in 'Windows 11' started by Enthousiast, Jun 28, 2021.

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    And now you mention it, when it (almost) is released, i thought it was using option 2 from the 2.0 release, now option 2 again in v3.0, using the old boot.wim registry fix you needed to use.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    5,776
    6,352
    180
    Indeed, it is option 2 from 2.1. I did use this one, but it alone didn't work for my old VBox, it blocked nonetheless. Thus, I have also integrated the winsetup.dll patcher from @AveYo. No big deal, I'll just modify the code again.
     
  3. scaramonga

    scaramonga MDL Senior Member

    Oct 27, 2012
    420
    252
    10
    Thanking you kindly Enthousiast.
     
  4. jimt-47

    jimt-47 MDL Novice

    Dec 3, 2022
    13
    0
    0
    ------------

    Never mind! I used the new fix and it is now updated
     
  5. jimt-47

    jimt-47 MDL Novice

    Dec 3, 2022
    13
    0
    0

    Never mind! I used the new fix and it is now updated THANKS!!!
     
  6. WindowsGeek

    WindowsGeek MDL Expert

    Jun 30, 2015
    1,351
    361
    60
    I just tested V 3.0 and works well thank you:)
     
  7. maxama123

    maxama123 MDL Senior Member

    Oct 22, 2009
    455
    158
    10
    #1007 maxama123, Dec 7, 2022
    Last edited: Dec 7, 2022
  8. snofte

    snofte MDL Member

    Jan 10, 2013
    152
    27
    10
    In process of upgrading some family and friend-pcs( =oldies) to win 11 22h2 on legacy mbr pc`s.
    Some have win 10, some have win 11 21h2 (=upgraded ok last spring with the fixing tool, no problems then)
    Have tried the new 3.0 fixing-version for further upgrade to 22h2.
    Running fix-kit, producing a FIXED-22h2- iso. No problem. Used option 3.
    Running setup from the fixed iso:
    Upgrade from either w10 or w11-21h2 aborts after second boot.
    (DPC watchdog violation). Selected keep files and apps for the upgrade.
    In all these cases I had to upgrade drivers for either the win 10 or the win11-21h2
    before running the fix-kit, Always ok upgrade then.
    So it seems ver 2 fix-kit with 21h2 in fix-kit source and old drivers on windows-drive, always ok
    ver 3 fix-kit with 22h2 in fix-kit source and old drivers on windows-drive, always abort.
    ver 3 fix-kit with 22h2 in fix-kit source and NEW drivers on windows-drive, altways ok.
    Cannot understand why 22h2 is more demanding than 21h2, Can anyone explain `?
    It would of course be great if the fix-kit could install new drivers while generating the FIXED iso.
    But thats probably to wish for too much. But maybe this problem could be explained in the READ.ME?

    BTW, another problem:
    For clean installs of win11-22h2 on formated hdd (yes, for some oldies I had to clean out everything) ,
    I generated i Rufus-bootable usb-stick with a FIXED win11-22h2 on it.
    Booted ok, going through all stages, restart, "installing" etc. then abort.
    Seems the upgrade-windows look like a normal windows-install with dark blue opening windows.
    Not the different light blue windows opening-window (Windows server) when running setup from the fixed iso.
    Do I have a wrong setup in my Rufus, or what ?
     

    Attached Files:

  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    @snofte, to me it seems non of this has to do with the Fixed ISO, but when version 2.2 option 2 worked fine why did you now use option 3? Option 1 is now what before was option 2 (the one you used successfully before).

    Is rufus set to integrate it's own fix, looks like it?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Dark Dinosaur

    Dark Dinosaur X Æ A-12

    Feb 2, 2011
    2,475
    3,002
    90
    work well .. time to get rid of old v2.2 file
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    Why would a copy with code i can't maintain and not really needed make the original subject of this thread less working?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Dark Dinosaur

    Dark Dinosaur X Æ A-12

    Feb 2, 2011
    2,475
    3,002
    90
    I am talking about your version :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Muggaen

    Muggaen MDL Addicted

    Dec 30, 2011
    563
    230
    30
    I havent tried the new tool my self but if I understand you right I have always used option 2 in the old tool v.2.2 so for future I shall use option 1 in v 3.0 is that right?
     
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    Yes, option 2 from <v3.0 = option 1 (recommended option) on v3.0
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. snofte

    snofte MDL Member

    Jan 10, 2013
    152
    27
    10
    Re. ver 2.2 ver. 3:: I am afraid I might have explained the problem poorly.
    To clearify:
    In all of the aborted cases, I always must update drivers beforehand.
    That goes for 22h2, both on ver 2.2 and 3.0
    The only luck I had is with 21h2. Never problem with that one.
    Does it make any sense that MS has made driver update mandatory for 22H2 ?

    Re. rufus. Yes, it seems rufus has it own fixing system. Will try newer version as suggested by Errepublica.
    But can anyone suggest an alternative system for creating a bootable usb-stick with win11 22h2
    for clean install on formatted blank disk ?
     
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    The subject of this thread is a tool that only skips the minimum system requirement checks at setup for TPM, RAM, Disksize and Secureboot, when that is skipped the problem is not related to this tool and its purpose.

    I never use rufus or any tool for that matter to create a simple FAT32 USB drive and it is capable of booting UEFI and Legacy BIOS systems.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. Mellipes

    Mellipes MDL Senior Member

    Jun 17, 2021
    288
    170
    10
    First I have heard of it (BUT nothing M$ does surprises me anymore). If it is a driver issue, it may be a specific driver that is the problem, and not drivers in general. ie say a specific video driver for a specific chipset. Who knows, but I cant imagine 22H2 nor have seen any examples that 22H2 needs ALL THE LATEST DRIVERS.
     
  18. stemic28

    stemic28 MDL Member

    Aug 23, 2009
    246
    281
    10
    May I ask what is the way for ISO images larger than 4.7 GB? I would now only think of Diskpart for ISOs with ESD that are smaller than 4.7 GB