Win 11 Boot And Upgrade FiX KiT (v5.1f Released!!!)

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

  1. MIMMO61

    MIMMO61 MDL Senior Member

    Aug 19, 2009
    372
    107
    10
    For this without autounattend.xml works fine, I use the 24H2b26100.1742 version downloaded MCT
     
  2. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,694
    1,718
    150
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,318
    106,563
    450
    Then it has nothing to do with the subject of this thread, use of autounattended.xml is not part of this tool.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,318
    106,563
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. sonic9

    sonic9 MDL Member

    Aug 4, 2009
    192
    77
    10
    #1486 sonic9, Oct 3, 2024
    Last edited: Oct 3, 2024
    EDIT: Works fine with iso 24H2 IP build .1150
    As said, error is present without AutoUnattended.xml
    I'm keep trying to find root cause.
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,318
    106,563
    450
    Not in this thread please, this is a tool specific thread to discuss and support the tool at the OP.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Alifian

    Alifian MDL Novice

    Sep 2, 2018
    2
    0
    0
    I'm upgrading from Windows 11 23H2 Build 22631.4249
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,318
    106,563
    450
    Then use this info to be able to keep all when upgrading:
    https://forums.mydigitallife.net/posts/1846462

    When it still doesn't work you can use the tool at the OP of that thread.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. sonic9

    sonic9 MDL Member

    Aug 4, 2009
    192
    77
    10
    #1490 sonic9, Oct 3, 2024
    Last edited: Oct 3, 2024
    Seems iso build from uupdump break something , works fine with iso MVS .1742 and IP .1150 even with AutoUnattend.xml
    Thanks for your job.
     
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,318
    106,563
    450
    Could it be caused by an update, integrated by UUP>ISO for the selected build, an update that is not integrated in 26100.1150?

    Download the officially released 1742 ISO and test again.

    And once more, the unattended method is not part of this tool.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. MartinMDL

    MartinMDL MDL Novice

    Dec 13, 2012
    44
    28
    0
    Hi guys...so what i'm trying to do is upgrading from windows 23h2 (22631.4249) to 24h2. Here is what i did step by step.
    1. Downloaded/created an original 24h2 business version ISO
    2. Put said iso into the "source/win11" folder of this toolkit
    3. Ran option 1 and option 2b
    4. The script created a "fixed" ISO.
    5. Mounted said iso by double clicking on it and also wrote it on a USB pen using Rufus v4.5
    6. Either way, by clicking on "setup.exe" inside the mounted iso to start the upgrade process nothing happens.
    What am I doing wrong?

    Pc is an intel i7 4770k CPU with a UEFI Bios with no tpm 2.0 (but that shouldn't really matter since the whole purpose of this toolkit is to bypass those requirements completely).
    Any help is appreciated.
    Thanks
     
  12. MartinMDL

    MartinMDL MDL Novice

    Dec 13, 2012
    44
    28
    0
    hi...i'm getting the exact same behavior as yours and by looking at the logs the error is the same for me as well. Did you manage to find a solution?
     
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,318
    106,563
    450
    #1494 Enthousiast, Oct 3, 2024
    Last edited: Oct 3, 2024
    (OP)
    1. is a separate option on its own.

    2. is split into 2 options, 2a is meant for fixing the ISO and 2b is for editing the current OS registry <=== belong together.

    So either use 1 and upgrade by ISO.

    Or run 2b on the current os and fix the iso by running 2a with the ISO present in the Source\Win11 folder and next mount or extract the ISO to a local folder and run setup.exe
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. flubber2024

    flubber2024 MDL Novice

    Oct 2, 2024
    6
    2
    0
    Just wanted to thanks everyone.

    Today I upgraded 7 old ThinkCentre M900 Tiny computers running Windows 11 23H2 to Windows 11 24H2 using the wonder Bootkit tool. It was so easy.

    I also did a clean install of Windows 11 24H2 onto 3 ThinkCentre M900's. All worked a treat.
     
  15. MartinMDL

    MartinMDL MDL Novice

    Dec 13, 2012
    44
    28
    0
    yes... as i've said i tried all of those but when clicking on "setup.exe" nothing happens...the exact same behavior as the other user.
    By looking at the logs i'm getting his exact error :
    any guess as to what the problem might be?
     
  16. MartinMDL

    MartinMDL MDL Novice

    Dec 13, 2012
    44
    28
    0
    nevermind...fixed the problem and successfully upgraded to 24h2.
     
  17. ederfernandez

    ederfernandez MDL Junior Member

    Oct 26, 2012
    62
    31
    0
    Did you find a solution? Can you help me to solve the issue, I'm still not able to install 24h2.
     
  18. Bat.1

    Bat.1 MDL Expert

    Oct 18, 2014
    1,238
    1,415
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. MartinMDL

    MartinMDL MDL Novice

    Dec 13, 2012
    44
    28
    0
    #1500 MartinMDL, Oct 4, 2024
    Last edited: Oct 4, 2024
    Well...after reading all over the web for that particular error code I found out that it refers to a generic error that WU gives you when there's something not quite right with the OS...no surprise there. In my case the culprit was, probably, some system files that got corrupted during an update or something...because some guy couldn't install a minor update offered through windows update. So what I did was run a basic sfc /scannow command under an elevated command prompt and it found and fixed some files on my system. I then rebooted and mounted a "fixed" business version ISO made by this toolking using option n.1 and ran setup.exe again and it just started normally. I'm pretty sure that was the cause. Hope this helps.