Scheduling System Restore Point Creation

lx07 said:

You could try sfc /scannow and see if it replaces it. Otherwise you may have to do a repair install.

I tried both the suggestions that you have made, but without success. I have therefore performed a new complete installation of Windows, and that has rectified the issue.

Thank you very much for your support and suggestions.

Cburg said:

Hi Forum,
I see that Win10 has deleted the function to schedule the creation of restore points!
Supposedly it creates a new restore point before downloading updates (if the function is turned on; by default it is off!).
I like to schedule the creation of points every few days or each week to prevent viruses from corrupting things.
This feature is so important; I can't believe they have hidden it, made it less functional, and turned it off by default!
Is there any way to run the creation button from the task scheduler or something to automatically schedule restore point creation?
Thanks!
Mike

Yes. I am amazed and annoyed that W10 Creators has removed the ability to create scheduled daily Restore Points. I used it before Creators, including in Windows 7 for years. I tried making a shortcut on the Desktop to make an anual RP (tenforums...... tutorials/64869) but it didn't work. Perhaps Microsoft has nobbled it for Creators.

I now have to search in the Start seach bar for Restore > Create a Restore Point which opens System Properties. Then press Create, type a name for the Restore Point when, at last, the Restore Point will be created!!!. Every day!! Microsoft is nibbling away at the freedom of users to use Windows in the way they want. Creators lacks other long-established routines.

At least Windows Backup and Restore ("Windows 7") will still backup files which are on the C drive, and a separate Windows Image, both in accordance with a time shedule. (But a Macrium Image is better, many people say, which I have, also set up to be made every day in a time schedule.

lx07 said:

.The difference is the "run whether user is logged on or not" setting.

That setting made silently ineffective some commands inside scripts, only when scripts were run by tasks (whether on schedule or invoked manually in task scheduler UI). The changing of that setting allowed the commands to be silently effective when scripts are run by tasks. Not that I know the reason.