I thank you for the valuable information. I tried on a virtual machine, started Powershell with administrator rights I pasted the command and restarted, but the connect app is not deleted. Maybe I'm wrong.
@Tapan Mazumder When a new ToolKitHelper.exe is released, I always rebuild ToolKit_v9.9.7z with the new file. This way I don't have to remember to copy the new version each time I extract the ToolKit.
Ok try this First run these commands in the command prompt Code: reg load HKLM\test C:\Windows\System32\Config\SOFTWARE reg add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v Visibility /t REG_DWORD /d 1 /f reg add "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1" /v DefVis /t REG_DWORD /d 2 /f reg delete "HKLM\test\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1\Owners" /f reg unload HKLM\test Then run the below command in command prompt to remove the Connect App. Code: Dism /Online /Remove-Package /PackageName:Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.18362.1 If your OS version is different then change the version in the above commands. PS: In W10 v2004 the Connect App is not present.
I did the proper testing and as a result, actually removing "Cortana, StartMenu and Settings Search App" from the "SystemApps" menu, breaks the search bar. Just remove the "CortanaApp" from "WindowsApps" menu and everything will be fine (for 1909 H2). I was doing this. And I was getting a "CONFIG INITIALIZATION FAILED STOP CODE ERROR" installation failure. I found that this occurs when "HKLM\System\CurrentControlSet\..." or for the entries I added in the Toolkit.cmd script "HKLM\TK_System\CurrentControlSet\..." registry entries are implemented Resolved by replacing this volatile entry with root entries: "HKLM\System\ControlSet001\..." or for the entries I added in the Toolkit.cmd script "HKLM\TK_System\ControlSet001\..." So... that way the addition of my "*.reg" files were imported perfectly. I hope this information is useful. Now let's get to the problem I'm experiencing at the moment. The compilation I am preparing has 3 index (Home, Pro and Pro for WorkStations). The problem is that when I install the Pro version, at the end of the installation, the Enterprise version watermark appears. Does anyone know what may be happening? Grateful for the attention!
hello , I can't creat new txt documents after remove some packPkgslists ,what caused it ,please, my win10 version is v2004,19041.208
i can't perform step 6> 1 because i get this message Cannot Perform Image Component Cleanup when Pending.xml is present... MSMG ToolKit Commandline Helper Version: 1.0.3132.0
Look here https://forums.mydigitallife.net/threads/how-to-clean-the-component-store-in-an-offline-image.81716/
Tried this, but still get SFC errors when I omit this step from my normal method. Spoiler: Method Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > C) Apply SSU and CU updates (3 > 4 > 2 > 1 > 4) Apply setup media update (3 > 4 > 2 > 2) Remove using RemovePkgsList.txt (4 > 3) Spoiler: RemovePkgsList.txt ToolKitHelper:GameExplorer ToolKitHelper:MapControl ToolKitHelper:OneDrive ToolKitHelpereopleExperienceHost ToolKitHelperPIProjection ToolKitHelper:RetailDemoContent ToolKitHelper:SkypeORTC ToolKitHelper:SecureAssessmentBrowser ToolKitHelper:WindowsMixedReality ToolKitHelper:XboxGameCallableUI ToolKitHelper:WindowsApps Tweaks for Task View, App Downloads, Photo Viewer (5 > 8 > B/D/J) Cleanup (6 > 1) Apply changes to image (6 > 2 > Y) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1) If I don't integrate Windows Updates I no longer get SFC errors with my method.