1. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,748
    3,575
    60
    It may be, but the import procedure through Toolkit is the same in all the features in which there is a need to import some reg. Even for the games (C:\\Program Files\\...), PowerShell (C:\\Program Files\\PowerShell\\7\\pwsh.exe). And, taking this as a basis, whenever there is an import of a tweak involving a program path directly to the registry image, it is "C:\" or "%SystemDrive%\" and "%SystemROOT%"\ to replace "C:\Windows\". I do not know if you did the test, but I had only placed the new suggestion point to in "C:\" and later I edited and put everything in point to "C:\".

    But there is always someone who is preparing a non-definitive image that will end up testing.

    I recently made many tests to implement CMD and WSL context menus. And, translation of the context menus of the PowerShell 7.1.4, to Portuguese that worked for 7.1.5 as well.

    I believe I did right. But as well you said, it may be that I have lost something on the way. Just more things I'm going to learn from his implementations and fixes.

    I followed the MSMG code itself that is already functional. I followed his lead.
     
  2. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,748
    3,575
    60
    But when we are in a browser, what can happen to the browser's console (element inspector)?

    My calculator key that opened inbox Calc, after I apply to Tweaks replaced to Win32Calc. And this way will work from any screen in which you are, for those who have the Mutimidia keys on your keyboard. But a direct shortcut button that is not used in other software, to add to Win32Calc universally, is a difficult choice to do.
     
  3. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    Usually in the keyboard the calc function works with Function (FN) + F12 key.

     
  4. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,748
    3,575
    60
    #21304 inTerActionVRI, Nov 11, 2021
    Last edited: Nov 11, 2021
    Okay, I'd thought it was directly on the F12 key.
    In my Laptop the "Function (FN) + F12 key: in Samsung is "WiFi", in Asus is "Vol Up" and Acer is "Scr Lk".
    There are many variations.
     
  5. mtfclphtknlrkn

    mtfclphtknlrkn MDL Novice

    Nov 6, 2021
    40
    12
    0
    I didn't know what could be deleted - that's the reason. What can be removed without harm?

    p.s.
    If possible, as much as possible.
     
  6. mhussain

    mhussain MDL Senior Member

    Oct 1, 2012
    368
    144
    10
    hi all,
    can't wate for the next release!
    as far as I am conserned, the slimmer windows can be made, the better for us all.
    my update stratagem is as folowes.
    gennerate a msmg windows iso image, with all components that can be removed, removed.
    remove all hyper-v features/components via dism.
    uninstall all windows update services.
    because windows update is not required.
    services that are deleted are
    windows update service
    windows update-medic service
    backround transfer service
    i'm sure i'm missing a few?
    having to use ntlite to integrate nvda silently to start after install
    nvda is my screen reader.
    @MSMG
    deleteing windows update services, related services and reg keys could be one way of removeing windows update components?
    also,
    the new offlines files removal capability would the removal function on windows 10?
    or is it just windows 11?
    thanks all!
    Majid
     
  7. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,748
    3,575
    60
    There is a way for you to view the dependencies. You can enter the menus of the removal categories and take a look at the descriptions of the components.
    Look for the infos "needed for" and "Depends On".
    You can also open the "Toolkit.cmd" script (notepad++) and search for these terms. This may vary according to the build used.
     
  8. delft 1985

    delft 1985 MDL Novice

    Oct 20, 2021
    21
    12
    0
    When will the new version 11.9 be released?:)
     
  9. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    Check it's released.

     
  10. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    783
    629
    30
    @MSMG
    Thank you for the update, shall begin my testing shortly.

    Can you let me know what to do with Win32Calc reg files?
     
  11. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    I have uploaded the updated Win32Calc reg files do download them.

     
  12. mhussain

    mhussain MDL Senior Member

    Oct 1, 2012
    368
    144
    10
    @MSMG
    thanks for the update!
    added the packages you mentioned after your changelog to another seperate file for later testing.
    thanks :)
    Majid
     
  13. bababafasdfggg

    bababafasdfggg MDL Novice

    Oct 5, 2018
    47
    15
    0
    Hm, sorry for late reply.
    Extreme, maybe not :D

    I made Powershell Script its atm 700 lines. Im not pro in scripting started learning this like month maybe ago.
    It can enable/disable features, remove/add capabilities, add/remove packages/backup (thanks for SxSExtract Script works well for backup).
    I made iso like u did MSMG Toolkit(First Updates and stuff i want to integrate, then removal) and NTLite, its probably the best way to do it at this moment.

    Dont Know why(Yet). Dism tool sometimes just throw errors when removing packages ??? Anyone have any ideas why ???
    Thats only problem with removal on offline image.

    Used to remove some more packages online, all works so far.
    Thats list of packages im on ltsc 2019 thats (353) Packages excluding laguage:
    Microsoft-Media-Foundation-Package
    Microsoft-Media-Foundation-WOW64-Package
    Microsoft-OneCore-EventLogAPI-Package
    Microsoft-OneCore-Http-Package
    Microsoft-OneCore-IsolatedUserMode-minkernel-Package
    Microsoft-OneCore-IsolatedUserMode-onecore-Package
    Microsoft-OneCore-IsolatedUserMode-Package
    Microsoft-OneCore-Multimedia-MFPMP-Package
    Microsoft-OneCore-Multimedia-MFPMP-WOW64-Package
    Microsoft-OneCore-VirtualizationBasedSecurity-Package
    Microsoft-Windows-AppManagement-AppV-Package
    Microsoft-Windows-AppManagement-AppV-WOW64-Package
    Microsoft-Windows-AppManagement-Common-Package
    Microsoft-Windows-AppManagement-Common-WOW64-Package
    Microsoft-Windows-AppManagement-UEV-Package
    Microsoft-Windows-AppManagement-UEV-WOW64-Package
    Microsoft-Windows-Basic-Http-Minio-Package
    Microsoft-Windows-Branding-EnterpriseS-Package
    Microsoft-Windows-Client-Desktop-Required-Package0010
    Microsoft-Windows-Client-Desktop-Required-Package00
    Microsoft-Windows-Client-Desktop-Required-Package01
    Microsoft-Windows-Client-Desktop-Required-Package02
    Microsoft-Windows-Client-Desktop-Required-Package031020
    Microsoft-Windows-Client-Desktop-Required-Package031021
    Microsoft-Windows-Client-Desktop-Required-Package0310
    Microsoft-Windows-Client-Desktop-Required-Package03110
    Microsoft-Windows-Client-Desktop-Required-Package03111
    Microsoft-Windows-Client-Desktop-Required-Package0311220
    Microsoft-Windows-Client-Desktop-Required-Package03112
    Microsoft-Windows-Client-Desktop-Required-Package03113
    Microsoft-Windows-Client-Desktop-Required-Package03114
    Microsoft-Windows-Client-Desktop-Required-Package03115
    Microsoft-Windows-Client-Desktop-Required-Package0311
    Microsoft-Windows-Client-Desktop-Required-Package0312
    Microsoft-Windows-Client-Desktop-Required-Package0313
    Microsoft-Windows-Client-Desktop-Required-Package0314
    Microsoft-Windows-Client-Desktop-Required-Package0315
    Microsoft-Windows-Client-Desktop-Required-Package0316
    Microsoft-Windows-Client-Desktop-Required-Package0317
    Microsoft-Windows-Client-Desktop-Required-Package0318
    Microsoft-Windows-Client-Desktop-Required-Package0319
    Microsoft-Windows-Client-Desktop-Required-Package03
    Microsoft-Windows-Client-Desktop-Required-Package
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package001020
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package0010
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package0011
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package0012
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package0013
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package0014
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package0015
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package00
    Microsoft-Windows-Client-Desktop-Required-WOW64-Package
    Microsoft-Windows-Client-Features-Package00
    Microsoft-Windows-Client-Features-Package0110
    Microsoft-Windows-Client-Features-Package0111
    Microsoft-Windows-Client-Features-Package0112
    Microsoft-Windows-Client-Features-Package0113
    Microsoft-Windows-Client-Features-Package0114
    Microsoft-Windows-Client-Features-Package0115
    Microsoft-Windows-Client-Features-Package0116
    Microsoft-Windows-Client-Features-Package01
    Microsoft-Windows-Client-Features-Package02
    Microsoft-Windows-Client-Features-Package03
    Microsoft-Windows-Client-Features-Package04
    Microsoft-Windows-Client-Features-Package05
    Microsoft-Windows-Client-Features-Package
    Microsoft-Windows-Client-Features-WOW64-Package0010
    Microsoft-Windows-Client-Features-WOW64-Package0011
    Microsoft-Windows-Client-Features-WOW64-Package0012
    Microsoft-Windows-Client-Features-WOW64-Package00
    Microsoft-Windows-Client-Features-WOW64-Package01
    Microsoft-Windows-Client-Features-WOW64-Package02
    Microsoft-Windows-Client-Features-WOW64-Package
    Microsoft-Windows-Client-Optional-Features-Package
    Microsoft-Windows-Common-Foundation-Package
    Microsoft-Windows-Common-RegulatedPackages-Package
    Microsoft-Windows-Common-RegulatedPackages-WOW64-Package
    Microsoft-Windows-ConfigCI-Onecore-Package
    Microsoft-Windows-ConfigCI-Onecore-WOW64-Package
    Microsoft-Windows-ConfigCI-Package
    Microsoft-Windows-CoreSystem-DISM-Package
    Microsoft-Windows-DeviceGuard-GPEXT-base-Package
    Microsoft-Windows-DeviceGuard-GPEXT-onecore-Package
    Microsoft-Windows-DeviceGuard-GPEXT-Package
    Microsoft-Windows-EditionPack-Professional-Package
    Microsoft-Windows-EditionPack-Professional-WOW64-Package
    Microsoft-Windows-Editions-EnterpriseS-Package
    Microsoft-Windows-EditionSpecific-EnterpriseS-Package
    Microsoft-Windows-Enterprise-Desktop-Shared-Package
    Microsoft-Windows-Enterprise-Desktop-Shared-WOW64-Package
    Microsoft-Windows-EnterpriseS-SPP-Components-Package
    Microsoft-Windows-EnterpriseSEdition
    Microsoft-Windows-FCI-Client-Package
    Microsoft-Windows-FodMetadata-Package
    Microsoft-Windows-Foundation-Package
    Microsoft-Windows-GroupPolicy-ClientExtensions-admin-Package
    Microsoft-Windows-GroupPolicy-ClientExtensions-ds-Package
    Microsoft-Windows-GroupPolicy-ClientExtensions-Package
    Microsoft-Windows-GroupPolicy-ClientExtensions-WOW64-admin-Package
    Microsoft-Windows-GroupPolicy-ClientExtensions-WOW64-ds-Package
    Microsoft-Windows-GroupPolicy-ClientExtensions-WOW64-Package
    Microsoft-Windows-GroupPolicy-ClientTools-admin-Package
    Microsoft-Windows-GroupPolicy-ClientTools-base-Package
    Microsoft-Windows-GroupPolicy-ClientTools-com-Package
    Microsoft-Windows-GroupPolicy-ClientTools-drivers-Package
    Microsoft-Windows-GroupPolicy-ClientTools-ds-Package
    Microsoft-Windows-GroupPolicy-ClientTools-enduser-Package
    Microsoft-Windows-GroupPolicy-ClientTools-inetcore-Package
    Microsoft-Windows-GroupPolicy-ClientTools-inetsrv-Package
    Microsoft-Windows-GroupPolicy-ClientTools-minio-Package
    Microsoft-Windows-GroupPolicy-ClientTools-minkernel-Package
    Microsoft-Windows-GroupPolicy-ClientTools-multimedia-Package
    Microsoft-Windows-GroupPolicy-ClientTools-net-Package
    Microsoft-Windows-GroupPolicy-ClientTools-onecore-Package
    Microsoft-Windows-GroupPolicy-ClientTools-onecoreuap-Package
    Microsoft-Windows-GroupPolicy-ClientTools-Package
    Microsoft-Windows-GroupPolicy-ClientTools-printscan-Package
    Microsoft-Windows-GroupPolicy-ClientTools-servercommon-Package
    Microsoft-Windows-GroupPolicy-ClientTools-shell-Package
    Microsoft-Windows-GroupPolicy-ClientTools-termsrv-Package
    Microsoft-Windows-GroupPolicy-ClientTools-windows-Package
    Microsoft-Windows-GroupPolicy-ClientTools-WOW64-admin-Package
    Microsoft-Windows-GroupPolicy-ClientTools-WOW64-ds-Package
    Microsoft-Windows-GroupPolicy-ClientTools-WOW64-Package
    Microsoft-Windows-Help-ClientUA-Enterprise-Package
    Microsoft-Windows-Hyphenation-Dictionaries-pl-Package
    Microsoft-Windows-LanguageFeatures-OCR-pl-pl-Package
    Microsoft-Windows-Media-Format-multimedia-Package
    Microsoft-Windows-Media-Format-Package
    Microsoft-Windows-Media-Format-windows-Package
    Microsoft-Windows-Media-Format-WOW64-multimedia-Package
    Microsoft-Windows-Media-Format-WOW64-Package
    Microsoft-Windows-Media-Format-WOW64-windows-Package
    Microsoft-Windows-MediaPlayback-OC-Package
    Microsoft-Windows-MediaPlayer-Package
    Microsoft-Windows-MediaPlayer-Payload-Package
    Microsoft-Windows-Multimedia-MF-avcore-Package
    Microsoft-Windows-Multimedia-MF-multimedia-Package
    Microsoft-Windows-Multimedia-MF-Package
    Microsoft-Windows-Multimedia-MF-WOW64-avcore-Package
    Microsoft-Windows-Multimedia-MF-WOW64-Package
    Microsoft-Windows-Multimedia-RestrictedCodecs-avcore-Package
    Microsoft-Windows-Multimedia-RestrictedCodecs-multimedia-Package
    Microsoft-Windows-Multimedia-RestrictedCodecs-Package
    Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-avcore-Package
    Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-multimedia-Package
    Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-Package
    Microsoft-Windows-NetFx-AutoNgenEnable.3.5
    Microsoft-Windows-NetFx-NgenAssemblyExclusionClient
    Microsoft-Windows-NetFx-Shared-Misc
    Microsoft-Windows-NetFx-Shared-MOF-Client
    Microsoft-Windows-NetFx-Shared-MOF-Extended
    Microsoft-Windows-NetFx-Shared-Package
    Microsoft-Windows-NetFx-Shared-Perfcounters-Client
    Microsoft-Windows-NetFx-Shared-Perfcounters-Extended
    Microsoft-Windows-NetFx-Shared-Typelibs
    Microsoft-Windows-NetFx-Shared-WCF-HttpNamespace
    Microsoft-Windows-NetFx-Shared-WPF-Package
    Microsoft-Windows-NetFx-Windows-Built-Package
    Microsoft-Windows-NetFx2-OC-Package
    Microsoft-Windows-NetFx3-OC-Package
    Microsoft-Windows-NetFx3-OnDemand-Package
    Microsoft-Windows-NetFx4-US-OC-Package
    Microsoft-Windows-NetworkDiagnostics-DirectAccessEntry-Package
    Microsoft-Windows-Portable-Devices-multimedia-Package
    Microsoft-Windows-Portable-Devices-Package
    Microsoft-Windows-Portable-Devices-windows-Package
    Microsoft-Windows-Portable-Devices-WOW64-Package
    Microsoft-Windows-Portable-Devices-WOW64-windows-Package
    Microsoft-Windows-PowerShell-V2-Client-Package
    Microsoft-Windows-Presentation-Package
    Microsoft-Windows-SecConfig-Package
    Microsoft-Windows-SecureStartup-Package
    Microsoft-Windows-SecureStartup-Subsystem-base-Package
    Microsoft-Windows-SecureStartup-Subsystem-onecore-Package
    Microsoft-Windows-SecureStartup-Subsystem-Package
    Microsoft-Windows-SecureStartup-Subsystem-WOW64-base-Package
    Microsoft-Windows-SecureStartup-Subsystem-WOW64-onecore-Package
    Microsoft-Windows-SecureStartup-Subsystem-WOW64-Package
    Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package
    Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package
    Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package
    Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package
    Microsoft-Windows-Spelling-Dictionaries-pl-Package
    Microsoft-Windows-SQL-Lite-Package
    Microsoft-Windows-SQL-Lite-WOW64-Package
    Microsoft-Windows-TerminalServices-WMIProvider-Package
    Microsoft-Windows-TextPrediction-Dictionaries-pl-Package
    Microsoft-Windows-win32calc-Package
    Microsoft-Windows-WindowsMediaPlayer-Troubleshooters-Package
    Microsoft-Windows-WPD-LegacyWmdmFeature-Feature-Package
    Microsoft-Windows-WPD-LegacyWmdmFeature-Feature-WOW64-Package
    Microsoft-Windows-WPD-UltimatePortableDeviceFeature-Feature-Package
    Microsoft-Windows-WPD-UltimatePortableDeviceFeature-Feature-WOW64-Package
    Multimedia-MFCore-Package
    Multimedia-MFCore-WOW64-Package
    Multimedia-RestrictedCodecsCore-Full-Package
    Multimedia-RestrictedCodecsCore-Full-WOW64-Package
    Multimedia-RestrictedCodecsCore-Package
    Multimedia-RestrictedCodecsCore-WOW64-Package
    Multimedia-RestrictedCodecsExt-Package
    Multimedia-RestrictedCodecsExt-WOW64-Package
    Networking-MPSSVC-Rules-EnterpriseEdition-net-Package
    Networking-MPSSVC-Rules-EnterpriseEdition-onecore-Package
    Networking-MPSSVC-Rules-EnterpriseEdition-Package
    Server-Help-Package.ClientEnterprise
    Not Sure What Next :D
     

    Attached Files:

  14. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,748
    3,575
    60
    Was maintained as X:\. So I was wrong. And, I was confused... I did not understand anything about this logic in this integration process of win32calc, because it is the only process that is peculiar, that does not follow the pattern I see at that time.

    @MSMG, can you explain a little more detailed why this particularity in the integration of Win32Calc?
    I confused the meanings of Dynamic path with Relative path and with Direct Path?
    X:\ would not it be considered a direct path?
     
  15. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    Actually the custom packs I do create from a live system already have the path set to C:\ so the reg files will contain C:\ instead of X:\ , suppose if the user integrates the packs like NET6, PowerShell7 and installs the OS to some other drive other than the C:\ then it will have issues and here comes the dynamic paths to rescue.

    The dynamic paths will use the %SystemDrive% for getting the OS installation drive and then the C:\ becomes %SystemDrive%\

    X:\ path is used by the Windows setup installer during the Windows installation.


     
  16. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,748
    3,575
    60
    #21317 inTerActionVRI, Nov 12, 2021
    Last edited: Nov 12, 2021
    So it is. That's how I understand.
    But then, all the reg files from the other Custom Packs, should be modified from C: to X:? In order to obey this scheme of the Windows setup installer during the Windows installation be X:?

    And, on the NET5 for W7 and W81, the Toolkit still keeps the support?
    Or will there be NET6 for both?
     
  17. graver.x

    graver.x MDL Senior Member

    Jan 18, 2020
    347
    484
    10
    MSMG,
    With the release of .NET 6 Toolkit now no longer supports .NET 5?
     
  18. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    #21319 MSMG, Nov 12, 2021
    Last edited: Nov 12, 2021
    (OP)
    No don't change it to X:\ just use the dynamic paths like the games pack.

    You need to import the key into registry, change the path to use the dynamic path and then export back the reg to file and add the new entries to the packs registry files.


     
  19. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,608
    210
    Yes I have replaced the .NET 5 pack with .NET 6.

    Do you want the .NET 5 pack to be updated? if yes then will do create the packs or will share the steps to make it.