<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Schtasks on Locodigital</title><link>https://locodigital.com.br/en/tags/schtasks/</link><description>Recent content in Schtasks on Locodigital</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 22 Jul 2026 09:00:00 -0300</lastBuildDate><atom:link href="https://locodigital.com.br/en/tags/schtasks/index.xml" rel="self" type="application/rss+xml"/><item><title>How to schedule Windows tasks without a GUI — schtasks in practice</title><link>https://locodigital.com.br/en/technology/schtasks-schedule-windows-tasks-from-the-terminal/</link><pubDate>Wed, 22 Jul 2026 09:00:00 -0300</pubDate><guid>https://locodigital.com.br/en/technology/schtasks-schedule-windows-tasks-from-the-terminal/</guid><description>&lt;p&gt;How many of you have opened the graphical Windows Task Scheduler, clicked "Create Task…" and got lost in the Triggers, Actions and Conditions tabs? &lt;code&gt;schtasks.exe&lt;/code&gt; solves that in the terminal, with no GUI, in a single command line — and it's installed on every Windows since XP.&lt;/p&gt;
&lt;p&gt;If you already know &lt;a href="https://locodigital.com.br/en/technology/crontab-on-linux-how-to-schedule-tasks/"&gt;crontab on Linux&lt;/a&gt;, the logic is similar: you define when to run and what to run. The main difference is the syntax — and the fact that schtasks can run tasks as any user, including SYSTEM, without needing a password visible in the script.&lt;/p&gt;</description></item></channel></rss>