1. Yanta

    Yanta MDL Senior Member

    May 21, 2017
    491
    284
    10
    Sometimes I forget that some people are still using 32 bit OSs :)

    Interestingly, when I created my image using 11.6 those files could not be found. No dramas though, I already had copies of them from when I used 10.4 to build the images. I am on LTSC 2019 though.
     
  2. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    #21482 MSMG, Nov 19, 2021
    Last edited: Nov 19, 2021
    (OP)
    Shorten the Toolkit's working path length.
     
  3. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    #21485 MSMG, Nov 19, 2021
    Last edited: Nov 19, 2021
    (OP)

    Microsoft.Windows.Photos_2021.21090.29009.0_neutral___8wekyb3d8bbwe.AppxBundle is not Windows 11


    - You need to open the Photos App with 7-zip and again inside it open the AppStubCS.Windows_2021.21090.10008.0__x64_Ship.appx

    - Now right click on AppxManifest.xml and choose Edit

    - Check this part to know which OS it is made for

    Code:
      <Dependencies>
        <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.19400.0" />
        <PackageDependency Name="Microsoft.UI.Xaml.2.4" MinVersion="2.42007.9001.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
        <PackageDependency Name="Microsoft.NET.Native.Framework.2.2" MinVersion="2.2.27405.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
        <PackageDependency Name="Microsoft.NET.Native.Runtime.2.2" MinVersion="2.2.27328.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
        <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.30035.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
      </Dependencies>
    
    You need these files

    Code:
    Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe.appx
    Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe.appx
    Microsoft.UI.Xaml.2.4_2.42007.9001.0_x64__8wekyb3d8bbwe.appx
    Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe.appx
    Microsoft.Windows.Photos_2021.21090.10008.0_neutral___8wekyb3d8bbwe.AppxBundle
    
    The License XML file is now included with-in the Toolkit so no need to look for it.
     
  4. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    May be those files were retained from recent versions.
     
  5. SimonPetrus

    SimonPetrus MDL Novice

    Dec 25, 2020
    16
    1
    0
  6. zero cool root

    zero cool root MDL Senior Member

    Jun 17, 2011
    391
    162
    10
    I tried too W10 19044.1348 and I get the same error..!!

    Portuguese-Brazil
     
  7. digitalized

    digitalized MDL Novice

    Nov 17, 2017
    30
    9
    0
    How do I get ToolKitHelper to show a list of component names that can be removed? I used to be able to do this by running ToolkitHelper.exe with an invalid name specified, however, now I'm only getting the following when I do this:
    ToolKitHelper used to show a list of valid component names.

    Alternatively, is there a text file updated with every iteration of the Toolkit that contains this list? Thanks
     
  8. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    You need to specify the ImageMountPath along with /? to get the list of components

    For example if your Toolkit folder is C:\Toolkit and the select index is 1

    ToolKitHelper.exe C:\Toolkit\Mount\Install\1 /?


    For Templates check in Bin\Lists\ToolkitHelper_Templates folder

     
  9. tosgaba

    tosgaba MDL Junior Member

    Nov 22, 2009
    96
    41
    0
  10. tosgaba

    tosgaba MDL Junior Member

    Nov 22, 2009
    96
    41
    0
    This is what I need. Thank you very much.
     
  11. graver.x

    graver.x MDL Senior Member

    Jan 18, 2020
    349
    486
    10
  12. graver.x

    graver.x MDL Senior Member

    Jan 18, 2020
    349
    486
    10
  13. tosgaba

    tosgaba MDL Junior Member

    Nov 22, 2009
    96
    41
    0
  14. RB333

    RB333 MDL Novice

    Nov 19, 2021
    2
    0
    0
    Hello, I recently began using MSMG toolkit to customize and Win10 ISO and am having a strange issue. Once I go through the source image, remove apps/items I don't want included and create a bootable USB, the actual installation appears to contain only the items I intended to remove from the image. Groove music, xbox live, Office etc... Virtually nothing else is in the image.

    Clearly I am doing something fundamentally wrong. Any guidance would be greatly appreciated.

    Thanks,
     
  15. ashish.k

    ashish.k MDL Senior Member

    Dec 27, 2014
    303
    136
    10
    In the removal menu if you have "+" on the left of the item then it will be included. "-" means it'll be removed. You might be doing vice-versa.
     
  16. RB333

    RB333 MDL Novice

    Nov 19, 2021
    2
    0
    0
    #21499 RB333, Nov 19, 2021
    Last edited: Nov 19, 2021
    Thank you for the response.

    Yeah that was the first thing I checked. I actually went through a second time and created a new ISO to make sure. Definitely had the minus "-" next to the packages.

    Problem persists
     
  17. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    786
    631
    30
    I think I now understand why the error in NVSlimmer. I created another image, keeping these four components:
    • WindowsStoreClient
    • DesktopAppInstaller
    • ServicesStoreEngagement
    • WindowsStoreApp
    When I pressed the Install NvCpl button, Microsoft Store was launched. So NVSlimmer isn't actually installing NVCpl, it is just redirecting the user to the Microsoft Store.

    I believe I showed that NVCpl was installed even without the above four components. So my question is do I actually need them? On my system, only the Nvidia drivers need an app - and this installed without the above four components.