Regarding Windows.old removal, Assuming system sense is to also include the same options to do the same thing as the "old" disk cleanup. 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. also disk cleanup needed to be run as admin, or the clean system files button needed to be clicked). 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.
Also regarding the 10 days auto cleanup, you can stop it from happening, it's controlled by a task in task scheduler. 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). When it's active it will be scheduled to run in approx 10 days and it's a one off task (i.e. not monthly or weekly), and will likely be the only one that is set to run this far in the future. 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.
Anyway 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. I wouldn't recommend it over a backup, but it could be convenient keeping the rollback option around a bit longer.
I do not have W10 installed currently (long story I'll spare you, its going to be installed again soon) however this may or may not help, useful for previous versions.
If you open a command prompt as admin and:
cleanmgr.exe /sageset:1
You should have if you are lucky more options here to pick from, select as needed. To actually run it this way (well I think this way rather than "just the defaults") , again as admin:
cleanmgr.exe /sagerun:1
You can have several 'sageset' / 'sagerun' sets if you wish. With W7 I tend to just have one and use the normal cleanup occasionally and rarely (say every month or two) use the sagerun:1 option on it.
<div class="ipsQuote_contents">
<p>
Also regarding the 10 days auto cleanup, you can stop it from happening, it's controlled by a task in task scheduler.
</p>
</div>
I personally think they should make that a user customisable amount, perhaps the minimum being 10 and the max at perhaps 90 days. I would've liked to have had it go for longer as I was still getting used to Windows 10.
<div class="ipsQuote_contents">
<p>
I personally think they should make that a user customisable amount, perhaps the minimum being 10 and the max at perhaps 90 days. I would've liked to have had it go for longer as I was still getting used to Windows 10.
</p>
</div>
Yeah I definitely agree with you there. It's not like MS is known for it's ability to fix problems caused by upgrades within 10 days, so it really shouldn't be enforcing a no backsies policy for a timeframe they also can't adhere to. Not to mention it would be somewhat trivial for them to offer a setting which effectively alters the run time of a task that is going to do the work. Especially when you consider the task that controls this functionality doesn't actually allow the trigger time itself to be altered via task scheduler, it only allows toggling whether it's disabled/enabled.
I know I'm willing to put up with a problem that's introduced for around a month (assuming it's an intermittent issue, not some major always happens problem) but if it takes much longer I'd be inclined to roll back, the issue with 10 days, is sometimes the intermittent problems aren't even apparent till it's too late.
Hardware related issues are rather obvious which is what I dealt with the first time it installed v1803. On the software side I wouldn't really know what it could've potentially broke since it really isn't feasible to open every possible program on a computer in that allotted time since I'd merely be running non-stop testing of the computer versus just using and enjoying it.