Windows 11 Hotfix Repository

Discussion in 'Windows 11' started by Tito, Jul 1, 2021.

Tags:
  1. Outcast

    Outcast MDL Member

    Mar 23, 2009
    207
    166
    10
    #1341 Outcast, Jan 6, 2023
    Last edited: Jan 6, 2023
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,365
    73,919
    340
    :dunno:

    you can try /discard instead /commit to revert changes
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    #1343 Enthousiast, Jan 6, 2023
    Last edited: Jan 6, 2023
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    14,365
    73,919
    340
    Why?
    depending on the usual weird dism percentage, i don't think so :)

    /ResetBase command itself is never disabled
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    I remember it was disabled and you needed to set some regkeys to be able to run real /resetbase (it actually only ran /startcomponentcleanup)?

    I asked because msft advises to run it after updates integration is done in winre.

    On 11 it is sufficient to only integrate ssu + lcu (no du for safeos needed)?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
    Windows 10:
    winre.wim - SSU+DU
    boot.wim - SSU+EP+LCU

    Windows 11:
    winre.wim - SSU+DU+LCU
    boot.wim - SSU+EP+LCU (+General update for Dev channel)
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    I should pay attention at what i post at the checksum / media content posts:D

    Noticed i didn't put them in since 22621.525, fixed for .963:)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. gjohnson5

    gjohnson5 MDL Junior Member

    Jul 25, 2013
    50
    25
    0
    I thought resetbase was disabled as per the below old post

     
  10. gjohnson5

    gjohnson5 MDL Junior Member

    Jul 25, 2013
    50
    25
    0
    Didn't even know what spoiler was until I googled it

    I see there's a code box as well.

    Anyway Corrected
     
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    #1351 Enthousiast, Jan 6, 2023
    Last edited: Jan 7, 2023
    Code:
    Microsoft Windows [Version 10.0.22621.963]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\Windows\System32>md c:\mount
    
    C:\Windows\System32>ReAgentC.exe /mountre /path c:\mount
    REAGENTC.EXE: Operation Successful.
    
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021255-x64_LCU_963.1.8.msu" /PackagePath:"C:\Winre\windows11.0-kb5021041-x64_DU_SafeOS_815.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 - Adding package Package_for_KB5021041~31bf3856ad364e35~amd64~~22621.815.1.0
    [==========================100.0%==========================]
    Processing 1 of 1 -
    [===========================80.0%==============            ]
    [==========================100.0%==========================]
    Error: 1726
    
    The remote procedure call failed.
    An error occurred closing a servicing component in the image.
    Wait a few minutes and try running the command again.
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    C:\Windows\System32>Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.963
    
    [=====                      10.0%                          ]
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>ReAgentC.exe /unmountre /path c:\mount /discard
    REAGENTC.EXE: Operation failed: c1420117
    
    REAGENTC.EXE: An error has occurred.
    
    
    C:\Windows\System32>
    Code:
    Microsoft Windows [Version 10.0.22621.963]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\Windows\System32>md c:\mount
    
    C:\Windows\System32>ReAgentC.exe /mountre /path c:\mount
    REAGENTC.EXE: Operation Successful.
    
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\SSU-22621.898-x64.cab" /PackagePath:"C:\Winre\windows11.0-kb5021255-x64_LCU_963.1.8.msu" /PackagePath:"C:\Winre\windows11.0-kb5021041-x64_DU_SafeOS_815.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 2 - Adding package Package_for_ServicingStack_898~31bf3856ad364e35~amd64~~22621.898.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_898 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    Processing 1 of 2 - Adding package Package_for_ServicingStack_898~31bf3856ad364e35~amd64~~22621.898.1.1
    [==========================100.0%==========================]
    Processing 2 of 2 - Adding package Package_for_KB5021041~31bf3856ad364e35~amd64~~22621.815.1.0
    [==========================100.0%==========================]
    Processing 1 of 1 -
    [===========================80.0%==============            ]
    [==========================100.0%==========================]
    Error: 1726
    
    The remote procedure call failed.
    An error occurred closing a servicing component in the image.
    Wait a few minutes and try running the command again.
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    C:\Windows\System32>
    
    When first installing the SSU separately (extracted from catalog MSU) and next LCU and last the DU for SafeOS (in this exact order), no installing errors but still errors during unmounting and committing
    Code:
    Microsoft Windows [Version 10.0.22621.963]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\Windows\System32>md c:\mount
    
    C:\Windows\System32>ReAgentC.exe /mountre /path c:\mount
    REAGENTC.EXE: Operation Successful.
    
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\SSU-22621.898-x64.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_898~31bf3856ad364e35~amd64~~22621.898.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_898 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021255-x64_LCU_963.1.8.msu"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 -
    [===========================80.0%==============            ]
    [==========================100.0%==========================] The operation completed successfully.
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021041-x64_DU_SafeOS_815.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.963
    
    Processing 1 of 1 - Adding package Package_for_KB5021041~31bf3856ad364e35~amd64~~22621.815.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.963
    
    [=====                      10.0%                          ]
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>ReAgentC.exe /unmountre /path c:\mount /commit
    REAGENTC.EXE: Operation failed: 70
    
    REAGENTC.EXE: An error has occurred.
    
    
    C:\Windows\System32>
    
    Leaving out the DU for Sources, also error during unmounting:
    Code:
    Microsoft Windows [Version 10.0.22621.963]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\Windows\System32>md c:\mount
    
    C:\Windows\System32>ReAgentC.exe /mountre /path c:\mount
    REAGENTC.EXE: Operation Successful.
    
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\SSU-22621.898-x64.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_898~31bf3856ad364e35~amd64~~22621.898.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_898 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021255-x64_LCU_963.1.8.msu"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 -
    [===========================80.0%==============            ]
    [==========================100.0%==========================] The operation completed successfully.
    
    C:\Windows\System32>Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.963
    
    [=====                      10.0%                          ]
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>ReAgentC.exe /unmountre /path c:\mount /commit
    REAGENTC.EXE: Operation failed: 70
    
    REAGENTC.EXE: An error has occurred.
    
    
    C:\Windows\System32>
    
    When i leave out the LCU entirely all goes well (and winre.wim still is updated to 22621.963):
    Code:
    Microsoft Windows [Version 10.0.22621.963]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\Windows\System32>md c:\mount
    
    C:\Windows\System32>ReAgentC.exe /mountre /path c:\mount
    REAGENTC.EXE: Operation Successful.
    
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\SSU-22621.898-x64.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_898~31bf3856ad364e35~amd64~~22621.898.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_898 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021041-x64_DU_SafeOS_815.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 - Adding package Package_for_KB5021041~31bf3856ad364e35~amd64~~22621.815.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.963
    
    [=====                      10.0%                          ]
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>ReAgentC.exe /unmountre /path c:\mount /commit
    REAGENTC.EXE: Operation Successful.
    
    
    C:\Windows\System32>
    
    All tests are performed on clean 22621.963 clones (22621.525 online updated to 22621.963 by W10UI_v25).

    ps, can the above situation be related to the fact that for beta/rp channel updates a third party script is needed to create the PSFX LCU and thus the LCU is not needed for online winre.wim updating?

    Working:
    Code:
    md c:\mount
    ReAgentC.exe /mountre /path c:\mount
    Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\SSU-22621.898-x64.cab"
    Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021041-x64_DU_SafeOS_815.cab"
    Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
    ReAgentC.exe /unmountre /path c:\mount /commit
    rd c:\mount
    
    These updates are available and working at/from UUP (dump) system.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
    #1352 Paul Mercer, Jan 7, 2023
    Last edited: Jan 7, 2023
    I was trying this on my 22621.963 main system and I forgot that I can't install updates after SSU in the same DISM session
    After I've got an error I can no longer run ReAgentC.exe from Windows Terminal lol, but it still works from elevated CMD

    in the end this is working fine for me in elevated CMD (not Windows Terminal):
    Code:
    md f:\mount
    ReAgentC.exe /mountre /path f:\mount
    Dism /Add-Package /Image:f:\mount\ /PackagePath:"D:\Downloads\111\SSU-22621.898-x64.cab"
    Dism /Add-Package /Image:f:\mount\ /PackagePath:"D:\Downloads\111\windows11.0-kb5021041-x64_DU.SafeOS_815.1.0.cab"
    Dism /Add-Package /Image:f:\mount\ /PackagePath:"D:\Downloads\111\windows11.0-kb5021255-x64_LCU_963.1.8.msu"
    Dism /image:f:\mount /cleanup-image /StartComponentCleanup /ResetBase
    ReAgentC.exe /unmountre /path f:\mount /commit
    Code:
    Microsoft Windows [Version 10.0.22621.963]
    (c) Корпорация Майкрософт (Microsoft Corporation). Все права защищены.
    
    C:\Windows\System32>md f:\mount
    
    C:\Windows\System32>ReAgentC.exe /mountre /path f:\mount
    REAGENTC.EXE: операция выполнена успешно.
    
    
    C:\Windows\System32>Dism /Add-Package /Image:f:\mount\ /PackagePath:"D:\Downloads\111\SSU-22621.898-x64.cab"
    
    Cистема DISM
    Версия: 10.0.22621.1
    
    Версия образа: 10.0.22621.819
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_898~31bf3856ad364e35~amd64~~22621.898.1.1
    [==========================100.0%==========================]
    Сообщение, отправленное на сокет датаграмм, было больше, чем буфер внутренних сообщений или был превышен иной сетевой параметр. Также возможно, что буфер для принятия сообщения был меньше, чем размер сообщения.
    Операция успешно завершена.
    
    C:\Windows\System32>Dism /Add-Package /Image:f:\mount\ /PackagePath:"D:\Downloads\111\windows11.0-kb5021041-x64_DU.SafeOS_815.1.0.cab"
    
    Cистема DISM
    Версия: 10.0.22621.1
    
    Версия образа: 10.0.22621.819
    
    Processing 1 of 1 - Adding package Package_for_KB5021041~31bf3856ad364e35~amd64~~22621.815.1.0
    [==========================100.0%==========================]
    Операция успешно завершена.
    
    C:\Windows\System32>Dism /Add-Package /Image:f:\mount\ /PackagePath:"D:\Downloads\111\windows11.0-kb5021255-x64_LCU_963.1.8.msu"
    
    Cистема DISM
    Версия: 10.0.22621.1
    
    Версия образа: 10.0.22621.819
    
    Processing 1 of 1 -
    [===========================80.0%==============            ]
    [==========================100.0%==========================] Операция успешно завершена.
    
    C:\Windows\System32>Dism /image:f:\mount /cleanup-image /StartComponentCleanup /ResetBase
    
    Cистема DISM
    Версия: 10.0.22621.1
    
    Версия образа: 10.0.22621.963
    
    [=====                      10.0%                          ]
    [==========================100.0%==========================]
    Операция успешно завершена.
    
    C:\Windows\System32>ReAgentC.exe /unmountre /path f:\mount /commit
    REAGENTC.EXE: операция выполнена успешно.
    
    
    C:\Windows\System32>

    in conclusion:
    1. make sure your recovery partition size is not too small, anyway you can resize it using any disk manager
    2. try to avoid Windows Terminal, elevated CMD works perfectly
    3. always install SSU first in separate DISM session
     
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    @Paul Mercer

    That was the only order i didn't test after finally it worked without the LCU and still the winre.wim was updated to 22621.963 but (another clone):
    Code:
    Microsoft Windows [Version 10.0.22621.963]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\Windows\System32>md c:\mount
    
    C:\Windows\System32>ReAgentC.exe /mountre /path c:\mount
    REAGENTC.EXE: Operation Successful.
    
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\SSU-22621.898-x64.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_898~31bf3856ad364e35~amd64~~22621.898.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_898 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021041-x64_DU_SafeOS_815.cab"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 - Adding package Package_for_KB5021041~31bf3856ad364e35~amd64~~22621.815.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>Dism /Add-Package /Image:C:\mount\ /PackagePath:"C:\Winre\windows11.0-kb5021255-x64_LCU_963.1.8.msu"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.525
    
    Processing 1 of 1 -
    [===========================80.0%==============            ]
    [==========================100.0%==========================] The operation completed successfully.
    
    C:\Windows\System32>Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.963
    
    [=====                      10.0%                          ]
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\System32>ReAgentC.exe /unmountre /path c:\mount /commit
    REAGENTC.EXE: Operation failed: 70
    
    REAGENTC.EXE: An error has occurred.
    
    
    C:\Windows\System32>rd c:\mount
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
    #1354 Paul Mercer, Jan 7, 2023
    Last edited: Jan 7, 2023
    resize your recovery partition, mine is on C drive with plenty of space

    AOMEI Partition Assistant should be fine for that

    __
    got the same error in my Beta channel VM, winre partition size is 575 Mb.
    I'm gonna expand it to 700 Mb. now
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    #1355 Enthousiast, Jan 7, 2023
    Last edited: Jan 7, 2023
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
    #1356 Paul Mercer, Jan 7, 2023
    Last edited: Jan 7, 2023
    yeah, typical Microsoft

    0x70 error is just about small recovery partition size, works fine in my VM with 700 Mb.

    wow, it's too much, I don't want to expand it to about 900 Mb. just for winre

    I think it's better and just a lot easier to copy updated winre.win from refreshed ISO to winre location, if filesize is the problem then we can compress wim with wimlib

    I'm not sure but maybe it's big because it wasn't exported (and we can't do that anyway lol)
     
  17. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    After optimizing (wimlib-imagex recompress):
    Code:
    Name: winre.wim
    Size: 596504963 bytes (568 MiB)
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
    yep, is there any way to commit changes without backup of old files?
     
  19. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    43,467
    80,783
    450
    Not that i know off:(
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  20. Paul Mercer

    Paul Mercer MDL Senior Member

    Apr 6, 2018
    480
    898
    10
    this is just stupid, this should work fine

    reagentc /disable
    blah-blah (Microsoft article, file location is C:\Windows\System32\Recovery\Winre.wim)
    wimlib optimize "C:\Windows\System32\Recovery\Winre.wim" --compress=LZX:100
    reagentc /enable