Is your Windows Photo Viewer working? What are you getting in sfc scan? I was getting the following when I first ran sfc scan : 2018-08-27 13:3 1:17, Info CSI 000023d7 [SR] Repairing corrupted file \??\C:\Windows\System32\en-US\\OneDriveSettingSyncProvider.dll.mui from store 2018-08-27 13:3 1:31, Info CSI 000026b8 [SR] Repairing corrupted file \??\C:\Windows\System32\\OneDriveSettingSyncProvider.dll from store 2018-08-27 13:33:58, Info CSI 00004421 [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\en-US\\OneDriveSettingSyncProvider.dll.mui from store 2018-08-27 13:34:04, Info CSI 00004565 [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\\OneDriveSettingSyncProvider.dll from store 2018-08-27 13:34:44, Info CSI 00004d91 [SR] Repairing corrupted file \??\C:\Windows\System32\en-US\\OneDriveSettingSyncProvider.dll.mui from store 2018-08-27 13:34:44, Info CSI 00004d93 [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\en-US\\OneDriveSettingSyncProvider.dll.mui from store 2018-08-27 13:34:44, Info CSI 00004d95 [SR] Repairing corrupted file \??\C:\Windows\System32\\OneDriveSettingSyncProvider.dll from store 2018-08-27 13:34:44, Info CSI 00004d97 [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\\OneDriveSettingSyncProvider.dll from store
When you say Toolkit Helper, what do you mean? Because I can't seem to find anything related to that.
You need to use [5] Customise -> Tweaks -> Enable and Set Windows Photo Viewer As Default Viewer to enable PhotoViewer, then the option will be available in the defaults list. Although the Tweaks is meant to make the Windows PhotoViewer as the default one, the Settings app won't obey it, still some extra tweaks needs to be added to automate it. It's normal the SFC will throw errors when a patch or skin is applied to windows files When a component is removed using the ToolKit Remove Component menu, it uses the DISM.exe to remove the component which does causes the SFC to throw errors.
In ToolKit-v8.8\ToolKit.cmd (open with notepad++ or notepad, notepad ++ it shows line numbers) change line 25209 from Code: echo. echo.------------------------------------------------------------------------------- echo.Removing Microsoft Unified Telemetry Client ^(Asimov^) Package... echo.------------------------------------------------------------------------------- %ToolKitHelper% "%InstallMount%" UnifiedTelemetryClient echo. to Code: echo. echo.------------------------------------------------------------------------------- echo.Removing Microsoft Unified Telemetry Client ^(Asimov^) Package... echo.------------------------------------------------------------------------------- REM %ToolKitHelper% "%InstallMount%" UnifiedTelemetryClient echo. REM = comments = skip This change is for version 16299+ But if you search for UnifiedTelemetryClient can be done for older version of windows to.
Anyone having issues with configuring Xbox accessories (i.e One S controller) ? I'm stuck on the next page after pressing configure. Perhaps some component removal doesn't play nice?
Hello MSMG I've been using days ago the Toolkit v 8.8 (having Windows 8.1 as host) so I was able to check in your Read me. txt that the cleanup Source images with Component cleanup & Resetbase item does not appear as the first option within Windows 8.1/Server Usage Order What It can cause problems for some users who may not pay the proper attention.
So if I use the latest August Win10 image then I should not remove components because it breaks the Windows setup process?
Usually I don't recommend MS refreshed source images because - Previously the DISM had issues in removing Apps, But now I don't know whether that issue still exists or not. - By the time the MS releases a refreshed ISO, the updates contained in the image are outdated. With the latest Windows 10 RS4 LCU, removing WMP breaks the windows setup, so I do not recommend removing it or use the original image remove the components and then integrate the updates/install updates through WU.
As earlier said, the Microsoft has made it more difficult to remove components by merging several removable components into main packages and so the usual method of using DISM to remove a component wont work anymore. Starting from next version of Toolkit (command-line), As a starting point the Toolkit will start the process of using the manual method (ToolKitHelper.exe) to remove all components for Windows 10 RS3 (MUI), RS4 (MUI) Source OS's. If there is no new W10 RS5 build until next week then support for W10 RS5 Build 17751.1 (en-GB/en-US) Source OS will also be added for testing. The component removal for other Source OS's will be removed temporarily and will be added back when it's ready to use the manual method (ToolKitHelper.exe). People using the ToolKit to remove components for other Source OS's do stick with the current version.
Hello MSMG, out of pure curiosity my programming language uses the ToolkitHelper.exe or manual method since from now on we will not be able to use Dism anymore because of its limitations maybe from now on would be the Powershell? or something similar to the Chocolatey staff ...
It's not that DISM can't remove any packages but only the packages that are merged can't be removed properly. I don't know Powershell programming and also it's bit slow in execution. The current Toolkit script needs to be cleaned up and refactored, I'm thinking of using the C# instead of batch for Toolkit command-line and so both the CMD and GUI will be using the same programming language.