MSMG ToolKit

Thanks for the advice. You are right.

It is possible and recommended to disable Windows PowerShell 2.0, in Windows 10 (I disable it via Turn Windows features on or off).

After doing a lot of research, I realized that it is not possible to upgrade the native 5.1 version directly to 7.x, as I imagined before, but rather to block some scripts for non-admins (which I need).

 

Yes, I disable this at all times.
You can use DisableFeatures.txt

I just dont remove the native PowerShell 5.1.

 

@MSMG, cortana for above 19041 remains blocked for removal. Is that right?
Should it be changed from:

Code:

    if "%CC_ShellSearch%" equ "+" (
       set "CC_ShellSearch=-"
       if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" set "C_Cortana=+"
   ) else (
       set "CC_ShellSearch=+"
       if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" set "C_Cortana=*"
   )
)

to:

Code:

    if "%CC_ShellSearch%" equ "+" (
       set "CC_ShellSearch=-"
       set "C_Cortana=+"
   ) else (
       set "CC_ShellSearch=+"
       if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" set "C_Cortana=*"
   )
)

C_NETNativeFramework17 is available for 22621, but not available in the menu.
from:

Code:

if "!ImageBuild!" geq "17763" if "!ImageBuild!" leq "19045" (
       echo.  [20] ^(!C_NETNativeFramework17!^) [106m[30m .NET Native Framework Package 1.7 ^(Microsoft.NET.Native.Framework.1.7^) [44m[97m

to:

Code:

if "!ImageBuild!" geq "17763" if "!ImageBuild!" leq "22631" (
       echo.  [20] ^(!C_NETNativeFramework17!^) [106m[30m .NET Native Framework Package 1.7 ^(Microsoft.NET.Native.Framework.1.7^) [44m[97m

or just:

Code:

if "!ImageBuild!" geq "17763" (
       echo.  [20] ^(!C_NETNativeFramework17!^) [106m[30m .NET Native Framework Package 1.7 ^(Microsoft.NET.Native.Framework.1.7^) [44m[97m

optimizing from:

Code:

       if /I "%%~#" equ "40" if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" (
           if "%C_ZuneVideo%" equ "+" (
               set "C_ZuneVideo=-"
           ) else (
               if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+"
               set "C_ZuneVideo=+"
           )
       )
       if /I "%%~#" equ "40" if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22640" (
           if "%C_ZuneVideo%" equ "+" (
               set "C_ZuneVideo=-"
           ) else (
               if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22640" if "%C_UIXaml27%" neq "*" set "C_UIXaml27=+"
               if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+"
               set "C_ZuneVideo=+"
           )
       )

to:

Code:

       if /I "%%~#" equ "40" (
           if "%C_ZuneVideo%" equ "+" (
               set "C_ZuneVideo=-"
           ) else (
               if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22640" if "%C_UIXaml27%" neq "*" set "C_UIXaml27=+"
               if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+"
               set "C_ZuneVideo=+"
           )
       )

typo from:

Code:

if "%C_XboxIdentityProvide%" neq "*"

to:

Code:

if "%C_XboxIdentityProvider%" neq "*"

from:

Code:

       if /I "%%~#" equ "27" ( if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "22000" if "%C_QuickAssist%" equ "+" ( set "C_QuickAssist=-" ) else ( set "C_QuickAssist=+" ) )

to:

Code:

       if /I "%%~#" equ "27" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "22000" (if "%C_QuickAssist%" equ "+" ( set "C_QuickAssist=-" ) else ( set "C_QuickAssist=+" ) )

Aestethical from:

Code:

       if /I "%%~#" equ "21" if "%C_WindowsStoreCore%" neq "*" ( if "%C_WindowsStoreCore%" equ "+" (
               if "%SelectedSourceOS%" equ "w10" set "C_ServicesStoreEngagement=-"
               if "%ImageBuild%" equ "17763" set "C_SolitaireCollection=-"
               if "%ImageBuild%" leq "22640" set "C_StickyNotes=-"
               set "C_StorePurchaseApp=-"
               if "%C_WindowsStore%" neq "*" set "C_WindowsStore=-"
               set "C_WindowsStoreCore=-"
           ) else (
               set "C_WindowsStoreCore=+"
           )
       )

to:

Code:

       if /I "%%~#" equ "21" if "%C_WindowsStoreCore%" neq "*" (
           if "%C_WindowsStoreCore%" equ "+" (
               if "%SelectedSourceOS%" equ "w10" set "C_ServicesStoreEngagement=-"
               if "%ImageBuild%" equ "17763" set "C_SolitaireCollection=-"
               if "%ImageBuild%" leq "22640" set "C_StickyNotes=-"
               set "C_StorePurchaseApp=-"
               if "%C_WindowsStore%" neq "*" set "C_WindowsStore=-"
               set "C_WindowsStoreCore=-"
           ) else (
               set "C_WindowsStoreCore=+"
           )
       )

and several elses with double spaces.
from:

Code:

) else  (

to:

Code:

) else (

Finished

 

Why in the download folder of version 13.5 - 2 different files "Toolkit.cmd" (1 in folder and 1 in the archive)?

 

the packs hasn't been updated for a long time

 

@MSMG,

Thank you, I am eagerly waiting for the next testing opportunity.

What is going to happen to the broken Start Menu / File Explorer search if Cortana App is removed?
It was working till v13.3, as you may have read / know.
Can we have it again working the same way it was back then (so Cortana was removed, but search was not broken) ?
Supposedly it still works if DISM is used instead of Toolkit, so I assume it can be made working with Toolkit method again.
You have not commented on the reason behind one yet, and I have not created a new image as I am waiting for a feedback from you regarding this.

Also, did you had the chance to look at the discussion about how to get the Start.cmd requirement eliminated?

 

@MSMG, @inTerActionVRI

OK, solved the issue with Realtek audio console.. I think.
It requires an internet connection when it is installed. I guess since the app is expected to be installed from the store one would have an internet connection.
But I always install Windows offline. This was causing the app to crash on first run. So when side loading, it needs an internet connection too.
I've tested it now on my base image 1288 and on 3208.

Someone on another forum said to me that the app version must match the driver version, in my case .290. I have to question this as the latest app version is .302 and there have been no driver updates since Feb.
I doubt that realtek would continue to update the app and not the driver if the two are required to be kept in sync.
So I have one more test to do - installing the latest console version .302 with 19044-3208 and see if that works.

As to win32calc. I've done over a dozen tests now using toolkit 13.3, 13.4 and 13.5. Selecting 2>3>3>G to integrate it does not work. When Windows is installed Win32calc is completely absent.
But as I said, I have the installer so I have a workaround for this.

As to the codecs, they are also fine, provided they are integrated after the removal process, at the same time as I integrate .net 3.5. If they are integrated before removal of components they seem to disappear when Windows is installed, despite /get-provisionsappxpackages showing them to be present when looking at the offline image. Strange.

@inTerActionVRI You mentioned in a previous post about the patches that can be applied. Did you mean that I could use a later patch with the toolkit? For example, the august patches have been released and if I can integrate it and do my removals that would be great.

I have another PC to build for a family member on the 18th of August, so it would be good to have the latest patch on that if possible.

 

For my eye sight issues I can't tell the difference between dark blue and black. Two colors that are close together look the same to me.
I find light themes to be easiest to cope with. So many people send me stuff in dark theme and I have to keep telling them I can't see it

 

So, is it correct to rename the files by removing en-US from their name? And move them to the architecture folder? Will it be the same file for all languages?

This, about lss 19941, is to make it easier to compare the toolkit and IMCK when merging. The change was from leq 18363 to lss 19041.
So it should be leq 18362 or only equ 17763? Or keep what is which is leq 18363. But the point of the suggestion was to remove that conditional from the line that unlocks the Cortana.
I got used to keeping lss 19041 because dism always detects 18363 as 18362.
But really, I don't remember where I found something that made a difference.

About every geq 17763 and every leq 22631 you dont need this in all 8 Remove Menu codes as it is specified in the first statement of each menu.

 

If you, as usual, use an ISO supported by the toolkit, that's right. If you apply the recent update and without committing install.wim or saving the ISO for further customization, removing components is still supported.

@MSMG, Please correct me if I got something wrong. So, I'll explain better to the people when necessary.

 

I had told you, that once, I suggested and MSMG deleted the start.cmd. But the change was not mature enough. So he had to go back. We can have the schema implemented, but you must keep the start.cmd for a while. Until people stop reporting problems.

Right now, the focus is on making the testing version stable. I believe that this part auto trustedinstaller, later on, will go well with the part about checking the path of the toolkit folder.

I believe, at moment, it is not possible to put another problem on the agenda.
But it is up to MSMG.

I'm struggling to merge with this massive change that MSMG has made (something that's already available for me to compare and refactor). Imagine how, he who is creating the changes, must be busy.

This will be very good to be resolved again. Your tests and reports were top.

Now we can only wait. From what I witness here, he responds when the solution is at hand.

 

Thank you.

Obviously the change for starting the tool is not there to make all that much difference, however, notice that earlier attempts did fail, because there was no (proper) identity verification implemented.
If you could do more tests for other languages (this is the only thing that is missing from my point of view), you can clear all doubts afterwards now that you are aware what kind of issues people were facing previously.

 

MSMG Toolkit 13.5

Updates renamed this way:
KB5028951.msu
KB5029244.msu

I put the updates in the folder:
C:\MSMG\Updates\w10\x64

Error: 87

What am I doing wrong?

 

Edit: it looks like the file name pattern must have x64 in it, then the .msu extraction happens.
The script did not find the filename pattern, so it was not extracting anything, and thus DISM could not find .cab files to integrate.
Do not rename the update files, no need for that.
Additionally, integration might fail, as the recent updates require higher Servicing Stack version.
If you are trying to add the update to an older image, be sure to integrate the SSU update from the latest .msu first.

Do note that KB5029244 is not yet supported when it comes to component removal - we have a discussion about this on a weekly basis lately.
Either you use KB5028166, or you wait for the next release if you want to be certain that there will not be any issues after you modified the image.

@inTerActionVRI, as per the above, how about adding some checks before trying to integrate anything?

 

@inTerActionVRI

few weeks ago you said StartComponentCleanup & ResetBase should be disabled so theres no errors. took me a month to realize and find out why you said what you said, lol.

dism resetbase causes problems on win11 22h2 22621.1 just as much as on 22621.2134.

used toolkit against 22.621.1 and 22621.2134 component removal against both worked alright when installed both copies no errors. then used dism resetbase and still no errors rebooted few times and viola both versions showed errors. lmao.

means simply dont use dism StartComponentCleanup & ResetBase ever