![]() ![]() If you choose to run this task, the task will have a 1 hour timeout and may not completely clean up all files. 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. This task is set to run automatically when triggered by the operating system. ![]() The StartComponentCleanup task was created in Windows 8 to regularly clean up components automatically when the system is not in use. This article gives information about a built-in Task Scheduler task: Library\Microsoft\Windows\Servicing\StartComponentCleanup The cleanup that this article discusses is cleaning up old components, this correlates to the removal of the superseded updates.Ĭlean Up the WinSxS Folder - Task Scheduler It turns out that this is exactly what I was looking for. While researching the issue, I came across an article detailing Windows built-in capability to clean up out-of-date components. So why are these superseded updates lingering and only being cleaned up during patching? Windows Task Scheduler StartComponentCleanup ![]() This means that much of our time spent patching is actually spent handling these superseded updates, causing our patches to take MUCH LONGER than we planned for. These events would always occur right as we are starting patching during our maintenance window. In this event viewer log, we can see an event denoting that a KB was marked as superseded and is to be removed. For people new to investigating patching on Windows Server, there is a Windows Event Viewer log called Setup which has events related to patch installation. So firstly lets talk about how we know there are CUs and other updates that are being cleaned up and delaying patch installation. Find more information about these scheduled tasks and Dism.exe commands here. This allows for faster, more reliable patching during maintenance windows. ![]() To fix this, you're able to run a Dism.exe command to manually cleanup these superseded updates. This scheduled task is responsible for cleaning up superseded updates. In short, the superseded updates were being caused by a Windows Owned scheduled task failing. ![]()
0 Comments
Leave a Reply. |