Some Apps requires resetting the non-removalable state to remove the app. Code: dism /image:mount /Set-NonRemovableAppPolicy /PackageFamily:Microsoft.Windows.SecHealthUI_cw5n1h2txyewy /NonRemovable:0 Deployment Image Servicing and Management tool Version: 10.0.21996.1 Image Version: 10.0.21996.1 The operation completed successfully. dism /image:mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.SecHealthUI_1000.21996.1.0_neutral__8wekyb3d8bbwe Deployment Image Servicing and Management tool Version: 10.0.21996.1 Image Version: 10.0.21996.1 The operation completed successfully.
[/QUOTE] Dear Brother i havent quoted you for this comment but in fact its a user comment which forced me to comment so that he must be clear of the fact about non removable policy set on some store apps specially in this build ie 21996. I think it will be resolved in 22000 build or vice versa some more apps will be added to non removable state too. Thanks for your comment as i tried the same to clear out the fact about user query. i hope you dont mind my comment on your thread in a very firm way.
Actually when you quoted zero cool root message it had tagged my id and so I did mis-read that you were addressing me, sorry about that.
@MSMG Just FIY: For me all of these are garbage, except "Windows Terminal". Yes, Notepad is also unwanted much (I hate it even in LTSC) - absolutely joking piece of crap. Even AkelPad from 2017 is 100 times better, aside from Notepad++ But we have a lot of time until Win11 Release (for me, - until new LTSC release, - official or leaked, but RELEASE image). Until it is released I'm stay calm around LTSC 2019 (сan't wait to see the new Toolkit v11.7 with all fixes discussed in the last time period)
Brother Pl Dont feel SAD . Pl dont be sorry i am always on your side. Credits Always Yours & Pleasure Always Mine. Pl be Happy Always.
I was tinkering with another file and when comparing the changes with the original file from the 19th, I ended up doing the comparison with the file I had changed and discarded. My mistake here. Amidst the tests with the Custom Toolkit I found some bugs, the hunt was arduous because at first I thought it was a hardware, HD or memory problem. I did general maintenance here. I downloaded the packs again. Errors persisting. I downloaded the same ISO again. Errors persisting. And, I found that these problems did not occur at Official, but persisted at Custom. Only the official issues related to Integration of Language Pack and Hearts Game were resolved with the new downloaded ISO. Sorry @MSMG, for having wasted some time there. My ISO was corrupted. A very important consideration to mention here. I put a feature to update the ImageBuild at the beginning of Custom, I thought the Script work with the correct ImageBuild would be more visibly interesting. Displaying the correct version, 18363 instead of 18362, 19043 instead of 19041, on the screen. But this creates conflict in integrations. So to fix it I just generated a new variable called "CurrentImageBuild", instead of overwriting the ImageBuild variable. Almost done here. Another question? Does the XboxIdentityProvider component only depend on "XboxClient" or does it depend on "XboxApp and therefore XboxClient"?
@mhussain Majid, I haven't launched Custom yet, But I already send this information for me to launch with the necessary adjustments. So, the sequence for automated component removal is: 3 > 1 > 1 > 1 > S > C 3 Remove Menu 1 Remove Windows Components 1 Custom PreSets for Removing Windows Components 1 Accessibility Custom Selection Retornará automaticamente para "Remove Windows Components" S Start Removing Windows Components C Continue Here will start the removal procedure. I can automate it for 1 click if that's your interest. Below is the list of components to be removed for you to read and with your feedback, I can make adjustments to add or remove other components. I left several components, as I think they are crucial for the proper functioning of the system. Components Name List ... [1] Internet AdobeFlashForWindows InternetExplorer [2] Multimedia FirstLogonAnimation GameExplorer WindowsMediaPlayer WindowsPhotoViewer WinSAT [3] Privacy CEIP UnifiedTelemetryClient WindowsInsiderHub [4] Remoting [5] System Paint WindowsSubsystemForLinux WindowsToGo [6] SystemApps ECApp MapControl PeopleExperienceHost RetailDemoContent WindowsMixedReality XboxGameCallableUI WindowsReaderPDF EdgeDevToolsClient Edge OneDrive SecureAssessmentBrowser [7] WindowsApps ZuneVideo ZuneMusic Maps OfficeHub Paint3D People Photos SolitaireCollection BingWeather OneConnect Print3D 3DViewer MixedRealityPortal It may seem small but it is what I consider non-essential. Considering use by other blind people. We cannot leave this possibility aside. There is also the possibility to adjust a list for your specific use. In the custom toolkit on removal through lists 3 > 3 > Y > 2 they are read, and you are forwarded directly to 1 "Remove Windows Components", making it possible to use option 3 "Dependencies correction Filter" (which is automatic) and edit the choices through option 4 "Select Windows Components" or, simply follow the options S > C and wait for the end of the procedure. This "Dependencies correction Filter" option will save you headaches. If you want there where you have to press C to start the removal process, there is the option R, to return to the Menu "Remove Windows Components" where there are options 3 and 4 mentioned above.
hi, @RaiyvaN your package list sounds greate! that one click removal sounds like a neat edition Majid
hi @MSMG if it is no trouble, could you tell us how you find the packages files for removal? what apps, tools you use? for the remove methord via toolkit? not dism. in detail? and is it possible for us to contribute? I wish there was a utility that could assist you in locateing these packages. since you are 1, still suffering from the horror that is covid 19, 2, building the next genneration of software that will improve our lives, 3, have a life out side of mdl, it would be greate if we could lighten the load. here's an exammple. if I wanted to remove manually the folowing components how would I go about doing so? Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.928 Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-merged-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.867 Microsoft-Windows-Multimedia-RestrictedCodecs-merged-Package~31bf3856ad364e35~amd64~en- thanks! Majid
The TK can't integrate the TPM reg into the boot.wim 1 & 2 only in instal.wim MSMG could you please change or integrate this into the TK It can't be that almost all mainboards can't install Windows 11 without this TPM chip that's the only reason why I can't install Windows 11 And unfortunately there is no ASUS TPM-M R2.0 for sale
Sorry to be that guy again.. But why focus on a pre release version of Win11? Likely the hardware requirements won't be easily circumvented (reg file) in the final release. It just seems like a waste of time to me. It would be better to focus on the SFC errors in 21H1. Cheers.
Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig] "BypassTPMCheck"=dword:00000001 "BypassSecureBootCheck"=dword:00000001 Save this code as a reg file on your USB setup drive, for example Bypass TPM.reg - make sure that the file extension is .reg and not .txt if you save in Notepad. Start setup, then press Shift + F10 to open a command prompt, change to the path where you saved the .reg file on the setup drive, ie: D;\Resources and type in Bypass TPM.reg and accept the prompts to integrate this registry file. Be assured that this registry file is only integrated into the setup session and not your actual Windows 11 installation. Works for me on my old laptop.
@mhussain Majid, It's done. You will need to follow the 3 > 0 path to import and apply a list you already have. Or 3 > 1 > 0 to apply the predefined list in the Accessibility Custom Selection item. At the end of the application there will be 4 beeps indicating the end of the component removal process and Return to the previous menu. I will make this scheme work from the main menu. So, every pause there is in the script for you will beep. There is some things left to know: Do you prefer the beep and pause or the beep and continue? You can define, according to your experience, the amount of beeps and their meanings. I put 4 beeps at the end of the procedure. for stop could be 2 beeps. For multi component integration 1 beep. etc... Remembering that I just made assumptions about how I think it would be good. Description: These are short and short beeps so 4 beeps are quickly played. Tell me how it looks better for you. Also, 2 lists will be created in the path "Bin\Lists\Personal" inside your Toolkit folder with the names: "RemovePkgsList_[*].txt" and "RetainedPkgsList_[*].txt" Where the asterisk * character is a Date Time Stamp in the following format 20210629_173325. As the names above, one containing the removed components and the other containing the retained components. Today I send you the list of maintained components. Tell me if you want to add any of them to the custom removal list, you might want to keep Media Player and Zune Music so you can listen to music. I listen on the cmd.to page. Attached is the "PkgsLists.zip" file with the txt files of the removal example, as it is at the moment, for you to better analyze there.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Are you trying to pull my leg? I had posted this TPM bypass reg. on page 989 # 19778 and I know how to make a registry!!!
You're the one pulling your own leg, misinterpreting help given, with that kind of rude comment. He tried to help... If it wasn't helpful, simply say thank you. Just press the like. TK_ is only for integration through the Toolkit. Because the registry image offline mount, has been customized that way. Outwardly, to apply the registry through a .bat or .cmd script you would have to do the same procedure he mentioned, because anyway it wouldn't be possible to install. Final consideration: adding the registry file to the root of the usb stick install media is very simple and the most effective procedure at the moment. I put the Tweak in the Custom Toolkit. But I haven't tested any Windows 11 images yet.
I can't give an in-depth explanation but will give an overview of how to remove packages. The manual process involves reading the package mum files, get the associated manifest file list, expand the manifest files to get the file and registry data and then build the database of it and use it to remove the component. If there are no package mum files then you need to get the manifest file list manually, one method is by getting the hard link of the package files. In the example package you have given read the update.mum to get the sub-packages or manifest file list then expand the manifest file using the SxSExpand tool and read the expanded manifest file to get the package file and registry data. You will see something like this inside the manifest files, the file tag contains the package filename and location where a the registry tag contains the package registry key and values. Code: <file name="msmpeg2adec.dll" destinationPath="$(runtime.system32)\" sourceName="msmpeg2adec.dll" importPath="$(build.nttree)\" sourcePath=".\"> </file> Code: <registryKeys> <registryKey keyName="HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}\"> <registryValue name="FriendlyName" valueType="REG_SZ" value="Microsoft DTV-DVD Audio Decoder" /> <registryValue name="CLSID" valueType="REG_SZ" value="{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}" /> <registryValue name="FilterData" valueType="REG_BINARY" value="02000000ffff5f0002000000000000003070693300000000000000001a0000000000000000000000307479330000000020020000300200003174793300000000200200004002000032747933000000002002000050020000337479330000000020020000600200003474793300000000700200003002000035747933000000007002000040020000367479330000000070020000500200003774793300000000700200006002000038747933000000008002000090020000397479330000000080020000a00200003a7479330000000080020000b00200003b7479330000000080020000400200003c7479330000000080020000500200003d7479330000000080020000c00200003e74793300000000d0020000a00200003f74793300000000d0020000400200004074793300000000d0020000300200004174793300000000d0020000e002000042747933000000008002000030020000437479330000000080020000f0020000447479330000000080020000e00200004574793300000000d0020000000300004674793300000000d002000010030000477479330000000080020000200300004874793300000000800200000003000049747933000000008002000010030000317069330800000000000000040000000000000000000000307479330000000080020000300300003174793300000000800200004003000032747933000000008002000050030000337479330000000080020000600300006a910bed4d04d111aa7800c04fc31d602c806de046dbcf11b4d100805f6cbbea2b806de046dbcf11b4d100805f6cbbea32806de046dbcf11b4d100805f6cbbea33806de046dbcf11b4d100805f6cbbea20806de046dbcf11b4d100805f6cbbea6175647300001000800000aa00389b7181eb36e44f52ce119f530020af0ba77087eb36e44f52ce119f530020af0ba7705000000000001000800000aa00389b710120000000001000800000aa00389b7183eb36e44f52ce119f530020af0ba770af87fba7022dfb42a4d405cd93843bdd0020000000001000800000aa00389b710016000000001000800000aa00389b710216000000001000800000aa00389b71ff00000000001000800000aa00389b719200000000001000800000aa00389b710800000000001000800000aa00389b710300000000001000800000aa00389b710100000000001000800000aa00389b71" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> <registryKey keyName="HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}\Capabilities\"> <registryValue name="{374ac4df-7c98-4257-b13d-36087dbee458}" valueType="REG_DWORD" value="0x00000001" /> </registryKey> <registryKey keyName="HKEY_CLASSES_ROOT\CLSID\{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}\"> <registryValue name="" valueType="REG_SZ" value="Microsoft DTV-DVD Audio Decoder" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> <registryKey keyName="HKEY_CLASSES_ROOT\CLSID\{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}\InprocServer32\"> <registryValue name="" valueType="REG_SZ" value="$(runtime.system32)\msmpeg2adec.dll" /> <registryValue name="ThreadingModel" valueType="REG_SZ" value="Both" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> <registryKey keyName="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Decoder\"> <registryValue name="PreferredMPEG2AudioDecoderCLSID" valueType="REG_SZ" value="{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}" /> </registryKey> <registryKey keyName="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectShow\Preferred" perUserVirtualization="DisableRecurse"> <registryValue name="{e06d802b-db46-11cf-b4d1-00805f6cbbea}" valueType="REG_SZ" value="{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}" /> <registryValue name="{e06d8032-db46-11cf-b4d1-00805f6cbbea}" valueType="REG_SZ" value="{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}" /> <registryValue name="{00001600-0000-0010-8000-00aa00389b71}" valueType="REG_SZ" value="{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}" /> <registryValue name="{00001602-0000-0010-8000-00aa00389b71}" valueType="REG_SZ" value="{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}" /> <registryValue name="{000000FF-0000-0010-8000-00aa00389b71}" valueType="REG_SZ" value="{E1F1A0B8-BEEE-490D-BA7C-066C40B5E2B9}" /> </registryKey> </registryKeys> Yes will be taking a break may be in next two months as I will be moving to my native village to look after and to develop our agricultural land.