New
#11
As Halasz said earlier:
You can schedule them through task scheduler as described in method 2 here System Restore Point : Create at System Startup - Windows 7 Help Forums
Schedule a neat little script to run.
As Halasz said earlier:
You can schedule them through task scheduler as described in method 2 here System Restore Point : Create at System Startup - Windows 7 Help Forums
Schedule a neat little script to run.
I have tried to precisely follow the instructions set out in System Restore Point : Create at System Startup - Windows 7 Help Forums, but the Task Scheduler / script is failing to create a restore point:
- Running the script manually creates a Restore Point.
- Task Scheduler appears to run the script, but no Restore Point results.
(The Last Run Result code 0x41301 indicates "The task is already running".)
The Task Scheduler settings are as follows:
I would be grateful for any suggestions as to why the restore points are not being created.
Hi, not sure- not had a problem with this.
Do you have UAC on? If so, try with it switched off.
Does the name of your vbs script match with what is in your schedule?
You say running the vbs manually creates a restore point - I assume you mean by d clicking the vbs file.
Have you tried running the scheduled task manually? (Not 100% clear you have from above). (rt click scheduled task name, run)
Desperation:
Try inserting a dummy entry in the scheduled task Action - say Wordpad.exe and try running the scheduled task manually.
Hi. Thank you for the response.
Yes.
Yes. (I browsed to it.)
Yes.
Yes. The task "runs", but no restore point is created (ie. identical result to the scheduled run).
I've tried this. Wordpad appears under Task Manager, but does not open a window.
.The difference is the "run whether user is logged on or not" setting. This means it will not open a window but run task as a service. That being so both are acting correctly (for wordpad).
Don't know why the script wouldn't work from task scheduler. You unblocked it right?
Thank you for the postings, dalchina and halasz.
Yes, I did unblock it.
I hadn't realised that "run whether user is logged on or not" setting would cause the program to runs as service, and not open a window. I've therefore changed the setting for both Wordpad and the script. Wordpad now opens, but when Task Scheduler tries to run the script, the message "How do you want to open this file?" appears. Is the problem that Task Scheduler, on my PC, doesn't know how to run a script?
You shouldn't have to install it as far as I know. I also have it in System32 and SysWOW64 directories.
As a workaround you could make a batch file Something.bat and put the line cscript /nologo C:\Path\to\file.vbs (assuming you have cscript.exe) and schedule that instead.
Why wscript is not there is another matter. You could try sfc /scannow and see if it replaces it. Otherwise you may have to do a repair install.