What is the JOB file format?
.JOB is a system file used by Windows Task Scheduler. .job files contain rules regarding what action should be taken, at what time, and under what conditions. Each task is given a name, and the Task Scheduler service must be enabled for them to run.
.job files belong to the legacy Task Scheduler 1.0 binary format, introduced with Windows 95/98 and standard through Windows XP. They are stored in C:\Windows\Tasks. Starting with Windows Vista, Task Scheduler 2.0 replaced the .job format with XML files stored under \Windows\System32\Tasks - .job support on modern Windows is retained only for backward compatibility.
Tasks from .job files may be called manually or automatically when certain conditions are met (such as a scheduled time or system event). The tasks can be activated even if the user is logged out. Additionally, some tasks may be run under the control of other users - for instance, an Administrator. Task Scheduler is used to automate such operations as scanning the system for viruses or performing periodic backup copies.
Tasks are managed through the Task Scheduler MMC snap-in (taskschd.msc) or the command-line tool schtasks.exe. A .job file is not an executable - it is a scheduled-task definition read by the Windows service. Its internal structure is binary (a fixed-length header followed by a variable section storing the application name, parameters, working directory, and trigger array), so inspection requires a hex viewer rather than a text editor.
Security & safety
RISK: MEDIUMA .job file itself is inert data, but scheduled tasks are a classic persistence mechanism for malware - a hidden task that re-launches a payload at logon or on a timer. If you find an unexpected .job (or an odd task in Task Scheduler) that runs a script from a temp/AppData path, treat it as suspect: inspect the action in Task Scheduler, and disable/delete it there. Don't try to "run" a .job by double-clicking; manage it through taskschd.msc with the right privileges. Removing a legitimate system/updater task can break scheduled maintenance, so identify the task before deleting it.
Format details
in a nutshellPrograms that open JOB files
Technical details
deep spec| File type | Binary scheduled-task definition (Task Scheduler 1.0) |
| Encoding | Binary, little-endian |
| Container structure | Fixed-length FIXDLEN_DATA header + variable-length data section |
| Header contents | Product version, file-format version word, task UUID, priority, exit/error codes, idle and run-time settings |
| Variable section | Application name, command-line parameters, working directory, author comment, and an array of trigger definitions |
| Encryption | Task body unencrypted; an optional credential blob for the run-as account may be obfuscated |
| Typical file size | Under 1 KB to a few KB |
| Storage location | C:\Windows\Tasks (Windows 95 through XP era) |
| Supported OS | Windows 95/98/Me, Windows NT4/2000/XP/Server 2003; legacy compatibility on Vista and later |
| Task Scheduler version | Task Scheduler 1.0 (format frozen; not extended after Windows XP) |
| Superseded by | Task Scheduler 2.0 XML task files stored in \Windows\System32\Tasks (introduced Windows Vista, 2007) |
| Management tools | taskschd.msc (MMC snap-in), schtasks.exe (command line) |
| MIME type | application/octet-stream |
| Released | Task Scheduler 1.0 - Windows 95/98 (with Internet Explorer 4 / 'System Agent') through Windows XP/2003; legacy on Vista+ |
| Latest version | Task Scheduler 1.0 .job (frozen); Task Scheduler 2.0 (Vista, 2007) replaced it with XML task files |
| Specification | learn.microsoft.com |
JOB conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about JOB files.