MSMG ToolKit

But don't worry, Toolkit and Custom Toolkit are not yet prepared for the 22621 versioning packages. Probably at the official launch they will be.

While writing this message I already made the preview change:

Code:

if "%SelectedSourceOS%" equ "w7" (
   set "PackageBuild=%ImageBuild%"
   set "PackageVersion=%ImageVersion%"
   set "PackageServicePackBuild=17514"
)
if "%SelectedSourceOS%" equ "w81" (
   set "PackageBuild=%ImageBuild%"
   set "PackageVersion=%ImageVersion%"
   set "PackageServicePackBuild=16384"
)
if "%SelectedSourceOS%" equ "w10" (
   if "%ImageBuild%" geq "10240" if "%ImageBuild%" leq "15063" (
       set "PackageBuild=%ImageBuild%"
       set "PackageVersion=10.0.%ImageBuild%"
       set "PackageServicePackBuild=0"
   )
   if "%ImageBuild%" equ "16299" (
       set "PackageBuild=%ImageBuild%"
       set "PackageVersion=10.0.%ImageBuild%"
       set "PackageServicePackBuild=15"
   )
   if "%ImageBuild%" geq "17134" (
       if "%ImageBuild%" leq "17763" (
           set "PackageBuild=%ImageBuild%"
           set "PackageVersion=10.0.%ImageBuild%"
       )
       if "%ImageBuild%" gtr "17763" if "%ImageBuild%" lss "19041" (
           set "PackageBuild=18362"
           set "PackageVersion=10.0.18362"
       )
       if "%ImageBuild%" geq "19041" if "%ImageBuild%" leq "19044" (
           set "PackageBuild=19041"
           set "PackageVersion=10.0.19041"
       )
       if "%ImageBuild%" geq "20348" if "%ImageBuild%" lss "22000" (
           set "PackageBuild=%ImageBuild%"
           set "PackageVersion=10.0.%ImageBuild%"
       )
       set "PackageServicePackBuild=1"
   )
)

if "%SelectedSourceOS%" equ "w11" (
   if "%ImageBuild%" geq "21996" if "%ImageBuild%" lss "22563" (
       set "PackageBuild=22000"
       set "PackageVersion=10.0.22000"
   )
   if "%ImageBuild%" geq "22563" if "%ImageBuild%" lss "25115" (
       set "PackageBuild=22621"
       set "PackageVersion=10.0.22621"
   )
   set "PackageServicePackBuild=1"
)

 

I also removed components with uup, I put the both list.

 

I believe it is a server error on Mediafire. It can be an upload interruption.

 

You need to login to view this posts content.

 

This script is from CustomToolkit right?

 

I think that since the last updates, the gamebar finds a way to reopen and since I no longer have access to the gamemode setting, I can't disable it properly, I'll try to install a vanilla ISO in VirtualBox and watch the registry changes when I disable it.

Before I used these keys
[HKEY_CURRENT_USER\Software\Microsoft\GameBar]
"AutoGameModeEnabled"=dword:00000000
"UseNexusForGameBarEnabled"=dword:00000000
[HKEY_CURRENT_USER\System\GameConfigStore]
"GameDVR_Enabled"=dword:00000000
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\GameDVR]
"AppCaptureEnabled"=dword:00000000

Edit : Nothing new in the registry.
Edit 2 : I identified the problem, it comes from the x360ce program, first time it does this to me in 10 years.

 

I do have a solution, but I think it should be build-in inside the script

 

I'm thinking of removing these aesthetic title details from the window title and display on screnn, to improve it, as you said. And, use the execution with the use of MS-DOS shortened paths and names to eight characters with %~fs0.

In Custom Toolkit I put the index mount folder, outside the Toolkit folder, in the shortest, possible paths. With these shortened paths and outside the Toolkit folder, the Toolkit main folder can be placed anywhere.

 

It is for both ones.

EDIT:
Sorry, I read "for Custom Toolkit"...

This has a slight change to W7 and W81 for a change in :RemovelockedPackage code block.
This originates from Toolkit. But it was optimized to be placed in the core of the code in Toolkit v11 and Custom Toolkit to avoid repetition of code in various parts of the script. So it fits both.

 

Hello! Can't update Windows 10 LTSC 19044.1288 to 19044.1766 error: 0x800f0823

 

@delft 1985 And how would that be related to the toolkit?

 

Yes.

 

What was the exact procedure?
where did you get update 19044.1766 from?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Thank you. I shall probably just wait for v12.3 to guarantee it also works with 22000.739.

 

You need to login to view this posts content.