Tag Info

New answers tagged

0

The other answer suggest this syntax indicates increments. Now I've set up a test with this expression 1/12 on the minutes field: 1/12 * * * * date >> ~/crontest.tmp If it would increment, then it would run on these minutes of every hour: 1, 13, 25, 37 and 49. But the results so far are: Mon Aug 24 17:01:01 CEST 2015 Mon Aug 24 18:01:01 CEST 2015 ...


1

Using net use S: \\D-DWSQL01\Share\load Apparently allowed the schedule task to see the drive normally.


1

What would be the expected behaviour of 1/12? 0 1/12 * * * doSomething This means run at 1 am and then every 12 hours (1,13,...). Special characters / - used to specify increments. For example, 0/15 in the seconds field means "the seconds 0, 15, 30, and 45". And 5/15 in the seconds field means "the seconds 5, 20, 35, and 50". Source ...


0

That appears to be the system maintenance task running. If so, you might try disabling system maintenance. WIN+R control search for "maintenance" in the search box, select "Change Automatic Maintenance settings". Clear the "allow scheduled maintenance to wake up my computer at the scheduled time". See if that helps remove the issue. It's going to be a lot ...


2

This has worked for me so far. Go to: Control Panel\Hardware and Sound\Power Options\Edit Plan Settings Click "Change advanced power settings" Go to "Sleep->Allow wake timers" and change the setting to Disable.


2

After upgrading to Windows 10, the computer in my bedroom kept waking me up at 3AM. Disabling Wake the computer on the Microsoft\Windows\UpdateOrchestrator\Reboot scheduled task didn't help. Windows turns the flag back on periodically. Even disabling "Disable wake timers" in Power Options didn't help. The UpdateOrchestrator kept orchestrating midnight ...


0

I think the problem is that I had marked the task to: (o) Run whether user is logged on or not According to Microsoft, You can specify that a task should run even if the account under which the task is scheduled to run is not logged on when the task is triggered. To do this, select the radio button labeled Run whether user is logged on or not . If ...


0

Slurm can not know how many processes/threads a script is going to create. It can only rely on the resources requested and hence that is what it uses to schedule jobs. The best approach here will be to use any of the affinity plugins in Slurm to prevent jobs using more resources than requested. This plugins bind a job to the requested cpus. (Affinity ...


2

Go to Start then Settings, select Privacy and click on Background apps. From there disable the apps that you don't want running in the background. This apps don't start with Windows, that's why they don't appear in the autostart list or the task scheduler. They are called upon by the Windows Runtime that manages universal apps. Most of the time they only ...


2

This should solve your problem: Search Task Scheduler Navigate to Task Scheduler Library\Microsoft\Windows\UpdateOrchestrator\Reboot Note: Reboot is just a file, but you need to go inside all those folders Right Click Properties then click Conditions Uncheck Wake the computer to run this task


0

You can download and run Autoruns for Windows: https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx It is the most powerful program for viewing things that automatically runs with Windows


0

I would recommend verifying you "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp" location for any unwanted application.


0

Most processes spend their time waiting (waiting for a network packet, waiting for the user, waiting for some other process/thread, ...). It does not make sense for the operating system to schedule that process at all - it would just return immediately and continue to wait. Uselessly looping draws power. Instead, if all processes are waiting (more ...


31

There are two directories within which you might find a scheduled task definition or log: c:\windows\tasks c:\windows\system32\tasks That said, depending on the task, you may or may not have difficulties using the configured task on another computer. Some tasks may contain system-specific information, and others may be in formats that cannot be opened ...


17

Tasks are normally stored in C:\Windows\System32\Tasks (as xml files). You should be able to import from there



Top 50 recent answers are included