I would've liked to have had it go for longer as I was still getting used to Windows 10. I personally think they should make that a user customisable amount, perhaps the minimum being 10 and the max at perhaps 90 days. I wouldn't recommend it over a backup, but it could be convenient keeping the rollback option around a bit longer. The problem with saying exactly which task it is, is that currently whatever task it is (I suspect "start component cleanup") isn't set to run at any future time, along with many others, and also my suspicion could be wrong, and the task itself may self delete after being run, I just remember when I did it, it seemed fairly self-evident which task would control it, and disabling that task did in fact work until I decided the update was safe, so I re-enabled the task, just in case it was needed for other cleanup stuff.Īnyway just thought I'd mention it in case it's something someone might find useful and want's to investigate after the next feature update. not monthly or weekly), and will likely be the only one that is set to run this far in the future. When it's active it will be scheduled to run in approx 10 days and it's a one off task (i.e. I can't remember 100% which task it was, But it's relatively easy to find if you use something like Nirsofts taskscheduleview.exe which lists all tasks in a sortable listbox view (i.e sort on next run time). The delivery optimization & Windows Update cleanup options, were and still are always present, but didn't (and I assume won't) do anything with windows.old when the old chestnut crops up again.Īlso regarding the 10 days auto cleanup, you can stop it from happening, it's controlled by a task in task scheduler. also disk cleanup needed to be run as admin, or the clean system files button needed to be clicked). Windows.old cleaning was always handled via a separate option named something along the lines of "remove previous windows installations" (which was a dynamic option in that it only ever existed as an option when there was a windows.old to clean. Regarding Windows.old removal, Assuming system sense is to also include the same options to do the same thing as the "old" disk cleanup. Storage Sense is one of the features MS are keen on improving, so I would expect more changes/improvements with the setting options in next months September 2018 feature upgrade. Of course its easy enough to empty the bin yourself at any time so I believe SS just does it with older files. With the recycle bin I'm also not sure how it works there, but there is a setting in "Change how we free up space." to leave files in the bin alone for different periods. (We'll be able to check on that in a month or so when the September feature update to v1809 comes). Of course minor updated and Patch Tuesdays don't usually craete a windows.old, but I'm pretty sure that SS also removed that after the last feature update. ![]() ![]() I'm not sure just how it works though if you have SS set to a schedule or just runnning when it thinks it needs to, which is why I put that bit in parenthises.Īlso from reading that I'm also not sure if will remove it, or compress it pending removal later? So obviously from that if you runs SS manually then you do not have to wait 7 days. (You can also see that the figure for Delivery Optimisation Files has gone up since the previous screenshot, from 236 to 508 KB). ![]() Running Free up space now in Storage Sense found it as 1 MB so I grabbed another screenshot: It's 1.2 MB download to patch Intel CPU microcode against Spectre (again). Well that was timely, this afternoon during my weekly clean up routine I ran WU and got an update, KB4100347.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |