In the Task Scheduler library there is a subdirectory "Microsoft." It is shown as blank, though I know there are tasks there. Is this intentional or a quirk in my setup?. The reason I am looking this time is an article about reducing the size of the WinSxS folder https://msdn.microsoft.com/en-us/win...or=-2147217396. This suggests to run the Task Scheduler Library\Microsoft\Windows\Servicing\StartComponentCleanup.
tcebob
Though this article was written for Windows 8 it talks about this scheduled task: Clean Up the WinSxS Folder. You can always run the DISM command manually, but I agree that something is amiss with your system. Using Everything to search for "StartComponentCleanup" on my production desktop, here's what I get:
If you want to try the manual command, the syntax is:
HTH,
--Ed--
Ed, Thanks for your advice. I was able to import the file into a new directory (\MS) -- but only after renaming it to *.xml, since that's what Task Scheduler is looking for. I ran it but couldn't tell if it was doing anything. Checked size of Winsxs folder. 3.8 G. That's better than the 5+ G that it was yesterday. So maybe it did work. When run manually in cmd, using dism.exe /online/ cleanup-image /startcomponentcleanup, there was an error comment: DISM doesn't recognize the command-line option "cleanup-image". So maybe it's changed since Win 8.
Anyway, the system doesn't seem to mind that the Microsoft Task Scheduler folder is empty. Apparently it refers directly to the \servicing directory.
I can only assume that MS moved all of its scheduled tasks out of public view to avoid tampering. Why they left the empty directory I can't guess. Or is it really empty? Are the files really there but invisible? Where will we all be on Coronation Day?
tcebob
You have put a space in front of "cleanup-image", that is the reason of the error.
Tasks are still located at the suggested location, do you have system files un-hidden?
If you can not see them directly in Task Scheduler, then there is definitely something wrong.
What TairikuOkami said: gotta put those slashes and spaces in the right places. Just ran this on my production PC at the (admin) command line to prove it to myself:
Syntax details matter. If you like, cut'n'paste this string:
dism /online /cleanup-image /startcomponentcleanup
and everything should work fine.
HTH,
--Ed--
Right. The space belonged before the slash, not after. dism.exe /online /cleanup-image /startcomponentcleanup
Since the consensus is that my system is awry I hope I can find how to fix it. The Microsoft subdirectory has been blank ever since I first upgraded to Win 10, last year. This has been through numerous upgrades. I have to be cautious about completely reinstalling Windows considering the slight advantage of getting a few oddities corrected compared with the weeks of work reinstalling all my software. But if you have any less drastic suggestions I'd like to hear them.
tcebob
If you're not getting any repairs from
sfc /scannow
dism /online /cleanup-image /restorehealth /source:WIM:<repairsource>\install.wim
you might want to consider an in-place upgrade/repair install. Here's a tutorial on that subject: Repair Install Windows 10 with an In-place Upgrade - Windows 10 Tutorials.
HTH,
--Ed--
PS: For DISM details see also DISM - Repair Windows 10 Image - Windows 10 Tutorials
Ed, good tips. I'll pursue them. I have tried repair install before without much success, but did not see the tutorial.
tcebob
Quote
