Hi winter.
Have you seen this parameter for DISM in Windows 8.1?
/StartComponentCleanup
The StartComponentCleanup task was created in Windows 8 to regularly clean up components automatically when the system is not in use. This task is set to run automatically when triggered by the operating system. When run automatically, the task will wait at least 30 days after an updated component has been installed before uninstalling the previous versions of the component.
Apparently it should be used with /ResetBase. See this MS Technet article.
Also, could you add the command as a task via WinReducer?
http://technet.microsoft.com/en-us/library/dn251565.aspx
I will look into this on my PC when I get home tonight. Usually Task Scheduler creates a file on OS level for each task, so it might be just as easy as copying and pasting this file, but maybe not
Also, maybe you could implement the steps from this MS Technet article into WinReducer:
Analyze and clean up the Component Store (WinSxS folder) in an offline Windows image
....
....
6. Analyze the size of the component store. For example:
Dism /Image:C:\test\offline /Cleanup-Image /AnalyzeComponentStore
7. If the component store cleanup was recommended in the displayed report, then you can start cleanup of the image. For example:
Dism /Image:C:\test\offline /Cleanup-Image /StartComponentCleanup
8. You can reduce the size of the component store further by adding the /ResetBase parameter. For example:
Dism /Image:C:\test\offline /Cleanup-Image /StartComponentCleanup /ResetBase
Maybe you can run the analysis in step 6, and based on that, perform step 7 and/or step 8.
I think that would be a better way of doing /ResetBase??
Thx.
theKramer
Have you seen this parameter for DISM in Windows 8.1?
/StartComponentCleanup
The StartComponentCleanup task was created in Windows 8 to regularly clean up components automatically when the system is not in use. This task is set to run automatically when triggered by the operating system. When run automatically, the task will wait at least 30 days after an updated component has been installed before uninstalling the previous versions of the component.
Apparently it should be used with /ResetBase. See this MS Technet article.
Also, could you add the command as a task via WinReducer?
http://technet.microsoft.com/en-us/library/dn251565.aspx
I will look into this on my PC when I get home tonight. Usually Task Scheduler creates a file on OS level for each task, so it might be just as easy as copying and pasting this file, but maybe not
Also, maybe you could implement the steps from this MS Technet article into WinReducer:
Analyze and clean up the Component Store (WinSxS folder) in an offline Windows image
....
....
6. Analyze the size of the component store. For example:
Dism /Image:C:\test\offline /Cleanup-Image /AnalyzeComponentStore
7. If the component store cleanup was recommended in the displayed report, then you can start cleanup of the image. For example:
Dism /Image:C:\test\offline /Cleanup-Image /StartComponentCleanup
8. You can reduce the size of the component store further by adding the /ResetBase parameter. For example:
Dism /Image:C:\test\offline /Cleanup-Image /StartComponentCleanup /ResetBase
Maybe you can run the analysis in step 6, and based on that, perform step 7 and/or step 8.
I think that would be a better way of doing /ResetBase??
Thx.
theKramer